Publisher verification
Concept
Publisher verification is a Microsoft Entra program that marks an application's publisher as verified, so consent policies can restrict user consent to apps from verified publishers.
Description
Publisher verification is a program in the Microsoft identity platform that gives users and administrators information about the authenticity of the organization behind an application. When an app integrated with Microsoft Entra is verified, a blue verified badge appears on the consent prompt and on the enterprise applications page. The badge shows that Microsoft has confirmed the publisher's identity. It does not describe the quality of the app and is not a certification.
The confirmation works through a verified Microsoft AI Cloud Partner Program account. The partner ID of that account is linked to the app registration, and Microsoft uses this link to establish who publishes the app. Administrators can then use the verification status as a criterion in user consent policies. This allows an organization to restrict user consent so that people can only approve apps from verified publishers, while other apps require administrator review.
Several requirements apply. The partner account has to be the verified global account of the organization. The app must be registered in a Microsoft Entra tenant with a work or school account, not in Azure AD B2C, and that tenant has to be associated with the partner account. The publisher domain must match the e-mail domain used during verification and cannot be an onmicrosoft.com domain. The user who starts the process needs an application administrator role in Entra and an admin role in Partner Center, and must sign in with multifactor authentication. There is no fee and no license for the program.
The feature mainly applies to multitenant apps that use OAuth 2.0 or OpenID Connect. National clouds are currently not supported, according to the documentation notes. Organizations that run apps in those environments therefore cannot rely on this mechanism today.
In practice, publisher verification is one building block of governing third-party apps and integrations in Microsoft 365. Without any guardrail, users may grant permissions to unknown applications, which creates exposure for organizational data. Combining a consent policy that requires verified publishers with a review process for everything else gives administrators a more manageable approval path. Because the badge only confirms who publishes an app, it works best alongside other checks, such as reviewing the permissions an app requests.
The M365.FM episode "Leadership and Microsoft 365 Governance Beyond Central Control" mentions publisher verification in its governance checklist. The episode lists reviewing and governing third-party apps and integrations with Microsoft 365, naming app consent and publisher verification, as one of the recurring governance tasks. It places this next to regular risk assessments, compliance gap analysis, budgeting for governance tools and administration, and periodic governance reviews with executive sponsorship. In that framing, controlling app consent is part of a continuous governance cycle rather than a one-time setting.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What does the blue verified badge in publisher verification mean? (AI)
It shows that Microsoft has confirmed the publisher of the app through a verified Microsoft AI Cloud Partner Program account linked to the app registration. It says nothing about the quality of the app and is not a certification.
How can administrators use publisher verification? (AI)
Administrators can use the verification status as a criterion in user consent policies, for example to allow user consent only for apps from verified publishers.
Does publisher verification cost anything or require a license? (AI)
No. The documentation notes state that there is no fee and no license. The process does require a verified partner account and specific admin roles in Entra and Partner Center.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: