You deploy a Azure Virtual Desktop host pool named Pooll. You have an Azure Storage account named store 1 that stores FSLogix profile containers in a…

FSLogix profile containers require a network path to an SMB (Server Message Block) file share. When using Azure Files for this purpose, the correct path format is the Universal Naming Convention (UNC) path. The UNC path for an Azure Files share is constructed as \\.file.core.windows.net\. In this scenario, the storage account is store1 and the share is profiles, making the correct UNC path \\store1.file.core.windows.net\profiles. This path is configured in the VHDLocations registry key or Group Policy setting on the session hosts.

A. This is an HTTPS URL, not a UNC path. FSLogix uses the SMB protocol to mount the share, which requires a UNC path.

C. This path points to the Azure Blob Storage endpoint (.blob.core.windows.net), but FSLogix profile containers must be stored on an SMB share, such as Azure Files (.file.core.windows.net).

D. This is an HTTPS URL for the Blob Storage endpoint, which is incorrect for both the protocol and the storage service type.

1. Microsoft Learn. "Create a profile container with Azure Files and AD DS". Under the section "Configure FSLogix profile container registry settings

" the documentation specifies the value for VHDLocations must be a UNC path in the format \\.file.core.windows.net\.

2. Microsoft Learn. "FSLogix profile containers and Azure Files". In the "Configure profile containers" section

it explicitly states to set the VHDLocations registry entry to the UNC path of the Azure Files share.

3. Microsoft Learn. "Profile Container registry configuration settings". The documentation for the VHDLocations setting defines it as "A REGMULTISZ value that contains one or more UNC paths to the locations where the user's profile VHD(x) files are stored." This confirms a UNC path is the required format.