FSLogix Profile Containers in Enterprise AVD

1. Profile Container Architecture

FSLogix stores each user profile inside a virtual hard disk file (VHDX) that lives on shared storage. When a user signs in, the container is mounted and treated as the C:\Users\<user> profile, so every session host sees the same desktop, cache, and application state.

• ProfileType: Set to VHD so profiles are written into a container rather than a loose folder.
• Shared Storage: Containers must sit on a location every session host can reach; local disks are not supported.
• Concurrency: FSLogix locks the container per user, enabling safe multi-session and cross-host sign-in.

2. Storage Backend Selection

Choose the backend by IOPS profile, protocol, and price. Azure Files is the fastest to stand up; Azure NetApp Files suits high-performance, protocol-flexible workloads.

3. Azure Files Mounts & Permissions

Azure Files shares used for profiles must follow the AVD naming and permission contract: the storage account group must match the resource group, and access must be delegated through the host pools so session hosts can mount the share at logon.

• Plan Naming: Name the file share after the site/host pool and keep the storage account in the same region as the pool.
• Delegated Access: Use AVD delegated file share permissions so the service brokers access securely - do not hand out broad SMB credentials.
• Mount on Sign-In: Validate the share mounts automatically at logon; pre-mount scripts should be avoided in favor of FSLogix native behavior.

4. FSLogix Configuration & Deployment

Configure FSLogix through a profile JSON, SCCM client settings, or Intune application settings. Keep the configuration identical across the fleet and pin the profile location to the share path:

5. Verification & Troubleshooting

Confirm a clean profile experience by checking that the container mounts, the profile loads under the user path, and logout releases the lock cleanly. Use the FSLogix log folder for root-cause work:

• Mount Check: fsmount -p lists active profile containers on the session host.
• Stale Locks: A user unable to sign in on any host usually means a container lock or shutdown is pending on the previous host.
• Telemetry: Monitor mount time and container size across sites; regressions indicate storage latency or profile bloat.