Microsoft Store personal-account support: Engage Center access blocked

Use the question-mark icon on the Engage Center “No Access” page, open How can we help?, and submit an Engage Center access case; Microsoft documents this as the free support channel for Engage Center website and platform problems, with no support contract required.^1^

Submit the access case

1. Return to the Engage Center page that displays No Access.
2. Select the ? icon in the top navigation.
3. Open How can we help? and request additional assistance or create a case.
4. Classify it as an Engage Center website/access issue, not as an app-certification appeal.
5. Include:
   • Personal Microsoft account (MSA) used for the Individual Store developer account.
   • Partner Center Apps & Games workspace is accessible.
   • The MSA Dev Center support link redirects to Engage Center.
   • Engage Center reports No Access / no workspace permissions.
   • The alternate MSA form remains on loading dots.
   • Browser, timestamp with time zone, screenshots, and any correlation/session ID shown.
   • Request restoration of access to the Dev Center support intake for Store publishers.

Do not put the account address, publisher identifiers, identity documents, or application records in a public Q&A post. Supply them only after the support case provides a private reply channel.

This Engage Center help service is specifically for Engage Center platform and feature issues. Microsoft says it is free, is provided by email, and typically responds within eight business hours, although that response time is not contractual.^1^

If the help control is unavailable

Microsoft documents a direct initialization link for an MSA that errors during its first Engage Center sign-in, particularly when that MSA was previously associated with an inactive Entra tenant:

https://engagecenter.microsoft.com/f8cdef31-a31e-4b4a-93e4-5f571e91255a

Open that exact link in a fresh browser session and select the same personal account used by the Store developer account. After initial sign-in succeeds, open the documented MSA users Dev Center support route again. This retry is relevant only if the direct initialization completes; otherwise, it is the same failed path and should not be repeated.^2^

The Windows developer documentation confirms that Store publishers using an MSA have a dedicated Dev Center support link for account management, enrollment, app management, payouts, and related issues.^3^ Your pre-submission app-management and capability-eligibility questions belong in that route.

Limits of the other channels

• Individual-developer onboarding email: [Email] is restricted to problems with the new zero-fee onboarding process. Microsoft directs all other account-management, submission, certification, and analytics matters to the Store support-ticket flow, so it is not the documented channel for this request.^4^
• Certification mailbox: This is for a specific certification failure. Since no package has been submitted, it is not applicable.^3^
• Business support contract: The separate enterprise incident route requires a support contract, but that is distinct from the Store publisher Dev Center route and the free Engage Center website-help route.^3^
• Creating another tenant or changing account type: Microsoft does not document either as a prerequisite for an Individual Store developer to request Dev Center support. In fact, Individual developer enrollment requires a personal Microsoft account.^5^

No separate public Store-support recovery form is documented beyond the MSA Dev Center route. If both the MSA initialization link and the ? → How can we help? control fail, record that outcome in Microsoft Q&A under the Partner Center/Store area, but Q&A itself cannot inspect the account or create an authenticated private Store case.

References

1. Microsoft Engage Center help | Microsoft Learn
2. Microsoft account (MSA) users in Microsoft Engage Center
3. Help and guidance for Windows developers
4. Free developer registration for individual developers
5. Steps to open a developer account