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","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'joindomain'. Error message: \\\"Exception(s) occured while joining Domain 'ourdomain.com'\\\".\"\r\n }\r\n ]\r\n }\r\n}"}]}
  • 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

      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

        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.

  • saarc 

     

    Same here, site-to-site connectivity is working fine.  Plenty of other VMs living in this subnet without issues contacting local AD.  Something is broken in the extension or deployment process.  I've tried dedicate service account and super users (Domain Admin, Enterprise Admin, etc.) no luck.

     

     

    • Christian_Montoya's avatar
      Christian_Montoya
      Icon for Microsoft rankMicrosoft

      ChristopherB2175 : If you go to these VMs after the domain join extension fails and you provide the same domain join credentials and the same "domainToJoin", does it then join the domain correctly?

      • hankchi95's avatar
        hankchi95
        Copper Contributor

        Christian_Montoya I've come across the same error while evaluating WVD preview. When the error occurs  after the domain join extension fails, the VM instance are not accessible. Tried connecting to the VM's to resolve the domain issue, but it looks like the VM that is created does not have a Public IP address assigned. 

         

        I see the comment about "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". Is there some tutorial on how to set this up as part of following the the WVD tutorial? Looking for tutorial that will allow evaluation of WVD from scratch, no current use of Azure services.

Resources