Deployment failed due to Join domain error

Jasmine lynam 21 Reputation points
2021-04-05T15:42:52.59+00:00

Hi there,

I'm currently a 4th-year college student investigating Virtual Desktop Infrastructures as part of my final year project. I'm hoping to build a prototype using Windows Virtual Desktops within Azure. However, after deploying the host pool I run into this error (please see screenshot attached). As I am just a student who does not have the equipment or infrastructure of a large organization I created a domain with Name.com (x01038184.live).

I would greatly appreciate it if someone could point me in the right direction!

Below is the error code

{"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":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'joindomain'. Error message: \"Exception(s) occured while joining Domain 'x00138184.live'\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot "},{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'joindomain'. Error message: \"Exception(s) occured while joining Domain 'x00138184.live'\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot "}]}84484-125.png

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,375 questions
Microsoft Entra
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,664 questions
0 comments No comments
{count} votes

Accepted answer
  1. Andreas Baumgarten 97,566 Reputation points MVP
    2021-04-05T18:14:10+00:00

    Hi @Jasmine lynam ,

    unfortunately the Active Directory is a mandatory requirement to run an Azure WVD environment.

    If you create a small Windows Server VM it's cheaper than the Azure Active Directory Services. You are able to reduce the costs for the VM if you deallocate the VM if not needed. A small VM SKU/size should be ok for a AD Domain Controller.

    Depending on your region and the time the VM is up and running the costs for the VM could look like this (around 20 US$ if you run the VM 40 hours per week/160 hours per month (choose the smalldisk version of the Windows Server Image! -> OS Disk will be 32 GB than):

    84478-image.png

    Only the storage transactions will be added, which should be just a few US$ per month in a test environment.

    You should take a look at the Azure Price Calculator and do your own math based on your requirements (VM Sku, time the VM is running):
    https://azure.microsoft.com/en-us/pricing/calculator/

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Andreas Baumgarten 97,566 Reputation points MVP
    2021-04-05T15:54:13.29+00:00

    Hi @Jasmine lynam ,

    You need to setup an Active Directory domain in sync with the Azure AD to join the WVD host VM.
    This AD domain could be deployed as "own-managed" with a Windows Server VM or using the Azure Active Directory Domain Services.

    84496-image.png
    https://learn.microsoft.com/en-us/azure/virtual-desktop/overview#requirements

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten


  2. Manu Philip 16,986 Reputation points MVP
    2021-04-05T16:02:02.8+00:00

    Another thought about the issue you are facing is as below as you can see from the troubleshooting reference: https://aka.ms/vmextensionwindowstroubleshoot
    It can be a timeout. If that's the case, easy fix is to deploy again by pressing 'redeploy'

    0 comments No comments