Forum Discussion

saarc's avatar
saarc
Copper Contributor
Apr 04, 2019

failed to join to the domain

hi All when running a deployment i received the flowing error even after enabling AD service endpoint. should the vnet have a vpn connection to on premise DC?    {"code":"DeploymentFailed","messa...
Christian_Montoya's avatar
Christian_Montoya
Icon for Microsoft rankMicrosoft

saarc tommy_barnes : Yes, the virtual machine needs to domain-join to an Active Directory that is synchronized with Azure AD. This is so the service can resolve the "on-prem" user when connecting them to a session on the VM.

 

One alternative to a VPN is using Azure AD Domain Services, since the users created in Azure AD Domain Services also exist in Azure AD. This would satisfy that requirement.

Alberto Rodriguez's avatar
Alberto Rodriguez
Copper Contributor
May 02, 2019

Christian_Montoya I am struggling with this too.  Trying to deploy WVD and getting same error message.  I have Azure AD only and Domain Services in Azure already.

  • Christian_Montoya's avatar
    Christian_Montoya
    Icon for Microsoft rankMicrosoft
    May 02, 2019

    Alberto Rodriguez : If you are using Azure AD Domain Services, can you try providing credentials of a user in the "AAD DC Administrators" group for the credentials?

     

    Also, adding my response to a different thread, for more visibility:

    Do you have access to those VMs? If you can RDP into them, please look at C:\Packages and navigate down to the JsonADDomainExtension folder, you should be able to find a "status" file (or equivalent). If you open it up, it will typically give you the reason that it errored out. Unfortunately, I do not have too many details at the moment because the documentation on the extension is fairly light.

Resources