Other features or issues related to Microsoft Partner Center
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.
- In Entra admin center → Identity → Roles & admins, assign the same user either:
- Application Administrator, or
- Cloud Application Administrator.
- Sign out of the Entra admin center completely, then use a private browser window to prevent an older session from being reused.
- 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
InteractionRequiredfailure.^2^ - Return to App registrations → your app → Branding & properties → Add Partner ID to verify publisher.
- 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:
- Sign in as the same role-enabled user and complete MFA.
- 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.
- Submit the request and retain the complete HTTP status and JSON response.
- 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