Endpoint management and virtual desktop admins who are considering Azure NetApp Files (ANF) as the profile storage location for AVD
About this article What you'll learn How to use ANF as the storage location for FSLogix profile containers The FSLogix registry settings How to verify that it works Test environment : Azure Virtual Desktop / Azure NetApp Files (as of September 2026) Assumptions : An Active Directory Domain Services (AD DS) environment FSLogix stores a user profile in a VHD(X)-based container and attaches it to…
Endpoint management and virtual desktop admins have the option to utilize Azure NetApp Files (ANF) as a storage location for FSLogix profile containers in Azure Virtual Desktop (AVD) deployments as of September 2026. This article provides a step-by-step guide for configuring ANF as the storage location, as well as necessary registry settings and verification methods.
FSLogix stores user profiles in VHD(X)-based containers, which are attached to session hosts upon login. These profiles persist user settings and data in non-persistent VDI and multi-session environments. By storing these containers on Azure NetApp Files, admins can benefit from low latency and high throughput.
The recommended workflow for implementing ANF as the profile storage location includes creating a NetApp account, capacity pool, Active Directory connection, and SMB volume in the Azure portal. Session hosts must then configure the registry settings to point to the ANF volume. An Active Directory connection is required before creating an SMB volume, with prerequisites including an Azure account with contributor or administrator permissions and a subnet delegated to ANF.
After completing the steps, admins should verify that the configuration works correctly. This includes checking the registry settings and testing the connection between the session hosts and ANF volume. With the correct setup, ANF can serve as a reliable and high-performance storage solution for FSLogix profile containers in Azure Virtual Desktop environments.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.