Document staging ACLs for manual staging (AB#21705401) - #474
Open
RDMacLachlan wants to merge 2 commits into
Open
Document staging ACLs for manual staging (AB#21705401)#474RDMacLachlan wants to merge 2 commits into
RDMacLachlan wants to merge 2 commits into
Conversation
Adds guidance on the file system permissions (ACLs) required when staging MSIX packages manually - to a local/external volume, a network share, or a WVD/AVD staging directory - rather than relying on a provisioning tool to set them. - deploy-preinstalled-apps.md: new "Staging permissions (ACLs)" section covering local/external volumes (SYSTEM, Administrators, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES) and network/ virtual-desktop shares (session-host computer accounts on NTFS + SMB), with icacls examples and links to AVD App Attach docs. - register-from-network.md: call out the app-container SIDs the share must grant read to, linking to the new section. - msix-troubleshooting-guide.md: point the ACL troubleshooting row at the new staging permissions guidance. Resolves AB#21705401 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 9b5ce28: ✅ Validation status: passed
For more details, please refer to the build report. |
Collaborator
Author
|
@DrusTheAxe - Please review content. |
DrusTheAxe
reviewed
Jul 6, 2026
| | Principal | SID | Access | | ||
| |-----------|-----|--------| | ||
| | `SYSTEM` | `S-1-5-18` | Full control | | ||
| | `Administrators` | `S-1-5-32-544` | Full control | |
There was a problem hiding this comment.
We grant administrators Full control? That includes Write access. I'm surprised.
SUGGEST: Verify this table against latest version of the tool/code and update table to match, if necessary
GrantMeStrength
previously approved these changes
Jul 8, 2026
Applies DrusTheAxe review threads 1-3,5-9: rephrase ACL intro (deployment sets ACLs when it can; read-only mounts require manual setup; pre-set to avoid one-time perf cost), link ACLs/ACEs to Learn security pages, rewrite app-container paragraph to reference packaged processes, use 'Read and eXecute' casing, drop NTFS/SMB-only framing, and reflow new prose to <=100 chars. Thread 4 (Administrators=Full control) left unchanged pending App Deployment team confirmation; not pushed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3d27fb29-0162-474f-8e83-e7cc06dfe11c
Contributor
|
Learn Build status updates of commit 45a6b4a: ✅ Validation status: passed
For more details, please refer to the build report. |
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
3 participants
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.
Summary
Resolves AB#21705401 — [MSIX Docs] Document ACLs required for staging for people who don't want to run the tool.
The bug asked us to document the ACLs (file system permissions) required on a WVD/external staging directory for admins who stage MSIX packages manually, rather than relying on a provisioning tool to set permissions. That guidance did not exist anywhere in the docs.
Changes
SYSTEM,Administrators,Users,ALL APPLICATION PACKAGES(S-1-15-2-1),ALL RESTRICTED APPLICATION PACKAGES(S-1-15-2-2), with anicaclsexample. Explains why the app-container SIDs are required (app fails to launch without them even if registration succeeds).icaclsexample and links to the AVD App Attach docs.Notes for reviewers
The exact per-machine ACL identities should be confirmed with the App Deployment team before publishing; the values here reflect the standard WindowsApps/app-container permission set.