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)
I am currently syncing users and groups with password Hash sync (from on-prem ad to cloud)
To deploy WVD do I also have to enable single sign-on and pass-trough authentication with AD Connect and having Domain services running in Azure?
MicrosoftLA99-999_ : If you are using password hash sync, you should be good to go. Because you are already syncing the password hashes, you can choose either of the two options for your Active Directory in your virtual network:
a. Connect your network to your on-premises infrastructure with an ExpressRoute or Site-to-Site VPN, then domain-join your VMs to that Active Directory.
or
b. Enable Azure AD Domain Services in your Azure subscription, then domain-join your VMs to that Active Directory.
The key things to ensure are
1. Make sure you have DNS set up on your vNet to point to the DNS IP's of the AADDS Dc's\DNS
2. Make sure you force a password change on the account you are using to join the wvd's to the domain
https://docs.microsoft.com/en-us/azure/active-directory-domain-services/synchronization
"For cloud-only Azure AD environments, https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-create-instance#enable-user-accounts-for-azure-ad-ds in order for the required password hashes to be generated and stored in Azure AD. For any cloud user account created in Azure AD after enabling Azure AD Domain Services, the password hashes are generated and stored in the NTLM and Kerberos compatible formats. All cloud user accounts must change their password before they're synchronized to Azure AD DS."
3. The account used for the domain join doesn't have MFA enabled
I had problems with the domain join also for months but once i figured out I had to setup the environment in powershell first I got past it! 415Group_Ray
- I swear I've tried every article I could find on the matter (including those with PS commands). I still could not get passed domain joining my instance. I spent almost an entire day on it. Azure support was little help. If you could find the article you used I could give it a shot.
ADDS by itself we just retired on premise 3 weeks ago we use cloud authentication now and not having those noisy servers running all the time has been great! 415Group_Ray
- Thanks for the reply Tommy. Are you running a hybrid AD environment using Azure AD Connect? Or are you running Azure ADDS all by itself?
I have WVD running in a production environment and it is critical to business what I can say to get this going with aads you need to setup just about everything in powershell first then do your deployment. There is a document floating around here that helped me greatly. 415Group_Ray
- Any news on this? I'm testing out WVD on an Azure trial for potential use and running into the issue where I can't deploy using Azure ADDS only.
- Christian_Montoya
Marcel Biebricher : No, it does not. VMs domain-joined to the Azure AD DS instance cannot be configured to be hybrid, as Azure AD DS does not allow that.
We're continuing to investigate the "100% cloud" scenario, but nothing to report at this time.
Christian_Montoya Josh Bender Mike Amox
If we choose option "b.", does the scenario support hybrid Azure AD join for the VMs joined to Azure AD DS ?
According to https://docs.microsoft.com/en-us/azure/active-directory-domain-services/synchronization#synchronization-from-on-premises-ad-ds-to-azure-ad-and-azure-ad-ds for Azure AD Domain Services it is not supported to sync from Azure AD DS to Azure AD.Any news on support for "100% cloud"? Would love to see this 🙂
