Forum Discussion

Brass Contributor

Mar 25, 2019

Solved

Requirement to have an on-prem AD

Looking at the documentation, it seems an on premise AD is required for Windows Virtual desktop in Azure and Azure domain join is not supported. Can anyone confirm if that's definitely the case? It s...

Josh Bender
Mar 25, 2019
HandA

on-prem AD is not required.

AD requirements:
Option 1: Domain controller that is synchronized with Azure Active Directory. The domain controller can be on-prem or in cloud. To synchronize with Azure Active Directory install Azure Active Directory Connect.
Option 2: Azure AD Domain Services domain in Azure (automatically synced with Azure Active Directory)

Christian_Montoya

Microsoft

Mar 28, 2019

smithanc : If this works right now, then great! However, we only support when there is a true synchronization between Azure AD and the local Windows Server AD: either through Azure AD Connect, Azure AD Domain Services, or through federation.

smithanc

Copper Contributor

Mar 28, 2019

Christian_Montoya Understood but hopefully you extend support to other models such as the one I have done in my PoC. Otherwise, my main use case right now for WVD is broken as I am looking to use WVD to provide VM access to isolated VMs that are located in a Azure VNET which does not have any public IP address associated to any NIC card within that VNET.

We looked into using RDS with Azure AD Application Proxy but ran into a blocker that it only worked with ActiveX and therefore only on Windows Machines running IE 11.

Otherwise, we will have to turn to the Citrix cloud.

KPA-1998
Copper Contributor
Apr 17, 2020
smithanc

For your use case, you might consider a product called TruGrid SecureRDP. It lets you connect to Windows computers running RDP behind firewall without opening firewall ports.