Windows Autopilot / Entra Join: OOBE, ESP Progress and Pending Validation

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

This Hyper-V walkthrough follows a virtual machine through OOBE, organizational sign-in and the Enrollment Status Page in an intended Microsoft Entra Join scenario. It provides a visual sequence for discussing the difference between reaching the desktop and proving the complete provisioning path.

The evidence shows later ESP completion and desktop access. Autopilot registration, profile application, device identity and the current Intune state still require verification. The requester responsible for the shutdown or restart remains unidentified. Treat these as open checks when interpreting the sequence.

Related learning: Read Autopilot requirements — conceptual guide before the walkthrough. Compare hardware hash registration and profile assignment for the preparation stage; that related post is not proof that its registration record belongs to this execution. For a separate existing-device route, see Windows Cloud Enrollment — Part 1.

Official documentation: Consult Microsoft’s Enrollment Status Page reference, deployment profile instructions and Autopilot requirements to plan the missing verification steps.