Use FSLogix Cloud Cache for public profile storage

This commit is contained in:
2026-09-18 11:09:44 -06:00
parent da310e4213
commit c47913e81d
6 changed files with 179 additions and 8 deletions
+3 -1
View File
@@ -84,7 +84,9 @@ Azure P2S deployments can add a dedicated, private Azure Files account. Student
accounts (`AL`) keep a non-authoritative local profile and redirect only
Documents/Desktop. Administrative and professor accounts (`AD`/`DO`) receive an
FSLogix VHDX profile container through object-specific settings keyed to their
AD security-group SIDs. The storage account uses AD DS Kerberos with AES-256;
AD security-group SIDs. Private endpoints mount the VHDX directly; public WAN
endpoints use a local FSLogix Cloud Cache synchronized to Azure Files so profile
I/O does not block on every SMB round trip. The storage account uses AD DS Kerberos with AES-256;
share-root ACLs use `CREATOR OWNER` so users cannot browse one another's data.
The bootstrap staging account is deliberately separate. See
[user-roaming.md](user-roaming.md) for rollout and recovery constraints.