-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Clarify app submission requirements and packaging formats #5894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: docs
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -15,7 +15,7 @@ Every app in the Microsoft Store must have a unique name. Reserving an app name | |||||
|
|
||||||
| To reserve a name: | ||||||
| - Go to your Apps & games section in Partner Center and select “New product.” | ||||||
| - Choose the type of app (e.g., MSIX/PWA or EXE/MSI). | ||||||
| - Choose the type of app (e.g., MSIX/PWA). | ||||||
| - Enter the app title and click **Check availability**. | ||||||
| - If available, click **Reserve product name** to hold the name for 3 months. | ||||||
|
|
||||||
|
|
@@ -32,7 +32,7 @@ After reserving a name, start a new submission. The process involves: | |||||
| - **Pricing and Availability**: Choose free/paid, markets, trials. | ||||||
| - **Properties**: Set category and capabilities. | ||||||
| - **Age Ratings**: Complete content questionnaire for regional ratings. | ||||||
| - **Packages**: Upload your MSIX or EXE/MSI packages. | ||||||
| - **Packages**: Upload your MSIX package. | ||||||
|
||||||
| - **Packages**: Upload your MSIX package. | |
| - **Packages**: Upload your package(s), such as supported MSIX and related package formats. |
Copilot
AI
Apr 10, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The answer states that “traditional installer formats such as .exe or .msi are not supported for direct submission”, but this repo contains a full MSI/EXE submission guide that describes reserving an “EXE or MSI app” and uploading EXE/MSI packages in Partner Center (see hub/apps/publish/publish-your-app/msi/create-app-submission.md and .../msi/upload-app-packages.md). Please reconcile these docs—either qualify this FAQ as “for MSIX apps”, or update/remove the MSI/EXE guide and adjust wording here so the documentation set is internally consistent.
Copilot
AI
Apr 10, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
“Using msix package format” should use the product name capitalization (“MSIX”) and read more clearly as “Using the MSIX package format …”. This helps keep terminology consistent across the docs.
| Using msix package format ensures a more reliable, secure, and streamlined installation and update experience for users. | |
| Using the MSIX package format ensures a more reliable, secure, and streamlined installation and update experience for users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instructions here imply only MSIX/PWA can be selected when creating a new product. Elsewhere in this repo there is current guidance for creating an “EXE or MSI app” in Partner Center (for example,
hub/apps/publish/publish-your-app/msi/reserve-your-apps-name.md). Please either scope this FAQ explicitly to MSIX/PWA submissions or keep/restore the EXE/MSI option to avoid contradicting the rest of the documentation set.