Publisher verification fails with "MPN ID has not completed the vetting process" although Partner Center account is fully verified

Haris 0 Reputation points
2026-10-15T00:48:47.0366667+00:00

Hello,

I cannot mark my multitenant Microsoft Entra app as publisher verified.

Calling setVerifiedPublisher (and using "Add MPN ID to verify publisher" in the portal) returns:

"The MPN ID (7168720) you provided has not completed the vetting process. Please complete this process in Partner Center and try again."

But in Partner Center everything is verified:

  • Legal profile verification status: Authorized
  • Verification summary: contact, identity and business verification all "Verified" (completed on 10 October 2026)
  • Microsoft AI Cloud Partner Program status: Active
  • Partner Program agreement accepted, no pending action
  • My user has Global admin and MPN partner admin roles in Partner Center
  • The Entra tenant of the app is associated in Partner Center (Tenants page)
  • The app's publisher domain matches the domain of the verified Partner Center email

I used the PartnerGlobal ID. It has now been 5 days since verification completed. The vetting status does not seem to have synced to the publisher verification service.

Could a Microsoft engineer refresh the vetting status of this MPN ID, or tell me what is still missing?

Thank you.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Palanikumar Annamalai 0 Reputation points
    2026-10-15T14:32:19.5066667+00:00

    The message is returned before Entra can attach the Partner ID to the app, so this is normally a Partner global account (PGA) eligibility/association check rather than an app API permission problem. An Authorized legal profile is necessary, but it does not by itself prove that the exact Partner ID supplied to publisher verification is the eligible PGA record seen by that service.

    Please verify these items in this order:

    1. In Partner Center Account settings > Organization profile > Identifiers, confirm that 7168720 is the Partner global ID / PGA, not a location Partner ID. Microsoft explicitly states that location Partner IDs are not supported for publisher verification.
    2. Confirm that the app is registered in a Microsoft Entra tenant by a work or school account. An app registered by a personal Microsoft account cannot be publisher verified.
    3. In Partner Center Account settings > Tenants, confirm the app-registration tenant is associated with that same PGA. Merely seeing the tenant in Partner Center is not sufficient if it is attached to a different partner/location record.
    4. Use one work account that has Application Administrator or Cloud Application Administrator in Entra and Microsoft AI Cloud Partner Program Partner Admin or Account Admin in Partner Center. Start a fresh MFA-authenticated session before retrying. Global Administrator alone does not replace the documented Partner Center role requirement.
    5. Confirm the app publisher domain is not onmicrosoft.com and that it either matches the domain used for Partner Center verification or is a DNS-verified custom domain in the app tenant.
    6. In Legal info > Verification Summary, check every verification component for the specific Microsoft AI Cloud Partner Program enrollment, including any additional-verification step. Partner Center notes that changes can take time to propagate and that only the primary contact receives requests for additional information.

    Official requirements:

    Since you have already waited five days and report that every item is satisfied, the next useful step is a Partner Center support case, not repeated setVerifiedPublisher calls. Include privately:

    • Partner global ID and Partner Center account/enrollment name;
    • Entra tenant ID and app object/application ID;
    • publisher domain;
    • UTC time of the latest failed request;
    • the full Graph error response, including request/correlation identifiers;
    • screenshots of the PGA identifier, tenant association, role assignments, and Verification Summary.

    Ask support to validate the publisher-verification eligibility/vetting state for the PGA and its association with the app tenant. Do not publish those identifiers or screenshots in this public thread. Only Microsoft can inspect or refresh the back-end vetting record.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.