Publisher verification

Publisher verification helps admins and end users understand the authenticity of application developers integrating with the Microsoft identity platform.

When an application is marked as publisher verified, it means that the publisher has verified their identity using a Microsoft Partner Network account that has completed the verification process and has associated this MPN account with their application registration.

A blue "verified" badge appears on the Azure AD consent prompt and other screens:

Consent prompt

This feature is primarily for developers building multi-tenant apps that leverage OAuth 2.0 and OpenID Connect with the Microsoft identity platform. These apps can sign users in using OpenID Connect, or they may use OAuth 2.0 to request access to data using APIs like Microsoft Graph.


Publisher verification provides the following benefits:

  • Increased transparency and risk reduction for customers- this capability helps customers understand which apps being used in their organizations are published by developers they trust.

  • Improved branding- a “verified” badge appears on the Azure AD consent prompt, Enterprise Apps page, and additional UX surfaces used by end users and admins.

  • Smoother enterprise adoption- admins can configure user consent policies, with publisher verification status as one of the primary policy criteria.


  • Starting in November 2020, end users will no longer be able to grant consent to most newly registered multi-tenant apps without verified publishers if risk-based step-up consent is enabled. This will apply to apps that are registered after November 8, 2020, use OAuth2.0 to request permissions beyond basic sign-in and read user profile, and request consent from users in different tenants than the one the app is registered in. A warning will be displayed on the consent screen informing users that these apps are risky and are from unverified publishers.


There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are:

  • An MPN ID for a valid Microsoft Partner Network account that has completed the verification process. This MPN account must be the Partner global account (PGA) for your organization. (NOTE: It can't be the Partner Location MPN ID. Location MPN IDs aren't currently supported)

  • The application to be publisher verified must be registered using a Azure AD account. Applications registered using a Microsoft personal account aren't supported for publisher verification.

  • The Azure AD tenant where the app is registered must be associated with the Partner Global account. If it's not the primary tenant associated with the PGA, follow the steps to set up the MPN partner global account as a multi-tenant account and associate the Azure AD tenant.

  • An app registered in an Azure AD tenant, with a Publisher Domain configured.

  • The domain of the email address used during MPN account verification must either match the publisher domain configured on the app or a DNS-verified custom domain added to the Azure AD tenant.

  • The user performing verification must be authorized to make changes to both the app registration in Azure AD and the MPN account in Partner Center.

    • In Azure AD this user must be a member of one of the following roles: Application Admin, Cloud Application Admin, or Global Admin.

    • In Partner Center this user must have of the following roles: MPN Partner Admin, Account Admin, or a Global Admin (this is a shared role mastered in Azure AD).

  • The user performing verification must sign in using multi-factor authentication.

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

Developers who have already met these pre-requisites can get verified in a matter of minutes. If the requirements have not been met, getting set up is free.

National Clouds and Publisher Verification

Publisher verification is currently not supported in national clouds. Applications registered in national cloud tenants can't be publisher-verified at this time.

Frequently asked questions

Below are some frequently asked questions regarding the publisher verification program. For FAQs related to the requirements and the process, see mark an app as publisher verified.

  • What information does publisher verification not provide? When an application is marked publisher verified this does not indicate whether the application or its publisher has achieved any specific certifications, complies with industry standards, adheres to best practices, etc. Other Microsoft programs do provide this information, including Microsoft 365 App Certification.

  • How much does this cost? Does it require any license? Microsoft does not charge developers for publisher verification and it does not require any specific license.

  • How does this relate to Microsoft 365 Publisher Attestation? What about Microsoft 365 App Certification? These are complementary programs that developers can use to create trustworthy apps that can be confidently adopted by customers. Publisher verification is the first step in this process, and should be completed by all developers creating apps that meet the above criteria.

    Developers who are also integrating with Microsoft 365 can receive additional benefits from these programs. For more information, refer to Microsoft 365 Publisher Attestation and Microsoft 365 App Certification.

  • Is this the same thing as the Azure AD Application Gallery? No- publisher verification is a complementary but separate program to the Azure Active Directory application gallery. Developers who fit the above criteria should complete the publisher verification process independently of participation in that program.

Next steps