Rıza KorkusuzTechnical Support
Device provisioning

Windows Autopilot Explained

Zero-touch Windows setup, hardware hash registration, the Enrollment Status Page and common troubleshooting.

Study guideUpdated 2026-10-20Original notes and diagrams

Study guide, not an experience claim. I wrote these notes while studying this tool for IT support and service desk work. I have not administered it in production. Everything here is summarized in my own words from public documentation and lab-style thinking. Confirm details in the current official documentation, because these products change often.

What it is

Windows Autopilot is a set of cloud services that sets up a new (or reset) Windows device for work without IT building a custom image. The device is registered in advance; when the user powers it on and connects to the internet, Windows recognizes it as a company device, shows the company's branded sign-in, joins Entra ID, enrolls in Intune and installs the required apps and policies.

Why organizations use it

  • Ship laptops straight from the vendor to the employee (zero-touch).
  • Replace time-consuming imaging with a standard, policy-driven setup.
  • Reset a device and re-provision it for the next user (Autopilot Reset / fresh start).
  • Consistent security from the first sign-in: BitLocker, updates, Defender.

How it works

The user-driven mode, step by step:

Windows Autopilot user-driven enrollment flow1. RegisterHardware hash uploaded2. ProfileDeployment profile assigned3. Power onOOBE + internet4. Sign inBranded login + MFA5. EnrollIntune enrollment6. ESPEnrollment Status PageWindows Autopilot user-driven enrollment flow1. RegisterHardware hash uploaded2. ProfileDeployment profile assigned3. Power onOOBE + internet4. Sign inBranded login + MFA5. EnrollIntune enrollment6. ESPEnrollment Status Page
User-driven mode. Pre-provisioning and self-deploying modes change who does which step.

Common service desk tasks

  • Confirm a device's serial number is registered and has a profile assigned before shipping.
  • Help a user stuck on the Enrollment Status Page: note which phase (device setup or account setup) and which app.
  • Collect diagnostics: press Shift+F10 at OOBE only if policy allows, or use the ESP's 'Collect logs' option.
  • Request a reset / re-provision when a device is reassigned.

Troubleshooting steps

  1. No company sign-in screen? Check internet at OOBE, then whether the device is registered and the profile shows Assigned. Profile assignment can take time after registration.
  2. Wrong sign-in / 'this account is not allowed': check user licensing (Intune) and enrollment restrictions.
  3. Stuck on ESP: find the app or policy that is still installing or failed; a single required app often blocks completion.
  4. Hybrid join timeouts: needs line of sight to a domain controller (VPN or on-site) and the connector; check with the endpoint team.
  5. Record serial number, time, ESP phase and error code, and attach logs to the ticket.

Glossary

OOBE
Out-of-box experience: the first-run Windows setup screens.
Hardware hash
A device fingerprint used to register it with Autopilot.
Deployment profile
Settings that control OOBE and join type.
ESP
Enrollment Status Page that tracks app and policy installs during setup.
Pre-provisioning
IT or a partner pre-installs apps before handing to the user (formerly 'white glove').
Self-deploying
Kiosk/shared devices that set up without user sign-in.

Official documentation