Forum Discussion
WVD setup with Azure AD DS and Multiple Custom Domains
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
Mike Stephens , Hmm, just figured out it does work after a password reset on Azure.
I now entered a more complex password.
Could it be that the password complexity policy of AAD DS was not met ? Is there even one set as default ?
Deleted Newly created cloud users do not sync to the managed domain until the user has changed their password. In Azure, when you create a new user, the user is assigned a default password and is forced to change it on the next sign-in. AAD DS will not sync the user until they change their password. Password complexity is entirely handled on the Azure AD side.