Hi @Joseph Miller ,
the solution depends on your environment:
If you have a AD Domain Controller running in Azure you have to make sure:
- The AD Domain Controller is reachable in the Azure Network from your WVD Host VM (network, peering, routing)
- The AD Domain Controller FQDN (AD Domain Name) needs the be resolved by the WVD Host VM via DNS during the deployment process (working DNS name resolution is required)
If you don't have a AD Domain Controller running in Azure but an on-premises AD DC:
- You have to make sure the on-premises AD Domain Controller is reachable by the WVD Host VM as well.
- Typically in this scenario is a VPN Gateway with a up and running Site-To-Site connection.
- It's the same with the DNS name resolution. The WVD Host VM must be able to resolve the AD domain name and the FQDN of the on-premises AD DC
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten