Introduction to Endpoint ManagementWindows Autopilot Overview

Windows Autopilot Overview

20 mins

Understanding the Concept

Windows Autopilot is a collection of technologies that simplify Windows device provisioning. Instead of creating and maintaining custom images, Autopilot uses the OEM-installed Windows image and transforms it into a business-ready state during the Out-of-Box Experience (OOBE).

The Autopilot process works by registering device hardware IDs with the Autopilot service. When a user powers on a new or reset device and connects to the internet, the device checks in with Autopilot, receives its deployment profile, and automatically configures itself - joining Azure AD, enrolling in Intune, installing apps, and applying policies.

Autopilot deployment profiles define the OOBE experience: user-driven (user signs in during setup), self-deploying (no user interaction needed - for kiosks/shared devices), and pre-provisioned (IT completes device prep, user completes remaining steps).

Key Points

  • Autopilot eliminates custom imaging - uses OEM Windows installation
  • Devices registered via hardware hash (CSV upload or OEM registration)
  • User-driven: user completes OOBE with Azure AD sign-in
  • Self-deploying: zero user interaction for kiosks and shared devices
  • Pre-provisioned: IT prepares device, user completes later (white glove)
  • Works with new devices and device reset/repurpose scenarios

Autopilot Provisioning Flow

Step 1

Register

Hardware hash uploaded to Autopilot

Step 2

Profile

Deployment profile assigned to device

Step 3

OOBE

User powers on, connects to internet

Step 4

Configure

Azure AD join, Intune enroll, apps install

Why This Matters in Real Organizations

Autopilot reduces device provisioning from hours to minutes, eliminates the need for imaging infrastructure, and enables direct-to-user shipping. Organizations save an average of 2-3 hours per device and can provision devices anywhere in the world.

Common Mistakes to Avoid

Not registering hardware hashes before shipping devices to users
Using self-deploying mode when user-driven is more appropriate
Not testing Autopilot profiles with different network conditions
Forgetting to assign an Enrollment Status Page (ESP) for app installation tracking

Interview Tips

  • Explain the Autopilot deployment modes and when to use each
  • Discuss how Autopilot eliminates the need for traditional imaging
  • Describe the hardware hash registration process

Exam Tips (MD-102)

  • Know all three Autopilot deployment modes and their requirements
  • Understand hardware hash registration methods
  • Be familiar with the Enrollment Status Page (ESP) configuration

Course Complete!

You've finished all lessons

←Previous|→Next|HHome