Developer apps shows the publisher verification record for each app. Add a TXT record at the displayed _institution subdomain of the app website’s host, with the institution-app value containing that app’s client ID.
Use the exact host and value from the app record rather than copying another app’s verification text. Then choose Verify publisher in developer settings.
If verification fails, check the DNS record’s name and value and allow for DNS propagation before retrying. A successful verification changes the action to Publisher verified.
Publisher verification does not by itself publish the app or grant it customer data. Submit for directory review separately, and each customer must still authorize access. If the website host changes during app editing, review the current verification instructions and the consent implications. Ask support about persistent verification problems with the app ID and public DNS context; there is no reason to send a client secret as proof of domain ownership.
Was this article helpful?
Tell us whether this answered the question you came with.