Publisher verification fails with "There's a temporary problem with the service"

Question

Publisher verification fails with "There's a temporary problem with the service"

Anthony Hobbs 0

Hello,

I'm unable to complete publisher verification for a multitenant app registration. Every attempt fails with the same generic error.

App: iSOLV Inbox (app registration in our Microsoft Entra tenant)

Tenant ID: 114c7f67-6d76-4543-85aa-34d7e8951b3f

Publisher domain: isolv.net

Partner ID (MPN ID) used: 7170862 (PartnerLocation ID)

Organisation: iSolv Ltd

Steps taken:

Microsoft Entra admin centre > App registrations > iSOLV Inbox > Branding & properties > Publisher verification.
Entered Partner ID 7170862. The field accepts it with a green tick.
Ticked the Microsoft Platform Policies agreement and clicked Verify and save.

Result: "There's a temporary problem with the service. Please try again. If you continue to get this message, try again later."

This has happened on repeated attempts on 8 October 2026 (from around 10:05 UK time), including in a fresh private browser session.

I've confirmed all three prerequisites shown on the Publisher verification page:

Our organisation is enrolled in the Microsoft AI Cloud Partner Program and vetting is complete in Partner Center.
I'm signed in as ******@isolv.net, which has the Account admin role in Partner Center and is an administrator in our Entra tenant.
isolv.net is a DNS-verified custom domain in our Entra tenant, is set as the app's publisher domain, and matches the domain used during vetting in Partner Center.

Thank you,

Tony Hobbs

iSolv Ltd

******@isolv.net

0 comments

1 answer

Your answer

Answer 1

The Partner ID being used is the likely cause. Publisher verification requires the Partner ID with type PartnerGlobal. A PartnerLocation ID is not supported for publisher verification, even if the field is accepted in the UI.

Use this path to verify and retry:

In Partner Center, open the connected partner profile.
Go to Identifiers > Microsoft Cloud Partners Program.
Find the Partner ID whose type is PartnerGlobal.
In Microsoft Entra admin center, open Entra ID > App registrations > iSOLV Inbox > Branding & properties > Publisher verification.
Enter the PartnerGlobal ID, accept the agreement, and retry Verify and save.

Additional checks supported by the troubleshooting guidance:

Ensure the app registration is in a Microsoft Entra tenant, not a consumer-account registration.
Ensure isolv.net is the app’s configured publisher domain and is a verified custom domain in the same tenant.
Ensure the signed-in account has the required tenant role. The troubleshooting guidance calls out signing in as at least a Cloud Application Administrator.
If the UI continues to show only the generic temporary-service message, reproduce the operation with Microsoft Graph or Graph Explorer to get a more specific error.

For Graph-based troubleshooting:

The request must target the application object ID, not the AppId/ClientId.
The verified publisher value must be the Partner ID used for publisher verification.
A typical request format is:

POST /applications/{application-object-id}/setVerifiedPublisher
{
  "verifiedPublisherId": "<PartnerGlobal ID>"
}

If Graph returns a specific error, map it as follows:

ApplicationNotFound or ApplicationObjectisInvalid: the wrong identifier was used; use the application object ID.
Missing or invalid partner ID errors: use the PartnerGlobal ID from the connected partner profile.
NoPublisherDomainOnApplication: set the app’s publisher domain first.
InteractionRequired: MFA must be enabled and actually performed in the same session before retrying.
PublisherDomainMismatch-type scenarios: the Partner Center verified domain must match the app publisher domain or a verified custom domain in the tenant.