In recent times I have started to become a bit of an “expert, well I will use that word loosely” for Windows 10. Hybrid Azure AD Join is becoming a very popular option for a lot of the clients that I am currently working with and pops up all the time in discussions about “Modern Management” of Windows 10. I have experienced a few highs and lows when implementing Hybrid Azure AD Join and want to share that knowledge I have gain over the past 6 months.
What is Hybrid Azure AD Join?
Hybrid Azure AD Join is where your Windows 10 device is connected to your local Active Directory Domain and synchronized using Azure Active Directory Connect (AADC) to Azure AD.
Why would you do this?
This enables you to manage your Windows 10 devices from Microsoft Intune and leverage the offers from the cloud. Most organizations today have the required Microsoft subscriptions to implement Microsoft Intune but are unaware of how to start their journey.
What do I need for Hybrid Azure AD Join in a Managed Domain?
- Azure Active Directory Connect version 1.1.819 or greater
- Devices must be able to connect to the following URLs
- All Computer Objects from your on-premises Active Directory must be within the sync scope
- Service Connection point (SCP) is created for device registration (Completed via running AADC)
Implementing Hybrid Join for your organization
We are now going to run through the steps required to gear up your environment for Hybrid Join, first of all we are going to create the SCP using AADC. When you launch AADC you see “Configure device options”, select this option and proceed
In this section you will receive the following Overview of what can be configured and in this case, we are looking at Hybrid Azure AD Join only.
Hybrid Azure AD Join enables devices in your Active Directory forest to register with Azure AD for access management. Computers in your organization will automatically discover Azure AD using a service connection point (SCP) object that is created in your Active Directory Forest.
Device writeback is a prerequisite for enabling on-premises conditional access using AD FS and Windows Hello for Business. Device writeback synchronizes all devices registered in Azure AD back to on-premises. The device are synchronized to a device container that is created in your Active Directory forest.
Important NoteDevice writeback requires the Active Directory Schema version to be Windows 2012 R2 (level 69) or higher
You can confirm that the SCP has been created by launching ADSI Edit and browse to the location displayed below.
Now we have configured Active Directory we need to create a new GPO that configures the Windows 10 device to AutoEnroll into Azure AD. First of all we need the correct GPO templates installed in your SYSVOL, these templates can be download by the below URL.
Once you have installed the required GPOs to your primary domain controller you’ll be able to “Enable automatic MBM enrollment using default Azure AD”
Once this policy enabled and linked to the OU where your computers are located, they will become Hybrid Azure AD Joined.
This Microsoft link is your friend if you encounter any issues with Windows Enrollment Errors
You can also follow the official Microsoft documentation
The Author – Blogabout.Cloud