FSLogix profile containers and Azure files
The Azure Virtual Desktop service recommends FSLogix profile containers as a user profile solution. FSLogix is designed to roam profiles in remote computing environments, such as Azure Virtual Desktop. It stores a complete user profile in a single container. At sign in, this container is dynamically attached to the computing environment using natively supported Virtual Hard Disk (VHD) and Hyper-V Virtual Hard disk (VHDX). The user profile is immediately available and appears in the system exactly like a native user profile. This article describes how FSLogix profile containers used with Azure Files function in Azure Virtual Desktop.
If you're looking for comparison material about the different FSLogix Profile Container storage options on Azure, see Storage options for FSLogix profile containers.
A user profile contains data elements about an individual, including configuration information like desktop settings, persistent network connections, and application settings. By default, Windows creates a local user profile that is tightly integrated with the operating system.
A remote user profile provides a partition between user data and the operating system. It allows the operating system to be replaced or changed without affecting the user data. In Remote Desktop Session Host (RDSH) and Virtual Desktop Infrastructures (VDI), the operating system may be replaced for the following reasons:
- An upgrade of the operating system
- A replacement of an existing Virtual Machine (VM)
- A user being part of a pooled (non-persistent) RDSH or VDI environment
Microsoft products operate with several technologies for remote user profiles, including these technologies:
- Roaming user profiles (RUP)
- User profile disks (UPD)
- Enterprise state roaming (ESR)
UPD and RUP are the most widely used technologies for user profiles in Remote Desktop Session Host (RDSH) and Virtual Hard Disk (VHD) environments.
Challenges with previous user profile technologies
Existing and legacy Microsoft solutions for user profiles came with various challenges. No previous solution handled all the user profile needs that come with an RDSH or VDI environment. For example, UPD cannot handle large OST files and RUP does not persist modern settings.
The following table shows benefits and limitations of previous user profile technologies.
|Technology||Modern settings||Win32 settings||OS settings||User data||Supported on server SKU||Back-end storage on Azure||Back-end storage on-premises||Version support||Subsequent sign in time||Notes|
|User Profile Disks (UPD)||Yes||Yes||Yes||Yes||Yes||No||Yes||Win 7+||Yes|
|Roaming User Profile (RUP), maintenance mode||No||Yes||Yes||Yes||Yes||No||Yes||Win 7+||No|
|Enterprise State Roaming (ESR)||Yes||No||Yes||No||See notes||Yes||No||Win 10||No||Functions on server SKU but no supporting user interface|
|User Experience Virtualization (UE-V)||Yes||Yes||Yes||No||Yes||No||Yes||Win 7+||No|
|OneDrive cloud files||No||No||No||Yes||See notes||See notes||See Notes||Win 10 RS3||No||Not tested on server SKU. Back-end storage on Azure depends on sync client. Back-end storage on-premises needs a sync client.|
UPD requires Storage Spaces Direct (S2D) to address performance requirements. UPD uses Server Message Block (SMB) protocol. It copies the profile to the VM in which the user is being logged.
While S2D clusters achieve the necessary performance, the cost is expensive for enterprise customers, but especially expensive for small and medium business (SMB) customers. For this solution, businesses pay for storage disks, along with the cost of the VMs that use the disks for a share.
S2D clusters require an operating system that is patched, updated, and maintained in a secure state. These processes and the complexity of setting up S2D disaster recovery make S2D feasible only for enterprises with a dedicated IT staff.
FSLogix profile containers
On November 19, 2018, Microsoft acquired FSLogix. FSLogix addresses many profile container challenges. Key among them are:
- Performance: The FSLogix profile containers are high performance and resolve performance issues that have historically blocked cached exchange mode.
- OneDrive: Without FSLogix profile containers, OneDrive for Business is not supported in non-persistent RDSH or VDI environments. The OneDrive VDI support page will tell you how they interact. For more information, see Use the sync client on virtual desktops.
- Additional folders: FSLogix provides the ability to extend user profiles to include additional folders.
Since the acquisition, Microsoft started replacing existing user profile solutions, like UPD, with FSLogix profile containers.
Best practices for Azure Virtual Desktop
Azure Virtual Desktop offers full control over size, type, and count of VMs that are being used by customers. For more information, see What is Azure Virtual Desktop?.
To ensure your Azure Virtual Desktop environment follows best practices:
- Azure Files storage account must be in the same region as the session host VMs.
- Azure Files permissions should match permissions described in Requirements - Profile Containers.
- Each host pool VM must be built of the same type and size VM based on the same master image.
- Each host pool VM must be in the same resource group to aid management, scaling and updating.
- For optimal performance, the storage solution and the FSLogix profile container should be in the same data center location.
- The storage account containing the master image must be in the same region and subscription where the VMs are being provisioned.
- Learn more about storage options for FSLogix profile containers, see Storage options for FSLogix profile containers in Azure Virtual Desktop.
- Set up FSLogix Profile Container with Azure Files and Active Directory
- Set up FSLogix Profile Container with Azure Files and Microsoft Entra ID
- Set up FSLogix Profile Container with Azure NetApp Files