Forum Discussion

bhushangawale's avatar
bhushangawale
Brass Contributor
May 04, 2020
Solved

WVD setup with Azure AD DS and Multiple Custom Domains

Hello everyone, need some guidance and views on WVD setup that we are thinking to provision   Azure subscription's Azure AD has multiple verified custom domains e.g. alpha.com, beta.com, gamma.com...
  • Mike Stephens's avatar
    Mike Stephens
    Jun 16, 2020

    bhushangawale 

    Multiple Custom Domains is different from Azure AD Domain Services. Custom domains are DNS domain names that you have associated with your Azure tenant.  Azure AD Domain Services is an Active Directory domain name hosted for you by Microsoft. It provides legacy authentication like LDAP, Kerberos, and NTLM. It also provides domain join capabilities ( not Azure AD Join) that is common with on-premises Active Directories.  The users created in the managed domain (Azure AD Domain Services) arrive through a one-way synchronization from Azure AD. All the users and groups in your tenant are synced in the managed domain and have the same user principal name as they do in Azure. So, it doesn't matter if they are from alpha, beta, or gamma domains. If the user has been created in your Azure AD Tenant (cloud user) or synced from your on-premises domains and forests through AAD Connect, then the user can authenticate to the managed domain (you just need to ensure those users have RDP access to the virtual machines or WVD sessions). 

     

    Hope that helps

    Mike Stephens

    Senior Program Manager

    Azure Identity

    IAM Core | Domain Services

     

Stefan Georgiev's avatar
Stefan Georgiev
Iron Contributor
Jun 16, 2020

bhushangawale I have a some what similar setup (2 different domain names in one DC, synching to Azure AD and from there to Azure AD DS) Generally I have not seen issues with users connecting (Regardless of the domain name in their UPN).

 

I am wandering why Azure AD DS is needed in this scenario? Due to no DC in Azure and no express route to on prem?

Resources