Windows Autopilot: Requirements and Deployment Readiness

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

This conceptual guide organizes Windows Autopilot readiness across software and hardware, cloud connectivity, licensing, tenant configuration and administrative permissions. It distinguishes classic Autopilot, device preparation and device association, then closes with a checklist for deciding whether a pilot is ready to begin.

The guide explains prerequisites rather than documenting a successful deployment. Select the intended Autopilot solution first, then verify its own support matrix, permissions and network dependencies; similarly named workflows should not be treated as interchangeable.

Related learning: Apply the registration concepts in Hardware Hash Registration and Profile Assignment and inspect the intended deployment experience in OOBE, ESP Progress and Pending Validation. For the hybrid route, read Autopilot Hybrid requirements and deployment workflow, which links to the two-part infrastructure and execution lab. For the existing-device cloud enrollment route, compare Windows Cloud Enrollment — Part 1 and Part 2: Policies, Security and Corporate Branding.

Official documentation: Start with Microsoft’s Autopilot requirements and manual device registration guidance, then review deployment profile configuration. The Enrollment Status Page reference explains the provisioning progress shown in the lab.