Publisher verification fails with "There's a temporary problem with the service" for a verified Partner ID

Hans 0 Reputation points
2026-11-21T15:30:53.9733333+00:00

I'm trying to verify the publisher of a multitenant app registration, but every time I click Verify and save I get a generic error:

  ▎ There's a temporary problem with the service. Please try again.

  Correlation ID: kTpAh42G1Qi0hY3KI2gsT5User's image

It has failed four times on 21 November 2026, on different attempts several hours apart. Nothing is saved, and the publisher display name still says "Not provided".

What I'm doing

  • Entra admin centre → App registrations → (app) → Branding & properties → Add MPN ID to verify publisher
  • Partner ID: 7194822 (the PartnerGlobal ID, not the location ID). The form accepts it, shows a green check, and I tick the Microsoft Platform Policies box.

What I've checked

  • Partner Center sent the "We've successfully verified your Partner Center profile" email on 20 November 2026. Contact, Identity and Business verification are all Verified.
  • The app is in the same Entra tenant that is linked to the Partner Center account. 
  • The app's publisher domain is a verified custom domain in that tenant, and it matches the domain on the Partner Center account.
  • The signed-in user is a work account in that tenant, with Account admin and Microsoft AI Cloud Partner Program partner admin roles in Partner Center.
  • The app is single-registration multitenant, not a personal Microsoft account app.

  

Questions

  1. What is the actual error behind this correlation ID?
  2. Is there a propagation delay after Partner Center verification completes before publisher verification works? If so, roughly how long?
  3. Does the signing-in user also need a specific Entra role on the app, such as owner or Application Administrator, or a session that includes MFA? The error message doesn't say.
Microsoft Partner Center | Other
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-22T08:35:33.94+00:00

    The verification must be performed by a user holding Application Administrator or Cloud Application Administrator in Microsoft Entra, with MFA completed in that same sign-in session; Partner Center roles alone are insufficient.^1^

    Retry with the required identity context

    Your Partner Center Account Admin role qualifies, but app ownership by itself is not the documented Entra authorization requirement.

    1. In Entra admin center → Identity → Roles & admins, assign the same user either:
      • Application Administrator, or
      • Cloud Application Administrator.
    2. Sign out of the Entra admin center completely, then use a private browser window to prevent an older session from being reused.
    3. Sign in with that work account and explicitly complete MFA during this new session. MFA being registered or enabled is not enough if it was not performed in the session used for publisher verification; this condition can produce an InteractionRequired failure.^2^
    4. Return to App registrations → your app → Branding & properties → Add Partner ID to verify publisher.
    5. Enter the PartnerGlobal ID, accept the terms, and select Verify and save.

    Success should return you to Branding & properties, where the publisher display name has a blue verified badge.^3^

    Expose the backend error with Microsoft Graph

    A correlation ID cannot be decoded from the portal or publicly looked up. Microsoft Support can correlate it with backend telemetry when supplied with the corresponding UTC timestamp and tenant details. Before escalating, reproduce the operation through Graph Explorer, which Microsoft specifically recommends when the portal only reports unexpected behavior.^2^

    Use the app registration’s Object ID, not its client ID:

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

    The API also permits addressing the application by appId; a successful request returns 204 No Content.^4^

    In Graph Explorer:

    1. Sign in as the same role-enabled user and complete MFA.
    2. Consent only to the delegated Microsoft Graph permission Graph Explorer requests for this operation. The available documentation here does not specify the exact OAuth scope, so do not grant unrelated permissions speculatively.
    3. Submit the request and retain the complete HTTP status and JSON response.
    4. If it succeeds, refresh Branding & properties. If it fails, the response should provide a more useful code such as:
      • InteractionRequired — MFA was not performed in this session.
      • MPNAccountNotFoundOrNoAccess — Partner role, associated tenant, account state, or Partner ID issue.
      • MPNAccountNotVetted — Partner Center still reports incomplete backend vetting.
      • PublisherDomainMismatch — domain alignment failed.
      • MPNGlobalAccountNotFound — a location ID was supplied instead of the PartnerGlobal ID.

    Do not repeatedly unset and reset the verified publisher if Graph reports success; unset changes the app’s publisher-verification state.

    Propagation after Partner Center verification

    Microsoft does not document a fixed post-verification synchronization delay before this operation can be started. It states that developers who satisfy all requirements can be verified in minutes, and that the verification request itself can take a few minutes.^1^ Replication delay is mentioned only after publisher verification succeeds, for the badge to appear across the system.^3^

    Therefore, there is no supported “wait 24/48 hours” estimate for your completed Partner Center verification. If Graph returns MPNAccountNotVetted, check Partner Center → Account settings → Legal info/Partner info for pending actions and ensure the relevant statuses are authorized or success; otherwise, waiting alone is not a documented resolution.^2^

    If it still fails

    There was another report of this exact generic publisher-verification message on November 21, 2026, but that report does not establish a Microsoft-wide incident.^5^

    Open a Microsoft Entra support request if the same-session MFA/role retry and Graph request still fail. Include:

    • Correlation ID from each attempt—the question and screenshot show different IDs.
    • Exact UTC timestamp for each ID.
    • Tenant ID and application Object ID.
    • HTTP status and complete Graph error response.
    • Confirmation that the user held the required Entra and Partner Center roles.
    • Browser/network trace if requested, after removing sensitive data.

    The Entra support flow is available to a Service Support Administrator through the Entra admin center’s new-support-request path.^6^


    References

    1. Publisher verification
    2. Troubleshoot publisher verification
    3. Mark your app as publisher verified
    4. application: setVerifiedPublisher
    5. Publisher verification fails with "There's a temporary problem with the service" for a verified Partner ID - Microsoft Q&A
    6. Find help and get support for Microsoft Entra
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Hans 0 Reputation points
    2026-11-22T08:55:23.4833333+00:00

    setVerifiedPublisher returns 400 Request_BadRequest, "A value is required for property 'displayName' of resource 'Application'" (request-id a234bb89-23b0-435e-90ba-9c832d4a5ac1, 2026-11-22T08:46:29Z). The app's displayName is "Odin by Borg", and Partner Center shows company name "Borg Security AS", Authorized.

    Was this answer helpful?

    0 comments No 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.