Edit

Microsoft Store readiness checklist for MSIX apps

Use this checklist before you upload an MSIX package to Partner Center. A submission can stop at three different points: when you test the package locally, when Partner Center validates the upload, or during certification. Each failure means another round of fixes and resubmission, so catch problems before you submit.

This checklist summarizes common requirements and links to the articles that define them. It applies to MSIX packages. For MSI or EXE installers, see App package requirements for MSI/EXE apps.

Account and app reservation

Package identity and version

  • The package manifest's Identity/Name, Identity/Publisher, and Properties/PublisherDisplayName values match your app's Product identity page in Partner Center. See View app identity details.
  • The display name in your manifest matches a name you reserved for the app.
  • The package version uses four parts (Major.Minor.Build.Revision) and follows the version rules in App package requirements. For an update, the version is higher than the installed package it replaces; same-version packages for different architectures and lower-version packages for additional device targets are also supported.
  • The package is built in the Release configuration, not Debug.

Signing

  • You don't need your own code-signing certificate for Store distribution, because the Store signs your package. A local development certificate is fine for installing and testing, but don't distribute packages signed with it outside the Store. For other channels, see Code signing options for Windows app developers.

Dependencies and capabilities

  • Runtime dependencies are declared and deployed as required by your app's deployment model. For framework-dependent Windows App SDK apps, see Deploy packaged apps, including its Visual C++ runtime prerequisites.
  • The manifest declares only the capabilities your app uses. If you declare a restricted capability, be ready to explain why your app needs it when you submit.

Store listing

  • Store logos and screenshots are real PNG files (not other formats renamed to .png) and meet the requirements in App screenshots, images, and trailers.
  • Screenshots show the current version of your app.
  • Your description and features are complete. See Add and edit Store listing info.
  • You have a privacy policy URL. Win32 and Desktop Bridge apps, including packaged desktop apps built with WinUI 3, WPF, or Windows Forms, always need one, even if they don't collect personal information. Other apps need one if they access, collect, or transmit personal information, or when required by law. See Microsoft Store Policies.
  • You're ready to complete the age ratings questionnaire.

Test the package locally

  • You installed the release package on a clean test device or virtual machine with only documented user prerequisites and, if needed for sideload testing, the public development certificate. The app launches and works. See Run the app on a clean device.
  • You ran the Windows App Certification Kit and fixed or understand every failure.
  • You tested core scenarios with the keyboard and a screen reader.

If a submission fails

See Fix Microsoft Store submission and certification failures, which is organized by where a submission stops: local testing, package upload in Partner Center, or certification. After you fix an issue, rebuild and retest the package. For updates, increase the version of the package being replaced, following the package-version rules.

For AI agents and automation

An AI agent can help with most of this checklist: reading the manifest, comparing identity values that the developer copies from Partner Center, checking image formats and dimensions, running the Windows App Certification Kit, and drafting listing text for review. A person must review the listing, complete account and agreement steps in Partner Center, and confirm every submission.

Next steps

  • Last updated on