Device EnrollmentWindows Autopilot Deployment

Windows Autopilot Deployment

30 mins

Understanding the Concept

Windows Autopilot deployment begins with hardware hash registration. Hardware hashes can be collected from existing devices using a PowerShell script (Get-WindowsAutopilotInfo), uploaded via CSV to the Intune admin center, or registered automatically by OEM partners (Dell, HP, Lenovo) at purchase time.

Deployment profiles control the OOBE experience. User-driven deployment requires the user to sign in with their Azure AD credentials during OOBE. Self-deploying mode requires no user interaction and is ideal for shared devices and kiosks. Pre-provisioned deployment (formerly White Glove) allows IT to complete network-intensive setup before the user receives the device.

The Enrollment Status Page (ESP) tracks the progress of device setup, showing users which apps and policies are being installed. ESP can block device use until critical apps are installed, ensuring the device is fully configured before the user starts working.

Key Points

  • Hardware hash collection: PowerShell script, CSV upload, or OEM registration
  • User-driven: user signs in during OOBE, most common deployment mode
  • Self-deploying: no user interaction, requires TPM 2.0, for kiosks/shared devices
  • Pre-provisioned: IT prepares device first, user completes setup later
  • Enrollment Status Page (ESP) tracks and controls setup progress
  • Autopilot reset: wipe and re-enroll device without re-registering hash

Autopilot User-Driven Flow

Step 1

Power On

User turns on new/reset device

Step 2

Connect WiFi

Device connects to internet

Step 3

Sign In

User enters Azure AD credentials

Step 4

ESP

Apps and policies install with progress

Step 5

Desktop

Device ready for use

Why This Matters in Real Organizations

Autopilot transforms device provisioning from a labor-intensive IT task to a user-self-service experience. Organizations deploying Autopilot report 80% reduction in provisioning costs and enable direct-to-user device shipping worldwide.

Common Mistakes to Avoid

Not testing Autopilot profiles before large-scale deployment
Forgetting to configure ESP, causing users to access unconfigured devices
Using self-deploying mode without TPM 2.0 hardware support
Not creating dynamic device groups for Autopilot profile assignment

Interview Tips

  • Walk through the complete Autopilot deployment process
  • Discuss ESP configuration and why it matters
  • Explain how you handle Autopilot at scale with OEM registration

Exam Tips (MD-102)

  • Know the requirements for each Autopilot deployment mode
  • Understand ESP configuration options (block vs non-blocking)
  • Know how to troubleshoot Autopilot enrollment failures
  • Understand Autopilot reset vs fresh start vs wipe

Course Complete!

You've finished all lessons

←Previous|→Next|HHome