adding MPN ID to verify publisher error

Joseph Ogirima 0 Reputation points
2026-10-05T18:56:03.04+00:00

Hello team,

I'm getting the error below when I try adding an MPN ID to verify the publisher; I keep getting the error message below. I have tried every suggested troubleshooting step, but it keeps failing.

"There is a temporary problem with the service. Please try again later. If you continue to get this message, try again later. [2BbYCFJbHfQ4kfrBqTFTYM]"

Microsoft Partner Center API
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-05T18:56:18.5833333+00:00

    For this generic temporary service error during publisher verification, the supported troubleshooting path is:

    1. Recheck all publisher verification prerequisites.
      • Confirm the app registration meets the publisher verification requirements.
      • Confirm the steps to mark the app as publisher verified were completed successfully.
    2. Validate the Partner One ID being used.
      • In Partner Center, open the partner profile > Identifiers > Microsoft Cloud Partners Program.
      • Use the Partner ID with type PartnerGlobal.
      • If a location-based or incorrect Partner ID is used, verification can fail.
    3. Confirm the Partner Center account is fully vetted.
      • In the partner profile, verify there are no errors or pending actions.
      • The verification status under Legal business profile and Partner info must show authorized or success.
    4. Confirm tenant association and role assignments.
      • In the CPP tenant management page, verify the tenant where the app is registered is listed as an associated tenant.
      • In the CPP user management page, verify the signed-in account has one of these Partner Center roles: Global Administrator, MPN Admin, or Accounts Admin.
      • In Microsoft Entra ID, verify the signed-in account has an eligible admin role such as Cloud Application Administrator when setting the verified publisher.
    5. Check domain alignment.
      • The domain used for email verification in Partner Center must match the app’s Publisher Domain or a verified custom domain in the Microsoft Entra tenant.
      • In Microsoft Entra admin center, go to Entra ID > App registrations > Branding and Properties > Update Publisher Domain and verify the correct domain if needed.
    6. Ensure MFA is performed in the same session.
      • MFA must be enabled and required for the signed-in user for this scenario.
      • If MFA is enabled but not actually required/performed in that session, publisher verification can fail.
    7. Reproduce the operation with Graph Explorer.
      • This is the documented next step to gather more information and rule out a portal UI issue.
    8. If the app is being deployed through Bicep, do not set verifiedPublisher.publisherVerificationId during application creation.
      • The verifiedPublisher property is read-only at creation time.
      • Create the application first, then use Microsoft Graph REST API, CLI, or PowerShell to set the verified publisher.

    The error text shown is not listed in the documented error reference, so the practical next step is to use Graph Explorer to reproduce the request and identify whether one of the documented conditions above is the underlying cause.

    References:

    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.