Share via

Deplyment failed because of Azure domain join

Misbah Hasan 136 Reputation points
2020-07-02T11:43:42.163+00:00

Hello,

I get deployment error pointing to a resource related domain join, when creating a host pool for Windows Virtual Desktop. Please see the attached screenshot file Deplyment failed 1.png. The summary of the error is shown in the attached screenshot file Deplyment failed 2.png. Additionally, please find the attached screenshot file Virtual network 1.png to see the details of virtual network that, I create earlier.

Also, following is the error information:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations 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 'centrixe.com'\\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot \"\r\n }\r\n ]\r\n }\r\n}"}]}11160-virtual-network-1.png

I hope, I the information provided, is sufficient.

Many thanks.

Kind regards,
Misbah

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,436 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. prmanhas-MSFT 17,901 Reputation points Microsoft Employee
    2020-07-07T12:42:23.913+00:00

    @MisbahHasan-4008 Apologies for the delay in response.

    The 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 here.

    To learn more about the different identity solutions used with WVD you can find more information here.

    Similar issue has been reported here and has troubleshooting steps for the issue reported as well. One more article referring to similar issue is here.

    Please let me know if above helped or not.

    Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics.

    0 comments