Share via

FSLogix profile container is not creating in Azure file share in Native cloud environment

Happiest Minds 2 0 Reputation points
2025-05-20T06:03:12.5166667+00:00

We are configuring and testing the Azure Virtual Desktop setup in Completely Cloud Environment, The User profiles are not creating in the Azure file share which has already created in same region where the Hostpool and the session host.

As we referred Microsoft Public document till it is not functioning.

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 160 Reputation points Microsoft External Staff Moderator
    2025-07-24T10:41:44.04+00:00

    Welcome to the Microsoft Q&A Platform and thank you for your question!

    Based on your description, you are experiencing an issue where the FSLogix profile container is not being created in your Azure Virtual Desktop (AVD) environment.

    I would like to share a few steps that may help resolve the issue you are encountering.

    1. Enable “Delete local profile when FSLogix profile should apply” Policy

    Make sure this Group Policy is enabled to prevent Windows from loading a local profile when FSLogix is expected to handle user profiles.

    • Policy path: Computer Configuration > Administrative Templates > FSLogix > Profile Containers
    • Policy name: Delete local profile when FSLogix profile should apply
    • Set to: Enabled

    This ensures that a local profile doesn’t block the VHD/VHDX profile container from being mounted.

    2. Check File Share Access

    FSLogix requires access to the storage location where the profile containers are stored. If this is inaccessible, profile creation will fail.

    • Log into the AVD session host as the affected user (or an administrator), and try accessing the profile share directly using File Explorer by entering the UNC path ( \<fileserver><profileshare>) into the address bar.
    • Ensure the user has NTFS permissions (Full control on their own profile folder) and Share permissions (At least "Change").

    3. Use Cloud Cache (CCD) in Cloud-Only Environments

    If you are running a cloud-native environment (without a domain controller or hybrid AD setup), I recommend using Cloud Cache (CCD) instead of standard VHD mode.

    CCD simplifies deployment by allowing multiple storage locations and is more resilient in environments without traditional domain infrastructure. It also doesn’t rely on Group Policy Objects (GPO) from an on-premises DC.

    To enable CCD, set the following registry key and configure your CCDLocations accordingly: HKLM\SOFTWARE\FSLogix\Profiles\UseCloudCache = 1

    Additional Troubleshooting

    • Check the FSLogix logs at: C:\ProgramData\FSLogix\Logs\Profiles Look for errors related to VHD mount, access denied, or profile load failure.
    • Confirm that FSLogix is enabled: HKLM\SOFTWARE\FSLogix\Profiles\Enabled = 1

    Please let me know how it goes, I am happy to assist further if needed. Wishing you a smooth AVD experience!

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.