Forum Discussion
Requirement to have an on-prem AD
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)
MicrosoftHybrid-join means joining the machine to Active Directory, and then having those device objects synced with Azure AD Connect to Azure AD (with writeback). One of a few ways of accomplishing this is joining the machine to a domain created in Azure Active Directory Domain Services (AAD-DS) - as that is Active Directory as a service, which is automatically synced to an Azure AD that you configure when you set up AAD-DS.
Note: Azure Active Directory (Azure AD) is not the same thing as Azure Active Directory Domain Services (https://azure.microsoft.com/en-us/services/active-directory-ds/).
While it is possible to join Windows 10 machines directly to Azure AD, and there are many great reasons to do that rather than joining or hybrid-joining with an Active Directory domain (particularly in a modern management environment), it is not supported for Windows Virtual Desktop. The Windows Virtual Desktop service specifically requires that the machine is joined to an Active Directory Domain.
Mike Amox I currently have on premise AD synced to Azure AD with AAD Connect so right now this will work. I am in the process of migrating all workstations to AAD with the goal of decommissioning AD. All device & application management will be via cloud management tools. While I appreciate I could setup AAD DS this still requires domain joined or hybrid join, not something I am after & get the impression others are the same.
Do you know if Microsoft has on the road map to support AAD joined devices only for WVD?
Thanks.