By Andrew Armstrong 
Microsoft now ships two different ways to Autopilot-enrol a Windows device into Intune: classic Windows Autopilot (v1) and the newer Autopilot Device Preparation (v2, often shortened to “APv2” or “Device Prep”). They aren’t a straight upgrade path — each covers different scenarios, and picking the wrong one for your estate causes real deployment failures. This guide breaks down exactly what’s different, what each one can and can’t do, and how to decide which to use.
Quick Facts
- Classic Autopilot downloads its profile before sign-in using a pre-registered hardware hash; Device Preparation delivers the profile after the user signs in with Entra ID during OOBE.
- Device Preparation is Entra-join only — it does not support Hybrid Entra join, pre-provisioning, or self-deploying/kiosk scenarios. Classic Autopilot still covers all of those.
- Device Preparation replaces the Enrollment Status Page (ESP) with a simplified percentage-based progress indicator and near real-time monitoring.
- Device Preparation can mix Win32 and LOB apps in one deployment; doing that in classic Autopilot can cause failures.
- Both currently support only the user-driven physical-device scenario on the v2 side — pre-provisioning and self-deploying modes are planned for Device Preparation but not available yet.
How the Two Actually Differ
The single biggest architectural difference is when and how the device gets its deployment profile. Classic Autopilot relies on a hardware hash uploaded to Intune ahead of time — the device recognises itself against that registration and downloads its profile before anyone signs in. Device Preparation skips hardware-hash registration entirely: the profile is delivered only after the end user authenticates with their Entra ID credentials during Windows setup (OOBE).
| Capability | Classic Autopilot (v1) | Autopilot Device Preparation (v2) |
|---|---|---|
| Profile delivery | Before sign-in, via registered hardware hash | After Entra ID sign-in during OOBE |
| Join type supported | Entra join, Hybrid Entra join | Entra join only |
| Pre-provisioning / white glove | Supported | Not yet supported |
| Self-deploying / kiosk mode | Supported | Not yet supported |
| Progress UI | Enrollment Status Page (ESP) | Simplified percentage progress bar |
| Monitoring | Standard Intune reporting | Near real-time deployment monitoring |
| Mixing Win32 + LOB apps | Can cause deployment failures | Supported in a single policy |
| Hardware hash required | Yes | No |
Where Device Preparation Falls Short (For Now)
Device Preparation currently only supports the user-driven scenario for physical devices, plus automatic deployment for Windows 365 Frontline shared devices (still in preview). Pre-provisioning and self-deploying modes are on Microsoft’s roadmap for Device Preparation but aren’t available in the initial release — if your deployment needs either of those, you’re staying on classic Autopilot for now.
The other hard blocker is Hybrid Entra join. Device Preparation profiles don’t support it at all. If your organisation still depends on on-prem Active Directory alongside Entra ID — common for shops running co-management with SCCM — classic Autopilot remains the only option for those hybrid-joined devices.
Choosing the Right One
Decision Checklist
- If devices need Hybrid Entra join, pre-provisioning, or self-deploying/kiosk mode: use classic Autopilot — Device Preparation can’t do any of these yet.
- If it’s a straightforward user-driven, Entra-joined physical device rollout: Device Preparation is faster to set up (no hardware hash collection) and gives better real-time monitoring.
- If the deployment mixes Win32 and LOB apps: prefer Device Preparation, since mixing them in classic Autopilot risks OOBE failures.
- Keep app counts lean regardless of which path you use — nearly 90% of successful Autopilot deployments use 10 or fewer apps during OOBE.
- Expect to run both side by side for a while: most estates will keep classic Autopilot for hybrid-joined and kiosk devices while moving straightforward user-driven rollouts to Device Preparation.
Frequently Asked Questions
Is Autopilot Device Preparation replacing classic Autopilot?
Not yet, and not entirely. Device Preparation currently only covers the user-driven, Entra-joined physical device scenario. Hybrid Entra join, pre-provisioning and self-deploying/kiosk mode all still require classic Autopilot.
Do I need to collect hardware hashes for Autopilot Device Preparation?
No. That’s one of the main simplifications – Device Preparation doesn’t require registering a device’s hardware hash ahead of time. The device gets its profile after the user signs in with Entra ID during setup instead.
Can I use Autopilot Device Preparation on hybrid-joined devices?
No. Device Preparation profiles only support Microsoft Entra join. If any devices need to be Hybrid Entra joined, you’ll need to enrol them through classic Windows Autopilot instead.
Why would mixing Win32 and LOB apps cause failures in classic Autopilot?
Classic Autopilot’s Enrollment Status Page enforces a stricter app-installation sequence during OOBE, and combining Win32 and line-of-business app types in the same policy has been a known source of installation failures. Device Preparation was built to support both app types together in a single deployment without that issue.
Part of the TechyGeeksHome Intune series — see the Microsoft Intune: The Complete Guide and the SCCM to Intune Co-Management Guide for the rest of the cluster.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.
