Which FSLogix Profile storage option should I choose?

Nerdio Manager supports multiple storage options for FSLogix profile containers. The right option for you depends on your performance requirements, identity model, resiliency goals, and how much infrastructure you want to manage. In Nerdio Manager, the FSLogix profile path can point to an Azure Files share, an Azure NetApp Files volume, or a UNC path to an existing file share. When Cloud Cache is enabled, up to four paths can be configured.

For most environments, Azure Files is the best starting point because it is fully managed and integrates cleanly with Nerdio Manager. File server VMs, Azure NetApp Files, and Cloud Cache are also valid options, but they are usually chosen for more specific architectural or resiliency requirements.

Summary of recommendations

See the option-specific sections below for details. 

• For most environments, start with Azure Files Premium.

• Consider Azure NetApp Files if you already use it in your Azure tenant or have a specific storage requirement.

• Use a file server VM or UNC path only if you want to manage that layer directly.

• Add Cloud Cache when resiliency across multiple storage locations is a requirement. 

When to use each option 

       Azure Files 

Use Azure Files when you want the simplest and most common design. Azure Files provides fully managed serverless file shares and avoids the overhead of maintaining a file server VM.

Azure Files is usually the best fit when: 

• You want a managed service instead of a file server VM 

• Your environment uses AD DS, Entra Domain Services, or a supported Entra-based method 

• Your primary goal is to reduce operational overhead while maintaining good performance.

       Azure NetApp Files 

If you already uses ANF or have a storage design that requires it, you should use Azure NetApp Files for storage. In Nerdio Manager, Azure NetApp Files can be selected as the FSLogix Profiles path alongside Azure Files shares or a UNC path.

Azure NetApp Files is usually the better fit when: 

• ANF is already part of your Azure architecture 

• Profile storage needs to align with existing NetApp operational standards 

• You have storage or performance requirements that justify ANF.

       Existing UNC path or file server VM 

Use a UNC path or file server VM if you want to keep direct control of the storage server.

The file server should be kept in the same Azure region as the AVD hosts to avoid latency, and Premium storage is recommended. Existing guidance also recommends starting with a D4s_v3 VM or higher and monitoring disk latency and queuing.

A file server VM or UNC path is usually the better fit if: 

• You already have a mature file server design 

• You want full control over the underlying SMB server 

• You accept the extra operational responsibility.

       Cloud Cache 

Use Cloud Cache when resiliency across multiple profile storage locations is required. Cloud Cache asynchronously replicates profiles across multiple storage paths and allows the session host to fail over if one location becomes unavailable. In Nerdio Manager, you can configure up to four paths, and the profiles are created in all configured locations.

Cloud Cache is usually the right fit when: 

• Profile availability across multiple locations is important 

• The design requires higher tolerance for a storage path outage 

• You accept added complexity in exchange for resiliency

Identity considerations 

Azure Files supports identity-based authentication for Windows file shares over SMB using Kerberos through Active Directory Domain Services, Microsoft Entra Domain Services, and Microsoft Entra Kerberos for hybrid user identities. The setup differs depending on the method used.

When creating an Azure Files share for FSLogix, the storage account must be integrated with Active Directory, Entra Domain Services, or Entra ID as appropriate for the selected method. Nerdio Manager can join the storage account during setup, and the share should be assigned the required SMB Share Contributor permissions.

Best practices 

• Prefer Azure Files Premium for most FSLogix deployments. It is the recommended default and provides the best performance in most cases.
• Enable SMB Multichannel on Azure Files where appropriate to improve client performance.
• Keep file server VMs in the same Azure region as the AVD hosts to reduce latency.
• Use Cloud Cache only when there is a clear resiliency requirement.
• Assign both the required Azure RBAC share permissions and the recommended NTFS file-level permissions when using Azure Files for FSLogix.
• Exclude the stored admin account or domain admin account from FSLogix where appropriate so a non-FSLogix-backed sign-in path remains available for troubleshooting. Existing FSLogix guidance also notes that if FSLogix is already installed in the desktop image, the version selected in the profile settings is ignored.

Notes 

If file storage is not ready during initial setup, Nerdio Manager allows you to skip the step and configure the FSLogix storage later.

In Nerdio Manager, the FSLogix Profiles path can use Azure Files, Azure NetApp Files, or a UNC path. If Cloud Cache is enabled, multiple paths can be configured and reordered.