Publisher verification is broken on Entra Apps in Azure

Question

Using our Microsoft Partner id to perform publisher verification for an Entra app in Azure is broken and has been reporting a temporary problem going on 4+ hours.

Answer 1

Hello Jim,

If publisher verification using the Microsoft Partner ID has been returning a “temporary problem” consistently for several hours, this is worth treating as a possible service-side issue rather than repeatedly changing the app configuration.

A few checks can help isolate where the failure occurs:

Confirm that the Partner ID being used is associated with the correct Microsoft Partner Center account and organization.

Verify that the signed-in Entra account has the required permissions to configure publisher verification for the application.

In Microsoft Entra admin center → App registrations → Branding & properties, confirm that the publisher information and verified publisher configuration are being applied to the intended app.

Try the operation from an InPrivate/Incognito session or another browser to rule out a stale portal session.

If possible, test with another application in the same tenant. If multiple applications fail with the same temporary error, that provides stronger evidence of a service-side problem.

Check Azure Service Health for your tenant and the Microsoft Entra service for any active incidents.

If the error continues after these checks, open a Microsoft support request and include the tenant ID, application/client ID, Partner ID, exact error message, UTC timestamps, and correlation/request ID shown by the portal. Do not post those identifiers publicly in the Q&A thread.

Because publisher verification involves validation between Microsoft Entra and the Microsoft Partner identity, a persistent temporary error may require Microsoft to check the backend verification transaction. Repeatedly deleting and recreating the app is therefore not recommended unless Microsoft Support specifically asks you to do so.