What's changed: Created AZ-140 Chapter 1 (Domain 1 first-half: network requirement assessment/reverse connect/RDP Shortpath-Multipath/QoS (DSCP); Azure Private Link for AVD (private endpoints/private DNS zone)/connectivity troubleshooting (DNS/UDR/FW/Azure Monitor); user-data storage (FSLogix profiles/Azure Files Premium SMB/Azure NetApp Files/AD DS-Entra Domain Services auth/IOPS-logon storms/same region)).
1.3Storage for user data
Understand planning storage for Azure Virtual Desktop user data, storage for FSLogix components, storage accounts and file shares, and implementing Azure NetApp Files.
On AVD pooled hosts, users sign in to a different VM each time. To preserve user profiles (settings/data), place FSLogix profiles on shared storage. This section designs where that storage lives.
1.3.1Azure Files and Azure NetApp Files
FSLogix profiles (VHD/VHDX) live primarily in two places: Azure Files (SMB file shares; Premium for SSD performance; requires identity-based authentication via AD DS, Microsoft Entra Kerberos, or Microsoft Entra Domain Services) and Azure NetApp Files (high-performance, low-latency, large-scale managed NFS/SMB). Architects choose Azure Files Premium for "small–mid scale, cost-conscious" and Azure NetApp Files for "large scale, high IOPS/low latency required." Place storage in the same region as session hosts to limit latency.
1.3.2Storage design considerations
Profiles often bottleneck on IOPS and size; size capacity by users × profile size and required IOPS by concurrent logons (logon storms). Design redundancy (LRS/ZRS), backup, and authentication (for FSLogix shares on Microsoft Entra ID-joined session hosts, choose Microsoft Entra Kerberos; even cloud-only Entra ID users authenticate without connectivity to a domain controller). "Authentication for the profile share" being one of AD DS / Entra Kerberos / Entra Domain Services is a frequent point.
Cues: "small–mid, cost-conscious FSLogix share" = Azure Files Premium (SMB; AD DS / Entra Kerberos / Entra Domain Services auth). "large scale, high IOPS/low latency" = Azure NetApp Files. Keep storage in the same region as session hosts. Profile-share auth is identity-based (Entra Kerberos for Entra ID join).
Watch the mix-ups: (1) Azure Files (general SMB, cost-efficient) vs Azure NetApp Files (high-performance, large-scale). (2) "FSLogix shares assume AD-based auth, so cloud-only Entra ID cannot work" is wrong—Entra Kerberos works without domain controllers. (3) Storage in a different region from session hosts increases latency.
1.3.3Section summary
- FSLogix profiles live on Azure Files Premium (small–mid, cost) or Azure NetApp Files (large, high IOPS/low latency)
- Size capacity by users × profile size, IOPS by logon storms; keep in the same region
- Profile-share authentication is identity-based: AD DS / Entra Kerberos / Entra Domain Services
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. In a large AVD environment, FSLogix profiles require high IOPS and low latency. Which storage is best?
Q2. For small–mid scale, you want FSLogix profiles on a cost-efficient SMB share. Which is best?
Q3. Which is valid for authenticating an FSLogix profile share?
Q4. When sizing IOPS for FSLogix profile storage, what matters most?
Q5. In which region should FSLogix profile storage be placed?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.