Clarify Microsoft Store automatic code signing for MSIX packages#5825
Closed
Clarify Microsoft Store automatic code signing for MSIX packages#5825
Conversation
Contributor
|
Learn Build status updates of commit 1054703:
|
…SIX packages Co-authored-by: GrantMeStrength <1928855+GrantMeStrength@users.noreply.github.com>
Co-authored-by: GrantMeStrength <1928855+GrantMeStrength@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 6ac882e: ✅ Validation status: passed
For more details, please refer to the build report. |
…edback Co-authored-by: GrantMeStrength <1928855+GrantMeStrength@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Inquire about Microsoft Store code signing for .msix files
Clarify Microsoft Store automatic code signing for MSIX packages
Feb 12, 2026
Contributor
|
Learn Build status updates of commit 04af857: ✅ Validation status: passed
For more details, please refer to the build report. |
cgaarden
pushed a commit
to cgaarden/windows-dev-docs
that referenced
this pull request
Mar 1, 2026
…9893341306sync_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
Contributor
|
Closing this in favour of a re-submission to the private repo at MicrosoftDocs/windows-dev-docs-pr#6647. The same changes have been applied there. Thanks to @copilot for the original work |
learn-build-service-prod bot
pushed a commit
that referenced
this pull request
Apr 18, 2026
* Clarify Microsoft Store automatic code signing for MSIX packages - Added FAQ entry explaining Store auto-signs all submissions - Updated app-certification-process.md Publishing section to note Microsoft cert - Expanded app-package-requirements.md with code signing section Moved from #5825 (originally by copilot-swe-agent). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address Copilot feedback on store code signing PR - FAQ: scope 'all apps' to MSIX/AppX; add explicit callout that MSI/EXE installers must be Authenticode-signed by the publisher (Store doesn't re-sign) - FAQ: clarify 'no CA-trusted cert needed' (not 'no signing at all') - app-package-requirements: ### → #### for code signing section to fix heading hierarchy (App bundles was incorrectly nested under it) - app-package-requirements: reword bullets to clarify the Store replaces the MSIX signature — not that no signing exists in the pipeline - app-package-requirements: add NOTE that MSI/EXE require publisher signing - app-certification-process: remove trailing space on digitally signed line - app-certification-process: 'on an average' → 'on average' (consistency) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address Copilot review feedback on code signing docs - Broaden 'MSIX packages' to 'MSIX/AppX packages' consistently across all three files (Store re-signs both formats) - Scope 'all packages' to 'all MSIX/AppX packages' in certification process to avoid implying MSI/EXE are re-signed (they are not) - Add comma before 'depending on their location' in two sentences for grammatical clarity Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation did not explicitly state that Microsoft Store automatically signs MSIX packages, leaving developers uncertain about certificate requirements—particularly those using USB tokens unable to export .pfx/.cer files.
Changes
app-package-requirements.md
app-certification-process.md
get-started-with-the-microsoft-store.md
Key Points
Store submissions require only package files (.msix, .msixupload, .msixbundle, etc.). The Store re-signs all packages with a Microsoft certificate during publishing after certification passes. This eliminates the need for developers to purchase or manage code signing infrastructure for Store distribution.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.