The Microsoft Store Submission Process

Publishing an app to the Microsoft Store starts in Partner Center, Microsoft's web portal for managing app identities, pricing, and releases. A developer first reserves a unique app name, which generates a Store-specific package identity (a reserved Package/Identity/Name and Publisher pair) that must be embedded into the app's AppxManifest.xml before the package will be accepted. From there, the developer creates a submission: uploading one or more MSIX/MSIXUPLOAD packages, filling in Store listing details (description, screenshots, age ratings), setting pricing and market availability, and finally submitting for certification, after which Microsoft's automated and manual review pipeline takes over.

Before uploading, the app's AppxManifest.xml Identity element must contain the exact Package Name and Publisher values Partner Center assigned during name reservation, and the Version number must be higher than any previously published submission. Developers typically use Visual Studio's 'Create App Packages' wizard, which can produce architecture-specific packages (x86, x64, ARM64) bundled into a single .msixupload file, run the Windows App Certification Kit locally, and optionally enable automatic block map generation for differential updates. Getting the identity fields wrong is the most common reason a package is rejected before certification even begins.

After submission, packages go through Microsoft's certification pipeline, which combines automated security and policy scans (malware detection, API usage checks, manifest validation) with a manual functional test pass where a reviewer installs and exercises the app on real or virtualized hardware against the Microsoft Store Policies. Certification typically completes within a few hours to a couple of days depending on app complexity and current queue volume. If the app fails, Partner Center returns a detailed report citing the specific policy or technical failure; once it passes, the developer can choose immediate publish, a scheduled release date, or a staged rollout to a percentage of users before going to 100%.

Beyond the binary itself, Partner Center requires a complete Store listing: localized descriptions, at least one screenshot per supported device family, an age rating obtained through the International Age Rating Coalition (IARC) questionnaire, and privacy policy URL if the app collects any user data. The Microsoft Store Policies (section 10 in particular) govern in-app purchases, ads, and content requirements, and violating them — such as using deceptive metadata, requesting excessive capabilities the app doesn't use, or failing to disclose data collection — is the leading cause of manual rejection even when the automated scan passes cleanly.