Windows Autopilot
In plain English
Plain definition
Windows Autopilot is a Microsoft cloud service that provisions and pre-configures new or reset Windows devices using existing hardware identity, reducing manual imaging while requiring correct device registration and Intune enrolment policy.
Technical Definition
Windows Autopilot is a deployment and management capability that associates a device’s hardware hash (a unique identifier derived from device attributes) with an organisation’s tenant in Microsoft Intune and Microsoft Entra ID. When a registered device is powered on and connected to the internet, it queries the Autopilot service, receives its assigned deployment profile, and proceeds through automated Entra ID join, Intune enrolment and policy application, rather than a wiped, manually imaged, or generically enrolled state.
Operational Relevance
Autopilot is used by IT operations teams to eliminate manual imaging pipelines for corporate Windows fleets. It supports scenarios including user-driven deployment, self-deploying mode for kiosk or shared devices, and pre-provisioning (formerly known as White Glove) for partner or IT-staged setup before devices reach end users. Correct operation depends on accurate hardware hash registration, network connectivity to Microsoft cloud endpoints during OOBE, and an assigned deployment profile; misconfiguration in any of these commonly causes enrolment to stall or fall back to a standard OOBE flow.
Architecture Relationship
Windows Autopilot sits between hardware procurement and endpoint management. It depends on Microsoft Entra ID for identity and device registration, and on Microsoft Intune for policy, profile and compliance enforcement after enrolment. OEMs or resellers can register hardware hashes directly with Microsoft on an organisation’s behalf, or administrators can upload hashes gathered from existing devices. Autopilot itself does not perform imaging; it orchestrates the identity join and policy delivery that determine what configuration a device receives.
Example
An organisation purchases laptops from an OEM that has registered their hardware hashes to the customer’s tenant. On first boot, each laptop reaches the internet, contacts the Autopilot service, is recognised by its hardware hash, and is assigned a deployment profile that enforces Entra ID join, Intune enrolment, and a defined set of apps and policies, all without IT staff physically handling the device.
Common Misunderstanding
A frequent misunderstanding is that Windows Autopilot performs operating system imaging or reinstallation. It does not: Autopilot configures an existing, already-installed Windows image by driving identity join and policy assignment. If a device requires a different OS version or a full reimage, that is a separate provisioning step outside Autopilot’s scope.
Related Terms
- Microsoft Intune
- Microsoft Entra ID
- Enrollment Status Page (ESP)
- Mobile Device Management (MDM)
- Out-of-box experience (OOBE)
Further Reading and Verification Boundaries
Readers should confirm current Autopilot deployment profile options, supported enrolment modes and licensing prerequisites against Microsoft’s official documentation before implementing or troubleshooting a deployment, since these details are version- and tenant-configuration-sensitive.