Hybrid Entra Domain Joined Windows Enrollment with Intune Autopilot – 2026 Full Guide
Are you trying to bridge the gap between modern cloud deployment and on-premises Active Directory? In this video, I provide a complete, end-to-end walkthrough of setting up Microsoft Intune Autopilot for Hybrid Entra ID (Azure AD) Joined devices.
This setup allows you to give your users that seamless "out-of-the-box experience" (OOBE) while ensuring their devices still join your local domain and receive necessary on-prem configurations.
We cover every single step required to get this working successfully.
📺 Timestamps:
0:00 Introduction
[Insert Time] Step 1: Device Registration & Hardware Hashes
[Insert Time] Step 2: Configuring On-Prem GPO for MDM Enrollment
[Insert Time] Step 3: Entra Connect Configuration for Hybrid Join
[Insert Time] Step 4: Installing the Intune Connector for AD (ODJ)
[Insert Time] Step 5: Creating the Dynamic Device Group in Entra ID
[Insert Time] Step 6: Creating the Autopilot Deployment Profile
[Insert Time] Step 7: Configuring the Domain Join Profile (OU Path)
[Insert Time] Step 8: Testing the Final OOBE Experience
💡 Important Resources & Commands
Manual Hardware Hash Extraction:
If your vendor didn't upload the hash, use these PowerShell commands during the first boot screen (Shift + F10 to open CMD):
powershell
Set-ExecutionPolicy Bypass -Scope Process -Force
Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo -OutputFile C:\AutopilotHWID.csv
Dynamic Group Rule Syntax:
Use this rule to automatically catch Autopilot-registered devices:
(device.devicePhysicalIds -any _ -contains "[ZTDId]")
👍 If you found this guide helpful, please crush that Like button and Subscribe to the channel for more in-depth Microsoft Intune and IT tutorials!
Drop a comment below if you are stuck on any step or have questions about Hybrid Join!
#MicrosoftIntune #Autopilot #HybridADJoin #EntraID #ActiveDirectory #ITAdmin #Windows11Deployment