Publisher verification fails: Partner Center tenants page blank, AI Cloud Partner Program stuck in "Pending qualification" since 23 Sep

Lewis Seaborne 0 Reputation points
2026-10-22T23:43:02.1466667+00:00

PartnerGlobal ID 7164152 (Nexborne Ltd, UK). App: 58e8a1a7-5130-44b3-9efd-55517b168099.

Publisher verification fails every time with "There's a temporary problem with the service" [cCftgcyj28NOt53OY6bO2j], and earlier [R7Z54km7w8oghuw4M8aehu].

Microsoft's own checklist for this error passes on everything except two items we cannot change:

  1. Partner Center > Account settings > Tenants is blank. Our Entra tenant cec9fd6e-1f82-46c0-8795-b72df2e698af (Nexborne Ltd) is not listed, and there is no option to add it.
  2. Program info shows "Microsoft AI Cloud Partner Program status: Pending qualification" since 23 Sep 2026.

Everything else is done: legal business profile Authorized (vetting case 2610050050003647, 8 Oct), program agreement accepted 23 Sep, signed in as ******@nexborne.co.uk (Global Admin in Entra, Account Admin in Partner Center), nexborne.co.uk DNS-verified and matching the vetting email domain, correct PartnerGlobal ID.

Our support case was closed by the Vetting team as outside their scope, and the Partner Center support form only offers AI answers. Could a moderator route this to the team that handles tenant association and program enrolment?

Microsoft Partner Center | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-10-22T23:44:22.0033333+00:00

    A Microsoft Q&A moderator cannot directly associate the tenant or complete the program enrollment; create a Partner Center support request and ask for routing to MAICPP account enrollment/verification and tenant management, because both documented publisher-verification prerequisites are currently unmet.

    Submit the request through the AI assistant

    The AI assistant is now the entry point to human Partner Center support:

    1. Sign in to Partner Center with the affected work account.
    2. Open the AI assistant icon in the upper-right corner.
    3. Enter a detailed problem statement using the template below.
    4. After the assistant responds, select Contact Support at the bottom.
    5. Choose the Membership or Account settings workspace and the closest problem type concerning enrollment, verification, or tenant management.
    6. Select Review solutions, then Create support request.
    7. Submit it and retain the resulting service-request number.

    Contact Support only appears after describing the issue; the assistant itself is not the final support channel. This is Microsoft’s documented route for creating a Partner Center request.^1^

    Suggested request text:

    Subject: MAICPP enrollment pending and Tenants page blank—publisher verification blocked

    Legal business profile is Authorized, but Microsoft AI Cloud Partner Program status has remained Pending qualification since 23 September 2026.

    Account settings > Tenants is blank and does not offer Associate Microsoft Entra ID, so the Entra tenant containing the app registration cannot be associated with the Partner Global Account. Publisher verification then returns “There’s a temporary problem with the service,” with correlation/reference codes and timestamps attached.

    Please route this request to the team responsible for MAICPP enrollment/account verification and Partner Center tenant association. Please:

    1. determine why the MAICPP enrollment has not transitioned to Active;
    2. repair or complete the Partner Center-to-Entra tenant association;
    3. confirm that the PartnerGlobal ID is enabled for publisher verification.

    Attach screenshots of Program info, the blank Tenants page, the publisher-verification error, and Verification Summary. Include the PartnerGlobal ID, Entra tenant ID, app client ID, UTC timestamps, correlation codes, and the closed vetting case number in the private support request.

    Do not post tenant IDs, app IDs, or case details again in the public thread.

    Why this requires account-side correction

    Publisher verification requires:

    • a verified MAICPP account using its Partner Global Account ID;
    • the Entra tenant containing the app to be associated with that PGA;
    • the required Entra and Partner Center roles;
    • a matching verified domain and MFA.^2^

    Microsoft’s troubleshooting guidance specifically says that a missing tenant association can produce Partner-account access errors and instructs partners to verify the association on the CPP tenant-management page.^3^

    Your domain, PartnerGlobal ID, legal-business authorization, and administrator checks are already complete, so repeating those checks is unlikely to move this case forward. The two unresolved account states are the relevant blockers.

    Microsoft also documents that Pending MAICPP status means account verification failed or remains unresolved, whereas Active identifies an active MAICPP enrollment.^4^ Enrollment becomes Active only after vetting is Authorized, but status changes can take time to propagate across Partner Center.^5^ Given the elapsed time and blank tenant-management page, this is no longer a normal propagation delay.

    If support asks you to associate the tenant manually

    The documented path is:

    1. Partner Center → Settings → Account settings → Tenants
    2. Select Associate Microsoft Entra ID.
    3. Sign in as Global Administrator of the tenant being associated.
    4. Select Confirm.
    5. Confirm that All set appears and return to tenant management.^6^

    A tenant cannot be associated with more than one Partner Center account. If support determines that it is already attached elsewhere, Microsoft must identify the applicable account-side resolution; do not remove or recreate the Entra tenant.

    Because your Tenants page is blank and does not expose Associate Microsoft Entra ID, this manual procedure is currently unavailable and should be documented in the ticket rather than repeatedly retried.

    Optional diagnostic for the support case

    If requested, reproduce publisher verification in Graph Explorer. Use the application’s Object ID, not its client/application ID:

    POST https://graph.microsoft.com/v1.0/applications/{application-object-id}/setVerifiedPublisher
    Content-Type: application/json
    
    {
      "verifiedPublisherId": "{PartnerGlobal-ID}"
    }
    

    A success response is 204 No Content. Otherwise, provide the complete Graph error code, request ID, timestamp, and response body to support. Microsoft documents this method specifically for obtaining a more precise error when the portal only shows generic behavior.^3^


    References

    1. Get help and contact support in Partner Center
    2. Publisher verification overview - Microsoft identity platform
    3. Troubleshoot publisher verification
    4. Learn about the Microsoft Partner Agreement (MPA) for CSP program partners
    5. Understand the verification process in Partner Center
    6. Add and manage multiple tenants in your Partner Center account
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.