In this guide, you'll learn about Microsoft's publisher verification and how to complete the process.
What is publisher verification?
Microsoft's publisher verification gives application users and organization administrators information about the authenticity of the developer's organization. When the publisher of an application has been verified, a blue badge appears in the Microsoft consent prompt for the app.
If you already meet the requirements, you can complete the verification process in minutes. Microsoft doesn't charge developers for publisher verification, and you don't need a license to become a verified publisher.
Why is publisher verification required?
As of November 2020, if risk-based step-up consent is enabled, end users cannot consent to most newly registered multi-tenant applications that haven't been verified. Microsoft displays a warning on the consent page informing end users that the apps are risky because they're from unverified publishers.
Microsoft recommends restricting user consent to allow end users to consent for applications from verified publishers only, with specific permissions. For apps that don't meet this policy, your organization's IT team is responsible for making any decisions. This means that if you don't complete the verification process, you'll likely need admin consent from Microsoft 365 organizations before end users can connect their individual accounts. This can slow or block adoption.
For more information on Microsoft's publisher verification, check out Microsoft's official documentation.
Publisher verification process
To complete the publisher verification process, follow these steps:
- Create an Azure auth app for your project.
- Join the Microsoft AI Cloud Partner Program.
- Configure your app's publisher domain.
- Mark your app as publisher verified.
Your app is now verified! Make sure that you see a blue badge next to your Publisher display name, under Branding & properties.
If you run into any issues, see Microsoft's official troubleshooting steps.
