Publisher verification

Publisher verification gives app users and organization admins information about the authenticity of the developer's organization, who publishes an app that integrates with the Microsoft identity platform.

When an app has a verified publisher, this means that the organization that publishes the app has been verified as authentic by Microsoft. Verifying an app includes using a Microsoft Cloud Partner Program (CPP), formerly known as Microsoft Partner Network (MPN), account that's been verified and associating the verified PartnerID with an app registration.

When the publisher of an app has been verified, a blue verified badge appears in the Microsoft Entra consent prompt for the app and on other webpages:

Screenshot that shows an example of a Microsoft app consent prompt.

The following video describes the process:

Publisher verification primarily is for developers who build multitenant apps that use OAuth 2.0 and OpenID Connect with the Microsoft identity platform. These types of apps can sign in a user by using OpenID Connect, or they can use OAuth 2.0 to request access to data by using APIs like Microsoft Graph.


Publisher verification for an app has the following benefits:

  • Increased transparency and risk reduction for customers. Publisher verification helps customers identify apps that are published by developers they trust to reduce risk in the organization.

  • Improved branding. A blue verified badge appears in the Microsoft Entra app consent prompt, on the enterprise apps page, and in other app elements that users and admins see.

  • Smoother enterprise adoption. Organization admins can configure user consent policies that include publisher verification status as primary policy criteria.


Beginning November 2020, if risk-based step-up consent is enabled, users can't consent to most newly registered multitenant apps that aren't publisher verified. The policy applies to apps that were registered after November 8, 2020, which use OAuth 2.0 to request permissions that extend beyond the basic sign-in and read user profile, and which request consent from users in tenants that aren't the tenant where the app is registered. In this scenario, a warning appears on the consent screen. The warning informs the user that the app was created by an unverified publisher and that the app is risky to download or install.


App developers must meet a few requirements to complete the publisher verification process. Many Microsoft partners will have already satisfied these requirements.

  • The developer must have a Partner One ID for a valid Microsoft Cloud Partner Program account that has completed the verification process. The CPP account must be the partner global account (PGA) for the developer's organization.


    The CPP account you use for publisher verification can't be your partner location Partner One ID. Currently, location Partner One IDs aren't supported for the publisher verification process.

  • The app that's to be publisher verified must be registered by using a Microsoft Entra work or school account. Apps that are registered by using a Microsoft account can't be publisher verified.

  • The Microsoft Entra tenant where the app is registered must be associated with the PGA. If the tenant where the app is registered isn't the primary tenant associated with the PGA, complete the steps to set up the CPP PGA as a multitenant account and associate the Microsoft Entra tenant.

  • The app must be registered in a Microsoft Entra tenant and have a publisher domain set. The feature is not supported in Azure AD B2C tenant.

  • The domain of the email address that's used during CPP account verification must either match the publisher domain that's set for the app or be a DNS-verified custom domain that's added to the Microsoft Entra tenant. (NOTE__: the app's publisher domain can't be * to be publisher verified)

  • The user who initiates verification must be authorized to make changes both to the app registration in Microsoft Entra ID and to the CPP account in Partner Center. The user who initiates the verification must have one of the required roles in both Microsoft Entra ID and Partner Center.

    • In Microsoft Entra ID, this user must be a member of one of the following roles: Application Admin, Cloud Application Admin, or Global Administrator.

    • In Partner Center, this user must have one of the following roles: CPP Partner Admin, Account Admin, or Global Administrator (a shared role that's mastered in Microsoft Entra ID).

  • The user who initiates verification must sign in by using Microsoft Entra multifactor authentication.

  • The publisher must consent to the Microsoft identity platform for developers Terms of Use.

Developers who have already met these requirements can be verified in minutes. No charges are associated with completing the prerequisites for publisher verification.

Publisher verification in national clouds

Publisher verification currently isn't supported in national clouds. Apps that are registered in national cloud tenants can't be publisher verified at this time.

Frequently asked questions

Review frequently asked questions about the publisher verification program. For common questions about requirements and the process, see Mark an app as publisher verified.

  • What does publisher verification not tell me about the app or its publisher? The blue verified badge doesn't imply or indicate quality criteria you might look for in an app. For example, you might want to know whether the app or its publisher have specific certifications, comply with industry standards, or adhere to best practices. Publisher verification doesn't give you this information. Other Microsoft programs, like Microsoft 365 App Certification, do provide this information. Verified publisher status is only one of the several criteria to consider while evaluating the security and OAuth consent requests of an application.

  • How much does publisher verification cost for the app developer? Does it require a license? Microsoft doesn't charge developers for publisher verification. No license is required to become a verified publisher.

  • How does publisher verification relate to Microsoft 365 Publisher Attestation and Microsoft 365 App Certification? Microsoft 365 Publisher Attestation and Microsoft 365 App Certification are complementary programs that help developers publish trustworthy apps that customers can confidently adopt. Publisher verification is the first step in this process. All developers who create apps that meet the criteria for completing Microsoft 365 Publisher Attestation or Microsoft 365 App Certification should complete publisher verification. The combined programs can give developers who integrate their apps with Microsoft 365 even more benefits.

  • Is publisher verification the same as the Microsoft Entra application gallery? No. Publisher verification complements the Microsoft Entra application gallery, but it's a separate program. Developers who fit the publisher verification criteria should complete publisher verification independently of participating in the Microsoft Entra application gallery or other programs.

Next steps