I’m having trouble finding a guide to setting up Windows Virtual Desktop that doesn’t lose me at the domain setup step. I have a hybrid Azure/AD/O365 environment. When setting up Windows virtual desktop it appears to require a new resource group and then proceeds to prompt for a DC account t and and password and OU path. Where exactly is this supposed to be? It doesn’t spin up a DC when it automatically creates all the resources as part of the deployment.
Thanks for reply. So the AD info it's requiring in this screen to complete the provisioning of a Windows Virtual Desktop, must be for an AD account and path/OU that exists in an on-prem AD server in our on-prem environment? Or an ADDS DC in an Azure virtual machine that has a VPN or tunnel to our on-prem AD environment?
If you have an onprem Windows AD, then you should install Azure AD Connect on the DC. In Azure, you could create a VPN in your VNET, updating the VNET DNS settings to point to the onprem DC, and then join the WVD Sessionhosts to the onprem Domain using a AD account from that AD Forest.
If you don't want to use a VPN, you could use the following setup:
On the onprem Windows AD, install Azure AD Connect on the DC to sync to Azure AD.
In Azure, add Azure AD DS, which will update the VNET for you, and then you can use that AD account from the local domain to join the WVD sessionhosts.
Hope this makes things more clear
Best Response confirmed by
John Quile (Occasional Contributor)