Forum Discussion

Dhadhabeer2403's avatar
Dhadhabeer2403
Copper Contributor
Nov 11, 2025

AVD session host with Hybrid join

We have deployed a single and multi-session host on hybrid join.  Single session host:  Configured with local disk for user login and working fine for end users in Windows App.   Multi-session ho...
Kidd_Ip's avatar
Kidd_Ip
MVP
Nov 12, 2025

Seems related to Azure Virtual Desktop agent registration, hybrid join timing, or ADDS authentication alignment area. Multi-session hosts are more sensitive to broker/agent connectivity and profile container mounting delays. Check agent health, hybrid join status, and RDP properties like targetisaadjoined:i:1 to ensure proper login flow.

  • Dhadhabeer2403's avatar
    Dhadhabeer2403
    Copper Contributor
    Nov 12, 2025

    Hi Kidd_Ip​ ,

    Thanks for the update..!!

    The multi-session host is healthy state from the Azure portal. Also, the rdp property targetisaadjoined:i:1 is only applicable for microsoft entra id authentication right and dedicated session host works well.

    We have correct ntfs and smb share level permissions for AVD end users in the Azure file share RBAC.

    Also, the screenshot shows the avd status shows as "connecting" for long duration. 

     

Resources