Mark your app as publisher verified

When an app registration has a verified publisher, it means that the publisher of the app has verified their identity using their Cloud Partner Program (CPP) account and has associated this CPP account with their app registration. This article describes how to complete the publisher verification process.


If you're already enrolled in the Cloud Partner Program (CPP) and have met the prerequisites, you can get started right away:

  1. Sign into the App Registration portal using multifactor authentication

  2. Choose an app and select Branding & properties.

  3. Select Add Partner One ID to verify publisher and review the listed requirements.

  4. Enter your Partner One ID and select Verify and save.

For more details on specific benefits, requirements, and frequently asked questions see the overview.

Mark your app as publisher verified

Make sure you meet the prerequisites, then follow these steps to mark your app(s) as Publisher Verified.

  1. Sign in using multifactor authentication to an organizational (Microsoft Entra) account authorized to make changes to the app you want to mark as Publisher Verified and on the CPP Account in Partner Center.

    • The Microsoft Entra user must have one of the following roles: Application Admin, Cloud Application Admin, or Global Administrator.

    • The user in Partner Center must have the following roles: CPP Admin, Accounts Admin, or a Global Administrator (a shared role mastered in Microsoft Entra ID).

  2. Navigate to the App registrations blade:

  3. Select on an app you would like to mark as Publisher Verified and open the Branding & properties blade.

  4. Ensure the app’s publisher domain is set.

  5. Ensure that either the publisher domain or a DNS-verified custom domain on the tenant matches the domain of the email address used during the verification process for your CPP account.

  6. Select Add Partner One ID to verify publisher near the bottom of the page.

  7. Enter the Partner One ID for:

    • A valid Cloud Partner Program account that has completed the verification process.

    • The Partner global account (PGA) for your organization.

  8. Select Verify and save.

  9. Wait for the request to process, this may take a few minutes.

  10. If the verification was successful, the publisher verification window closes, returning you to the Branding & properties blade. You see a blue verified badge next to your verified Publisher display name.

  11. Users who get prompted to consent to your app start seeing the badge soon after you've gone through the process successfully, although it may take some time for updates to replicate throughout the system.

  12. Test this functionality by signing into your application and ensuring the verified badge shows up on the consent screen. If you're signed in as a user who has already granted consent to the app, you can use the prompt=consent query parameter to force a consent prompt. This parameter should be used for testing only, and never hard-coded into your app's requests.

  13. Repeat these steps as needed for any more apps you would like the badge to be displayed for. You can use Microsoft Graph to do this more quickly in bulk, and PowerShell cmdlets will be available soon. See Making Microsoft API Graph calls for more info.

That’s it! Let us know if you have any feedback about the process, the results, or the feature in general.

Next steps

If you run into problems, read the troubleshooting information.