The problem FSLogix solves
In pooled host pools, users land on whichever session host is available. Without portable profiles, settings, files, and print preferences would reset on every session. That is what FSLogix profile containers fix.
How it works
FSLogix mounts a per-user VHDX profile container from a shared store — in our case Azure Files. When a user signs in:
- Their profile container mounts from Azure Files
- Settings, app data, and printers load instantly
- Sign out → changes write back to the container
- Next session anywhere → same desktop, same settings
Azure Files sizing
Sizing profiles correctly prevents both cost blowups and slow logons:
| User type | Typical profile size | |
|
| | Light (data entry) | 1–2 GB | | Standard (ERP + Office) | 2–4 GB | | Heavy (design, CAD) | 5–10 GB |
Plan for ~1–2 GB per user plus 20% overhead, and enable incremental backups for the share.
Production best practices
- Use Azure Files Premium for logon performance
- Enable FSLogix container compaction to reclaim space
- Back up the Azure Files share (profiles are business data)
- Set correct NTFS/share permissions per user
- Test logon times during peak — not just at noon
What it delivered for our 200-desktop customer
- Every user's settings and print preferences intact across sessions and shifts
- Profile containers on Azure Files, backed up
- Cutover completed over one weekend — zero shifts missed
📘 Read the full AVD case study book
Setting up AVD? WhatsApp +91 93197 07938 or contact@krizia.in.
Loved this insight? Subscribe for more.
Join the inner circle of tech executives and senior engineers. Get our best architectural deep-dives delivered straight to your inbox.
Stay Ahead of the Curve
Join 2,000+ tech leaders. We verify every email to ensure only real insights reach real people.