Users receive temporary profiles on AVD – FSLogix profile not applying for some users

Hello, We’re experiencing an issue in our Azure Virtual Desktop (AVD) environment.

Only one user (Yochay Abergel) is able to log in successfully with their FSLogix profile applied. All other users (e.g., Gaya Dahan) are being logged in with temporary profiles.

From the FSLogix logs and Event Viewer, the following messages are seen:

FSLogix Profiles feature is not enabled

Reason set to 6: Component is not enabled in product key

Local profile already exists. Do nothing

Users are confirmed members of the FSLogix "Include" group (based on SID resolution).

Registry keys are present in both:

HKLM\SOFTWARE\FSLogix\Profiles

  `HKLM\SOFTWARE\WOW6432Node\FSLogix\Profiles` with `Enabled = 1` and `PreventLoginWithTempProfile = 1`.
  

Additional notes:

The session host is in a Pooled host pool.

"Start VM on Connect" is enabled, but connection fails unless the VM is already running.

AAD Join is successful.

The affected user is added to the Remote Desktop Users group.

User Gaya appears in the Desktop Application Group (DAG) assignments.

We would appreciate help with the following:

1. Why is FSLogix working correctly for one user, but all others receive temporary profiles?

Could this be due to SID mismatch between AAD and the local user profile or FSLogix configuration?

How can we confirm that FSLogix is licensed and functioning correctly on the session host?

Thank you for your support!Hello,

We’re experiencing an issue in our Azure Virtual Desktop (AVD) environment.

Only one user (Yochay Abergel) is able to log in successfully with their FSLogix profile applied. All other users (e.g., Gaya Dahan) are being logged in with temporary profiles.

From the FSLogix logs and Event Viewer, the following messages are seen:

FSLogix Profiles feature is not enabled

Reason set to 6: Component is not enabled in product key

Local profile already exists. Do nothing

Users are confirmed members of the FSLogix "Include" group (based on SID resolution).

Registry keys are present in both:

HKLM\SOFTWARE\FSLogix\Profiles

  `HKLM\SOFTWARE\WOW6432Node\FSLogix\Profiles`  
   with `Enabled = 1` and `PreventLoginWithTempProfile = 1`.
  

Additional notes:

The session host is in a Pooled host pool.

"Start VM on Connect" is enabled, but connection fails unless the VM is already running.

AAD Join is successful.

The affected user is added to the Remote Desktop Users group.

User Gaya appears in the Desktop Application Group (DAG) assignments.

We would appreciate help with the following:

Why is FSLogix working correctly for one user, but all others receive temporary profiles?

Could this be due to SID mismatch between AAD and the local user profile or FSLogix configuration?

How can we confirm that FSLogix is licensed and functioning correctly on the session host?

Thank you for your support!