What Are Azure Files and FSLogix Profile Storage Options?
Consider the following FSLogix profile containers storage options, as well as best practices and optimizations for FSLogix profile storage in Azure Files.
FSLogix Profile Storage Options
Nerdio Manager supports several options for storing the FSLogix profile containers.
Companion Video
Available Options
There are two most frequently used options for storing FSLogix profile container virtual disks:
File server VM: Using this option, you are managing the underlying server object, and undertake any server VM maintenance tasks, such as updating the file server, ensuring that it is active, and the storage performs as required. File server allows you to leverage the AD authentication for the NTFS permissions.
The server must be in the same Azure region as the AVD host to avoid latency between the source and end users. Also, Premium storage is recommended for the file server ultimate performance.
Recommendations:
D4s_v3 VM and higher
Premium SSD 1 TB
Monitoring the disk latency and queuing
Azure Files (recommended): Available as an IaaS service, Azure Files provides fully managed serverless file shares that are accessible via the industry-standard SMB and NFS protocols.
Azure Files uses the Azure storage, and like the File server, it requires the AD authentication for the NTFS permissions. Premium file shares support larger IOPS and throughput limits than standard file shares, and are recommended to ensure the ultimate performance.
Recommendations:
Premium file shares
SMB Multichannel. For details, see Configure SMB Storage Permissions and Boost your client performance with Azure Files SMB Multichannel.
For more details about the FSLogix profile containers deployment in Nerdio Manager, see FSLogix Settings and Configuration.
Azure Files Storage Considerations
When planning for the Azure Files deployment, consider the following details:
Deployment method: You can deploy Azure Files in the following ways:
By directly mounting the serverless Azure file shares using the standard SMB or NFS clients available in your OS.
By caching Azure file shares on-premises using Azure File Sync, if your organization uses a file server (cloud or on-premises).
Available protocols: Depending on your workload, you can choose between the SMB or NFS protocols. Azure file shares don't support both the SMB and NFS protocols on the same file share, although you can create SMB and NFS Azure file shares within the same storage account.
Authentication: Azure Files supports identity-based authentication for Windows file shares over SMB using the Kerberos authentication protocol through the following methods:
On-premises Active Directory Domain Services (AD DS)
Microsoft Entra Domain Services
Microsoft Entra Kerberos for hybrid user identities
The setup is different depending on the domain service you choose.
For more details about Azure Files, see:
Comments (0 comments)