Microsoft Store Individual Account — Policy 10.14 Clarification and Engage Center Support Issue

A Company developer account is required if “MALMIN RUDRA TECHWORKS” would reasonably be understood as a business or trade name, and using a free or private-audience release does not create an exception to Policy 10.14.^1^

Account type and compliant procedure

Policy 10.14 requires a Company account when:

• The publisher or application name would reasonably be interpreted as a business entity.
• Distribution relates to a business, trade, or profession.
• The product requires financial information for its primary functionality.

Individual accounts are intended for a single developer publishing under their own name, where Store distribution is unrelated to business, trade, or profession.^1^

Because “MALMIN RUDRA TECHWORKS” appears business-styled, the compliant course is:

1. Do not submit the app under that publisher identity from the Individual account while the account-type question remains unresolved.
2. Create a new Company developer account through https://storedeveloper.microsoft.com.
3. Select Company account and sign in with either a personal Microsoft account or Microsoft Entra work account.
4. Complete business verification using a D‑U‑N‑S number or official business documents, plus the requested organization and contact information.
5. Wait for all verification stages to complete before submitting the app.

Partner Center does not support converting an Individual account into a Company account. Publishing as a company requires creating a new Company developer account; both account types are currently free through the supported onboarding entry point.^2^^3^

Creating the required Company account does not inherently require deleting the existing Individual account. However, use only the correctly classified account for this publisher and product. The available documentation does not describe transferring an unpublished product reservation, publisher name, or registration history between these accounts; ask Dev Center support about those details before reserving or submitting the product again.

Conditional alternative: If this is genuinely a personal, nonprofessional project, an Individual account may be appropriate only when publishing under your own name rather than a business-style identity. Partner Center exposes the account type and publisher display name under the developer account details, and contact information can be updated there.^4^ Changing the display name alone does not make business-related distribution eligible for an Individual account.

Private-audience submission

A private audience controls who can see and acquire the app; it does not waive publisher-account policy. Therefore, it should not be used to bypass or defer the Policy 10.14 issue.

Once the correct account is verified, configure private testing in the submission at:

1. Pricing and availability → Visibility → Audience
2. Select Private audience.
3. Select or create a known user group.
4. Add each tester’s personal Microsoft-account email address.
5. Submit for certification and provide testers with the private authenticated listing link.

Testers must use personal Microsoft accounts, not work or school accounts. An app initially published to a private audience can later be changed to public, potentially requiring additional certification. A product submitted as public cannot later be changed back to private.^5^

Engage Center support

For an Individual Store developer using a personal Microsoft account, use Microsoft’s MSA-specific Dev Center support link, not the Entra ID link:

Open Dev Center support for MSA users

This is the documented private support route for Store publisher enrollment, account management, submissions, certification, and related issues.^6^ It is a direct MSA entry into the same Engage Center service, not a separate support system.

If that exact MSA route loads enough to display the header:

1. Select the question-mark icon.
2. Open Engage Center Help.
3. Under How can we help?, report that the MSA Dev Center experience remains stuck loading and request assistance with the Engage Center platform.

Microsoft documents this as the escalation path for Engage Center website problems and says responses are provided by email.^7^

If the page never renders the header or help control, the public Store-publisher documentation does not identify another equivalent private Dev Center ticket portal. The certification email listed on the support page is only appropriate after a specific app certification failure, not for an account-type policy clarification.^6^

References

1. Microsoft Store Policies
2. Set up your Microsoft Store developer account early
3. Steps to open a developer account
4. Manage a Microsoft Marketplace account in Partner Center
5. Choose visibility options for MSIX apps
6. Help and guidance for Windows developers
7. Microsoft Engage Center help