Issues with VM Connectivity in Host Pools Sessions

Hello @Majhi, Sarthak,

Firstly, enable the role for the user with the Virtual Machine User Login.

To troubleshoot AVD VM that are in a Running state but report a Shutdown health status, begin by restarting the VM from the Azure portal to resolve any potential state inconsistencies. Additionally, verify the Azure VM Agent status to ensure it is running and up to date. If issues persist, consider resetting or upgrading the agent following the recommended steps provided in the Azure documentation.

Please follow the below given steps-

1. Navigate to the VM\Extensions + applications
2. Note the Version, for Win11ms, I would expect 2.2.0.0.
3. Click the Uninstall button.
4. Reboot the VM
5. Once the VM is back online after reboot, open Cloud Shell
6. Run the following in Cloud Shell substituting in your Resource Group name, VM name, and Location.

  Set-AzVMExtension -ResourceGroupName "<RESOURCE GROUP NAME>" -VMName "<VM NAME>" -Name "AADLoginForWindows" -Location "<LOCATION>" -Publisher "Microsoft.Azure.ActiveDirectory" -Type "AADLoginForWindows" -TypeHandlerVersion "2.2"

In the Azure portal, go to AVD VM > Select Access Control (IAM) > Select Role Assignments > Confirm that the user account has been granted either the Virtual Machine User Login or Virtual Machine Administrator Login role.

Ensure that the RDP property targetisaadjoined:i:1 was added to the AVD host pool. To do this, navigate to the Azure portal > Select the host pool configured for Azure AD Join > Select the RDP Properties blade > Select the Advanced Tab > Add targetisaadjoined:i:1.

Disable security defaults by navigating to Entra ID > Manage > Properties > Manage Security Defaults > Disable.

Add Conditional Access policies to exclude the VM from MFA by adding the user.

Enable Conditional Access policies and exclude the users and groups as needed.

I would suggest access the AVD VM's from windows app.

HI Nikhil,
All the VMs are in running state and working properly , with there extensions properly provisioned , it's just that for 6 Vms I created under the hostpool , I can see 4 are in can connect block and 2 of them are in can't connect state. With the 2 having this error , while the other 4 are connecting fine without any issues , could you help me understand this inconsistency ? I created them with the same image , same inputs and same vm sku. Kindly help me fix this.

Hey @Majhi, Sarthak ,

Could you please try re-adding the VM to the host pool?

Hi @Nikhil Duserla @Nikhil Duserla ,

Is there an option to create a support request directly through the Azure portal for this issue? I would like to expedite resolution by engaging with a Microsoft support engineer via a one-on-one call.

Additionally, I have a question regarding VM recreation: If I remove the problematic VMs and redeploy them as suggested, will the new VMs retain the original numbering (e.g., vm-1 and vm-2), or will they be assigned new sequential numbers (e.g., vm-7, vm-8) based on the current highest index in the host pool?

Thank you for your guidance.