3.1.1. Autopilot Deployment Profiles vs Device Preparation Policies
💡 First Principle: The two Autopilot experiences differ in when the device is bound to your tenant. Classic Autopilot binds it before it ever reaches the user, by registering its hardware hash; device preparation binds it at the moment the user signs in, by dropping it into a device group. Everything else — which modes are possible, how many apps you can deliver, whether there's a progress page — follows from that one difference, so ask "can I register this device in advance, and do I need what registration makes possible?"
Classic Windows Autopilot starts with registration: the device's hardware hash is uploaded and the device is associated with your tenant, ideally by the OEM or a reseller through Partner Center. You can register devices yourself — collect the hash with the Get-WindowsAutopilotInfo script and upload a CSV of up to 500 rows — but Microsoft positions manual registration mainly for testing. Registered devices are treated as corporate-owned. You then create a deployment profile (Devices > Windows > Device onboarding > Enrollment > Windows Autopilot > Deployment profiles), assign it to a device group, and usually pair it with an Enrollment Status Page (3.1.3). If a device's groups are assigned more than one profile, the device gets the oldest created one.
Autopilot device preparation, generally available since June 3, 2024, removes registration entirely. You configure two things: a device preparation policy and an assigned (static) security device group whose owner is the Intune Provisioning Client service principal (some tenants show it as Intune Autopilot ConfidentialClient). When the user authenticates during setup, Intune adds the device to that group — enrollment time grouping — and delivers the apps and scripts selected in the policy, which lives under Devices > Windows > Device onboarding > Enrollment > Windows Autopilot device preparation.
| Dimension | Classic Autopilot (deployment profile) | Autopilot device preparation |
|---|---|---|
| Pre-registration | Hardware hash required | Not required |
| Configure | Deployment profile + ESP | Device preparation policy + device group owned by Intune Provisioning Client |
| Join types | Microsoft Entra join and hybrid join | Microsoft Entra join only |
| Modes | User-driven, pre-provisioned, self-deploying, existing devices | User-driven and automatic |
| Delivered during setup | Up to 100 apps through device and user ESP | Up to 25 apps and 10 PowerShell scripts, device-based, during OOBE |
| Progress experience | Enrollment Status Page | Percentage progress indicator, no ESP |
| Windows versions | Supported Windows 11 and Windows 10 releases | Windows 11 only (24H2 or later, or 22H2/23H2 with KB5035942) |
| Mixing LOB and Win32 apps | Not supported | Supported |
| Reporting | Registered devices only, not real time | Near real-time deployment report |
A few details are easy to get wrong. The app limit rose from 10 to 25 on January 30, 2026; the script limit stayed at 10. Selected apps should be assigned to the device group and install in System context; other apps assigned to the group install after setup, and policies assigned to it sync but aren't tracked. By default, device preparation makes the user a standard user rather than a local administrator.
Device preparation also has features classic Autopilot lacks. Automatic mode attaches a policy to a Windows 365 provisioning policy and reached general availability on May 11, 2026 (3.1.5). Device association, added August 27, 2026, binds a physical Windows 11 device to the tenant before enrollment by writing a tenant-affinity marker into its UEFI firmware with TPM-backed attestation. Associated devices are automatically marked corporate-owned — so no corporate identifier upload is needed even when personal enrollment is blocked — and can receive device-targeted policies. You pre-associate devices with a CSV in Intune; removing an association is done on the device, not in Intune.
Both experiences can coexist, but any single device runs only one of them. If a registered device isn't associated with the tenant, the classic profile wins; if it is associated, device preparation runs.
⚠️ Exam Trap: The device preparation group must be an assigned security device group with the Intune Provisioning Client as its owner. A dynamic device group, or a group without that owner, is the classic wrong answer — device preparation doesn't use dynamic groups, and without the service principal as owner Intune can't add devices during setup.
Reflection Question: A company buys laptops from a retailer that can't register hardware hashes, and wants them Entra joined with 12 apps installed before the user reaches the desktop. Which Autopilot experience fits, what two objects do you create, and what would change your answer if the laptops had to be hybrid joined?