Guides · identity · Verification-gated
Get the blue "verified" badge on your app's Microsoft consent screen by linking a verified Microsoft AI Cloud Partner Program (MAICPP, formerly MPN) account to your Entra app registration. Without it, users in other organisations may be blocked from consenting to a newer multitenant app.
Researched · not yet run liveLast researched 25 October 2026 · Microsoft · provider site
Two accounts must line up: the Entra tenant that owns the app registration, and a Microsoft AI Cloud Partner Program account in Partner Center whose Partner Global Account (PGA) is associated with that tenant. The company's legal identity is checked on the partner side; the domain ties the two together.
The person who presses "Verify and save" needs Application Administrator or Cloud Application Administrator in Entra AND Partner Admin (CPP) or Accounts Admin in Partner Center, and must have done MFA in the same session.
Adding a tenant to the partner account gives all of that tenant's Global Administrators Global Admin on the Partner Center account.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Add your company domain (the one your partner email uses) as a custom domain in the tenant and complete its DNS verification. A *.onmicrosoft.com domain cannot be used for publisher verification.
Where: https://entra.microsoft.com/
In App registrations > your app > Branding & properties, set Publisher domain. Pick a verified domain of the tenant, or verify a new one by hosting a microsoft-identity-association.json file listing the app's client ID at https://{domain}/.well-known/microsoft-identity-association.json, served as application/json. This cannot be done by API.
Where: https://entra.microsoft.com/
A Global admin of the tenant goes to Partner Center > join the program, signs in with a work account in that tenant, selects the legal entity, reads and accepts the MAICPP agreement and enrolls. The person must be authorised to sign agreements for the company. If your company already has a partner account, signing in from the primary tenant adds you to it instead.
Where: https://partner.microsoft.com/dashboard/account/v3/enrollment/introduction/partnership
Microsoft checks email (primary contact's business email), identity (a government ID), employment (domain documents) and business registration (formation documents). Watch Account settings > Legal info > Verification Summary and upload what is asked. Only the primary contact receives emails. Changing legal name, address or primary contact later triggers verification again.
Where: https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo
The person who will verify needs Application Administrator or Cloud Application Administrator in Entra, and Partner Admin (CPP) or Accounts Admin in Partner Center. The tenant that owns the app must be associated with the Partner Global Account (Partner Center > tenant management).
Where: https://partner.microsoft.com/dashboard/account/v3/usermanagement
Sign in with MFA, open App registrations > your app > Branding & properties > Add Partner ID to verify publisher, enter the Partner Global Account's Partner One ID and select Verify and save. The badge appears next to the publisher display name; test with a fresh consent prompt.
MPNAccountNotFoundOrNoAccess): Check the ID, that the app's tenant is listed in Partner Center tenant management, and that you are Global Admin, MPN/CPP Admin or Accounts Admin in Partner Center. [3]MPNGlobalAccountNotFound): You used a location ID. Use the ID with type PartnerGlobal from Account settings > Identifiers. [3]MPNAccountNotVetted): Finish Partner Center verification until Legal business profile and Partner info both show authorized. [3]NoPublisherDomainOnApplication): Set a publisher domain on the app (Branding & properties). [3]PublisherDomainMismatch): Verify the primary contact's email domain in the tenant and set it as the publisher domain. [3]NotAuthorizedToVerifyPublisher): Get Application Administrator or Cloud Application Administrator in Entra. [3]MSANotSupported): Re-register the app in a tenant with a work or school account; apps registered with a Microsoft account cannot be verified. [3]InteractionRequired): Make MFA required for your user (for example by Conditional Access for admins), sign in again with MFA, and retry. [3]UserUnableToAddPublisher): Your user is flagged at risk. Remediate the user risk (for example a strong self-service password reset), wait, then retry. [3]UnableToAddPublisher): The request was judged risky; Microsoft does not say why. Try again the next day. [3]Where: https://aka.ms/PublisherVerificationPreview
Plain-English summary, not legal advice. Each card links its source.
Where risk-based step-up consent is on, users cannot consent to most multitenant apps registered after 8 November 2020 that are not publisher verified and ask for more than basic sign-in and profile permissions in another tenant. Plan verification before launching to other organisations. [1]
Enrolling accepts the MAICPP agreement. The enrollee must have authority to sign for the organisation and be able to produce legal documents during verification. [5]
Verification only confirms who the publisher is. It says nothing about app quality or compliance; Microsoft 365 Publisher Attestation and App Certification are separate programmes. [1]
Microsoft may suspend or terminate access to its APIs at any time and for any reason; keep your registration accurate. [7]
People report Partner Center business verification stuck far longer than the stated three to five business days, with support hard to reach. Start this weeks before you need the badge. [8]
People report that a sole trader using a trading name as the publisher name is not accepted (Tech Community). [10]
Source [1]
The same entry as JSON: /api/v1/entries/microsoft/publisher-verification · requirements /api/v1/requirements/microsoft/publisher-verification · terms /api/v1/terms/microsoft/publisher-verification.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Microsoft Entra publisher verification, and how long will it take?"
→ tools/call requirements { "provider_id": "microsoft/publisher-verification" }Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Microsoft is not affiliated with verapli.