Hello @Kiran Nukalapati
There are several reasons why Microsoft Entra ID-joined AVD session hosts may deploy successfully but fail to register with the host pool.
Some things I'd check first:
- Verify the AVD agent and AVD bootloader are installed and running on the session host.
- Confirm the host pool registration token was valid during deployment. An expired token prevents the VM from joining the host pool.
- Ensure the VM has outbound connectivity to the required Azure Virtual Desktop service URLs (HTTPS/443). Network restrictions, firewalls, or proxies are common causes of registration failures.
- Verify that Microsoft Entra ID login is enabled on the VM (via the AADLoginForWindows extension) and that the users are assigned the Virtual Machine User Login or Virtual Machine Administrator Login RBAC role.
- Check the Event Viewer under Applications and Services Logs > Microsoft > Windows > RemoteDesktopServices and Azure Virtual Desktop logs for registration or agent errors.
Could you also share:
- Are the session hosts Microsoft Entra joined only, or are they hybrid Microsoft Entra joined?
- Are you deploying with the Azure portal, Bicep/ARM, or Terraform?
- At which step does the deployment fail, or does it complete but the session hosts remain Unavailable/Not Registered in the host pool?
Those details will help narrow down whether the issue is with registration, identity, or networking.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.