Windows Autopilot vs. Windows Autopilot Device Preparation: In this post, I’ll explain the key differences between Windows Autopilot and Windows Autopilot Device Preparation. Both are designed to configure new Windows devices by managing the Out-of-Box Experience (OOBE), but they take different approaches.
📌 Windows Autopilot: It works best for organizations who need advanced customizations, hybrid join scenario, multiple device support and have already established or can establish a process to upload device hardware hash in Intune.
📌 Windows Autopilot Device Preparation: As of writing this post, this method supports only Microsoft Entra joined deployments and does not require collecting or uploading the hardware hash of devices. It is based on Enrollment time grouping and focuses on device-based targeting of apps and scripts delivered during OOBE.
The table below provides a quick summary of the differences between Windows Autopilot and Windows Autopilot Device Preparation. In the next sections, I provide a more detailed comparison along with my recommendation for the given scenario.
| Feature | Autopilot Classic (V1) | Autopilot Device Preparation (V2) |
|---|---|---|
| Setup requirement | Needs hardware hash upload | No pre-registration required |
| Join support | Entra join and Entra Hybrid join | Entra join only |
| OOBE screen | Enrollment Status Page (ESP) | Simple % progress screen |
| Targeting | Standard group targeting | Enrollment Time Grouping |
| Apps during setup | Can install many apps, may slow setup | Installs only critical apps/scripts [Up to 10] |
| Scripts | Supported | Supported (system context only) |
| Monitoring | Basic Intune reporting | Real-time app/script status with diagnostics |
| Pre-provisioning (White Glove) | Supported | Not supported |
| Windows version support | Windows 10 & 11 | Windows 11 only |
| Device types | Physical, VM, and VDI supported | Physical PCs, VMs, Windows 365 Frontline (preview) |
| Co-management | Supported (Autopilot into Co-management) | Not supported |
| Deployment modes | User-driven, self-deploying, pre-provisioning | User-driven, automatic (for Windows 365 Frontline) |
| User account type | Configurable (standard or admin) | Configurable (standard or admin) |
| When to use | Good for Hybrid or mixed OS environments | Best for Cloud first, Entra only scenarios |
| Time to desktop | Longer if many apps, policies, scripts install | Faster OOBE with minimal setup |
Contents
Windows Autopilot vs. Windows Autopilot Device Preparation
In the following sections, I’ll compare the features of Windows Autopilot and Windows Autopilot Device Preparation and highlight which method has the advantage in each case.
Device Registration
Windows Autopilot requires you to upload the device hardware hash to Intune before starting the provisioning process. In contrast, Windows Autopilot Device Preparation does not require the hardware hash. Instead, it uses Enrollment Time Grouping, which makes setup faster and more cost-efficient.
The Device Preparation method is easier to implement because it removes the need to upload a hardware hash. If you are working with a third-party vendor that charges for this step, eliminating it can help reduce overall costs.
🏆 Windows Autopilot Device Preparation ✅ No device registration required
Device Join types
Windows Autopilot supports both Microsoft Entra Join and Microsoft Entra Hybrid Join. However, the Windows Autopilot Device Preparation method currently supports only Microsoft Entra Join.
🏆 Windows Autopilot ✅ Supports both Microsoft Entra Join and Entra Hybrid Join
Supported Scenarios
Windows Autopilot supports several deployment modes, including User-Driven, Self-Deploying, and Pre-Provisioning (White Glove). In contrast, Windows Autopilot Device Preparation currently supports only User-Driven and Automatic (for Windows 365) modes.
🏆 Windows Autopilot ✅ Supports more deployment modes
Windows Version Coverage
Windows Autopilot supports Windows 10, Windows 11, and HoloLens (Autopilot #requirements), while Windows Autopilot Device Preparation is limited to newer Windows 11 builds (device preparation #requirements).
🏆 Windows Autopilot ✅ Supports multiple Windows OS
Cloud Services Support
Windows Autopilot Device Preparation supports Government Community Cloud High (GCCH) and Department of Defense (DoD) environments, whereas Windows Autopilot does not.
🏆 Windows Autopilot Device Preparation ✅ Supports (GCCH) and (DoD) cloud environments
Admin Effort
Configuring and managing Windows Autopilot requires more administrative effort because of device registration and ESP page setup. In contrast, implementing and managing Device Preparation involves less effort.
🏆 Windows Autopilot ✅ Less admin effort in deployment and management
LOB and Win32 App Deployment Support
With Windows Autopilot Device Preparation, you can deploy both line-of-business (LOB) and Win32 apps within the same deployment. In classic Windows Autopilot enrollment, mixing Win32 and LOB app installations can cause failures since both depend on the TrustedInstaller service running simultaneously.
🏆 Windows Autopilot Device Preparation ✅ Supports both LOB and Win32 apps in the same deployment
Monitoring and Troubleshooting
Windows Autopilot provides ESP status and standard reporting, while Device Preparation offers near real-time reporting for each app and script, along with simple options to export diagnostics.
🏆 Windows Autopilot Device Preparation ✅ Near Real Time Reporting
Overall OOBE Experience
Windows Autopilot uses the Enrollment Status Page (ESP), while Device Preparation provides a simplified percentage-based progress indicator without requiring ESP setup. Although there are a few additional OOBE screens with Device Preparation, the profile installs only essential apps and scripts during setup. This allows users to reach the desktop more quickly and delivers a smoother overall OOBE experience.
🏆 Windows Autopilot Device Preparation ✅Better and faster OOBE experience ✅ Time to Desktop
Autopilot Co-management Scenario
Windows Autopilot Device Preparation does not support co-management, and attempting to enable it during the Device Preparation flow may result in failed deployments. In contrast, Windows Autopilot (classic) supports co-management.
Autopilot into co-management is a classic Autopilot workflow that enrolls a new Windows device into both Intune and Configuration Manager during OOBE, making it co-managed from day one with workloads split according to your co-management settings.
Note
Autopilot vs. Device Preparation: Can you use both?
One of the most common questions is whether Autopilot and Autopilot Device Preparation can be used at the same time. The short answer is yes. The key point is not to assign both Autopilot and Device Preparation profiles to the same device. If you do, Windows Autopilot (v1) takes precedence and will be applied.
If a device is already registered with Windows Autopilot and you want to switch to the Windows Autopilot Device Preparation method, you must first deregister or delete the device from both Intune and Entra ID. For step-by-step instructions, refer to my post: Delete Windows Autopilot Devices from Intune and Entra ID.
