Forum Discussion
Windows Virtual Desktop - is AD Domain Controller needed and where does it reside?
Hi SeizeThaNight ,
I think you are mixing the things up a bit here
.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
Hi Micha,
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?
Hi SeizeThaNight ,
I think you are mixing the things up a bit here .
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