Other features or issues related to Microsoft Partner Center
Use the dedicated MSA/personal-account Dev Center support link, rather than selecting the generic “Support for Business” workspace:
Microsoft identifies this as the Store-publisher support route for personal Microsoft accounts and uses it for Partner Center account management, enrollment, app management, payouts, and related Dev Center issues.^1^
Create the developer support case
- Sign out of Engage Center.
- Open the link above and sign in with the same personal Microsoft account that owns the Store developer account.
- Go to Help + Support.
- Select the Store/Dev Center product. If it is not initially listed, select Find another product.
- Choose the closest problem type and subtype, answer the scoping questions, and select Create a support request.^2^
- In the request, include:
- “Individual Microsoft Store developer using an MSA/personal account.”
- Partner Center works and app submissions are accessible.
- Engage Center initially reports No Access.
- The Support for Business workspace remains loading after Save.
- Approximate time and time zone of the latest failure.
- Screenshots of both states.
- The affected page URL, but no passwords, verification codes, or other sensitive credentials.
The direct MSA link is important here: the Store-publisher documentation provides separate Engage Center entry points for Entra ID users and MSA users.^1^
If the dedicated MSA route also remains stuck
Treat that as an Engage Center platform-access problem, not as a Store app-submission request:
- On any Engage Center page that loads, select the question-mark icon at the top.
- Open Engage Center Help.
- Under How can we help?, request assistance or open a case.
- Ask for the personal Microsoft account’s Dev Center support workspace access to be corrected, and attach the evidence listed above.
Microsoft documents this section specifically for obtaining assistance with Engage Center itself; support is provided by email, with a typical response target of eight business hours.^3^
Suggested summary:
MSA Store developer cannot access Dev Center support workspace
I can access Partner Center and manage Store app submissions with this personal Microsoft account. The Dev Center support link displays “No Access,” and selecting and saving “Support for Business” leaves Engage Center loading indefinitely. A private browser session produces the same result. Please correct or provision access to the MSA Dev Center support workspace.
Since private browsing has already produced the same result, repeating cache, cookie, or incognito troubleshooting is unlikely to provide a new diagnostic result. Do not use the Entra-ID Store-publisher link unless the developer account is actually owned through an organizational Entra identity.
References