Azure Virtual desktop ->question

kumar kaushal 176 Reputation points

I have some questions on azure virtual desktop and need help with the same :

1)When we create a Host pool their we can two options

Select the directory you would like to Join

Active Directory
Azure Active directory

My understanding is : When you create an Onpremise AD you basically Sync it to Azure AD using AD connect tool .. And that is where all the users get synced .

Or you can also create your own Domain controller in azure and use AD connect to Sync with azure AD. Or you can also use AD DS . ..

Does this mean that if i select Active directory --> that means i am adding my machine to Active directory configured with a VM and that would create a Computer within the computers container ? But my Ad is in sync with azure AZURE AD using adconnect ..

How these are two are different ?

2)Now if i have made my on premise sync with azure active directory using AD connect .. and my domain name is XYZ.COM ..

But i have also configured Custom Domain names like

Can i make use virtual desktop to work both with Custom domain and Actual on premise domain which has synced with Azure AD .. ?

Not sure how we can even make this configuration . And to which domain i will join the Host pool ?

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,441 questions
{count} votes

1 answer

Sort by: Most helpful
  1. prmanhas-MSFT 17,901 Reputation points Microsoft Employee

    @kumar kaushal I had discussion internally and got below response from our internal team:

    1) If they select Active Directory in the portal when creating a host pool, they need to specify the FQDN of their AD domain and also optional the OU path were the VM should land in. If they don't specify an OU, it will land in computers container.

    If this DC running in Azure is part of their on-premises AD as an additional DC, it doesn't make any difference. AD connect sync is only required once. If they want to build up an isolated AD in Azure with DCs running as VMs, they can do that, but this would then require an additional sync and also in most cases a separate AAD tenant. Seems to be a lot of overhead.

    2) AVD relies on the UPN, so, as long as the configure the UPN properly to match between AAD and AD, it will work.

    Hope it helps!!!

    Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.