Windows Autopilot Hybrid Microsoft Entra Join — Part 2: OOBE Execution and Verification

Estimated reading and study time: 60–75 minutes. Allow time to review 63 slides, inspect the evidence and absorb the concepts. This estimate excludes reproducing the procedures and waiting for installation, synchronization or policy delivery.

Part 2 follows OOBE execution, authentication, Enrollment Status Page progress and domain sign-in in an Autopilot Hybrid Microsoft Entra Join lab. It then compares the client with Entra and Intune records, helping readers trace device identity across the endpoint and the two management portals.

Later evidence confirms Hybrid Join and PRT, matching device IDs and reported compliance and policy results. Final ESP completion, MDE runtime health and the cause of the disabled device object remain open. Continuity between the VMware baseline in Part 1 and the Hyper-V execution shown here is unconfirmed.

Related learning: Read the Autopilot Hybrid conceptual guide for prerequisites and acceptance checks, then Part 1: Infrastructure Preparation and Configuration for the documented preparation. Use general Autopilot readiness to compare the hybrid route with other provisioning options.

Official documentation: Consult Microsoft’s Autopilot Hybrid workflow, Enrollment Status Page documentation and Autopilot requirements. Microsoft recommends Entra join for new deployments; assess the need for hybrid before reproducing this scenario. The dsregcmd reference explains the device and user SSO fields used in verification.