Forum Discussion
Domain Join Error while deploying HostPool
MicrosoftThe VM's in the host pool must be Standard domain-joined or Hybrid AD-joined. Virtual machines can't be Azure AD-joined (in the future, AAD joined will be supported). You will need to either deploy or use an existing Domain Controller, or leverage the Azure Active Directory Domain Services (AADDS, not to be confused with AAD) in order to do a Standard domain-join.
Please review the requirements for WVD:
https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements
To learn more about the different identity solutions used with WVD:
https://docs.microsoft.com/en-us/azure/active-directory-domain-services/compare-identity-solutions
-Jeff
Jeff_Bryant I'm getting this error in spite of having Azure Active Directory + Azure AD Domain Services deployed and peer networked with my vnet in which the host pool vms are being provisioned. I verified classic domain join works by establishing a point-to-site vpn connection into the vnet, using virtual network gateway setup, and was able to join a localhost hyper-v windows 10 desktop setup that i have. So not sure what to do in order to get wvd host pool template deployed vms to successfully join.
q1. Is there a localhost user account you can connect to the host pool vms that fail to successfully join the domain so you can manually join them?
q2. Is there some permissions pre-provisioning that has to be done for the wvdadmin@myazureaddomain.com account which i specify for wvd host pool tenant group access given the default tenant group and host pool tenant group objects don't seem to exist in my azure ad environment or in my azure resource group before a wvd host pool deployment or after one that failed due to this vm domain join error?
