Other features or issues related to Microsoft Partner Center
Email [Email] and ask the Microsoft Store onboarding team to reconcile the completed identity-verification status with the failed account-creation state.
This mailbox is specifically designated for problems with the new, free individual-developer onboarding process that begins at storedeveloper.microsoft.com.^1^
What to include
For easier account correlation, send the message from the email address associated with the personal Microsoft account used during registration, and include:
- Subject: Individual Store onboarding – identity verification completed but account creation fails
- The exact error: User identity verification required before account creation
- Confirmation that steps 1–3 show completed check marks while Account setup remains at 0%
- Approximate date, time, and time zone of the latest failure
- Country/region selected during registration
- The Microsoft-account email address used for onboarding
- A screenshot showing the completed verification step and final error
- Any correlation ID, request ID, or timestamp shown in the browser’s developer tools
- A request to inspect the onboarding record and either synchronize or reset the verification/provisioning state
Do not email copies of your ID, selfie, passwords, authentication codes, or other unnecessary sensitive data. Supply additional identity documents only through a secure Microsoft workflow if support requests them.
The documented onboarding flow requires ID verification to complete before account setup and the Partner Center handoff.^2^ Because your UI already marks verification complete, repeated retries and private browsing are unlikely to resolve the contradictory server-side state. Microsoft support may need to inspect or correct it; there is no documented self-service reset for this condition.
Fallback: create a ticket without signing in
If the onboarding mailbox does not resolve the issue, use the public Partner Center support form without signing in:
Create a Partner Center support ticket without signing in
Microsoft’s Partner Center troubleshooting documentation explicitly provides this route when Partner Center sign-in is unavailable.^3^ Describe it as a Microsoft Store individual-developer enrollment/onboarding failure and note that Engage Center cannot be used because account provisioning has not completed. The request might require manual routing to the Store developer onboarding team.
Creating an Azure or Microsoft Entra tenant solely to access Engage Center is not required for this individual-account flow. The official process uses a personal Microsoft account, while work/Entra accounts apply to company onboarding.^2^
References