How to Follow Microsoft Store Developer Submission Guidelines for a Successful App Submission

To submit your first app to the Microsoft Store, you need to meet specific eligibility and account requirements, prepare your app package correctly, and follow Microsoft’s certification policies. This guide explains what you need before submitting, the detailed submission process, key compliance rules, and how to manage age ratings, content policies, and technical requirements. Following these steps carefully will help you avoid common mistakes and ensure a smoother review and publishing experience.

What do I need before submitting my app to the Microsoft Store?

Before submitting your app, confirm you meet these eligibility criteria and have all required accounts and materials ready:

• A Microsoft Developer Account registered in the Microsoft Partner Center; this account is necessary to submit and manage your apps.
• A complete developer profile with accurate personal or company information, including payment and tax details if you plan to sell your app or offer in-app purchases.
• Your app must be developed with supported technologies and target Windows versions specified by Microsoft.
• Prepare all app assets such as icons, screenshots, and a detailed, clear app description.
• Ensure you have the rights to all content within your app, including any third-party code, images, or media.

Having these ready reduces delays and issues during submission and certification.

How do I package and submit my app correctly?

Follow these steps to package your app and submit it properly:

1. Build your app package using supported tools like Visual Studio or the Windows App SDK, ensuring it meets Microsoft’s packaging standards (.appx, .msix, or .appxbundle).
2. Sign your app package with a valid certificate to verify authenticity.
3. Sign in to the Microsoft Partner Center and create a new app submission by reserving your app name.
4. Complete the submission form with metadata including your app description, category, pricing, and supported devices.
5. Upload your app package along with required assets such as the app icon, screenshots, and promotional images.
6. Configure additional settings like age rating, pricing options, and distribution regions.
7. Review all submitted information carefully before sending it for certification.

After submission, you cannot change your app package or metadata until the review process finishes, so verify all details thoroughly beforehand.

What certification requirements and policies must my app meet?

Your app must follow Microsoft Store policies to avoid rejection:

• Content must be appropriate for the assigned age rating or follow the Microsoft Store’s age rating guidelines.
• The app must not contain malware, misleading content, or infringe on intellectual property rights.
• Technical standards require your app to function correctly without crashes, respect user privacy, and use system resources efficiently.
• Accessibility features should support assistive technologies to accommodate users with disabilities.
• Handle sensitive user data securely and provide a clear privacy policy.

Review the Microsoft Store Policies documentation closely. Non-compliance can result in rejection or removal after publishing.

How do I handle age ratings, content policies, and technical requirements?

When submitting your app, configure age ratings based on your app's content and target audience using the Microsoft Store’s rating system. Ensure your app content complies with Microsoft’s content policies, avoiding prohibited or restricted materials.

On the technical side, test your app thoroughly to prevent crashes and ensure smooth performance. Confirm your app follows privacy guidelines by including a clear privacy statement and handling data securely. Incorporate accessibility features to support users with disabilities, enhancing usability.

Meeting these requirements upfront helps prevent certification failures and speeds up the approval process.

How can I avoid common submission mistakes and delays?

To avoid delays:

• Double-check that all required metadata and assets are complete and accurate before submission.
• Verify your app package is signed correctly and built with supported formats.
• Ensure your developer account and profile information is up to date, including payment and tax details.
• Test your app extensively on all targeted device families to catch issues early.
• Follow Microsoft’s content and certification policies closely.
• Respond promptly and thoroughly to any feedback from the certification team.

Being thorough during preparation and submission reduces the chance of rejection and speeds up the publishing timeline.

How will I know if my submission was successful?

Once submitted, your app goes through the certification review process:

• Monitor the status in the Partner Center dashboard, which shows stages like "In review," "Certification failed," or "Published."
• If approved, your app will be published and available in the Microsoft Store according to your distribution settings.
• If rejected, you will receive detailed feedback on issues that need correction.

To fix problems, update your app package or metadata as needed and resubmit. Repeat until your app meets all requirements. Check your email and Partner Center notifications regularly for updates and requests from the certification team.

Conclusion

After your app is live, continue monitoring user feedback and update your app regularly to maintain compliance and performance. Use Partner Center tools to manage updates, track sales, and respond to reviews. Careful preparation and attention to guidelines during your first submission lays the groundwork for a smooth publishing experience going forward.

Frequently Asked Questions

Do I need to pay to create a Microsoft Developer Account?

Yes. Creating a Microsoft Developer Account requires a one-time registration fee, which varies depending on whether you register as an individual or a company.

Can I update my app after it’s published on the Microsoft Store?

Yes. You can submit updates to your app package and metadata anytime through the Partner Center to improve features or fix issues.

What if my app targets multiple device types?

You can specify supported device families during submission and provide packages optimized for each device type to ensure your app works properly across devices.