Autopilot Device Preparation aka Autopilot v2 - Part 1

Microsoft is currently rolling out  “next generation of Autopilot” called Autopilot Device Preparation.

I will, in a series of blogs, walk you through what’s new, comparing Autopilot v1 and Autopilot v2, requirements and how to setup and use.

What is Autopilot Device Preparation (ADP) ?

Autopilot Device Preparation (ADP) is the successor to Windows Autopilot (Autopilot) as we know today. Autopilot is not being replaced but will work side-by-side with ADP and there is no need to migrate from Autopilot to ADP.

ADP supports personal and corporate device ownership.
Because of the support for personal device ownership there is no need for hardware hashes as we know from Autopilot.
But… as most of us will not allow personal devices by using device platform restrictions, enrolling a device with ADP will fail.
In this scenario we will use Corporate Device Identifiers (I will dig in to this later).

Difference

Autopilot	Autopilot Device Preparation
Hardware Hash required	No Hardware Hash required
Autopilot Profile downloaded before sign-in	Profile downloaded after sign-in
The old ESP	Less complex ESP
Autopilot Profile assigned to devices	Device Preparation Profile assigned to users
Pre-Provisioning & Self-deploying possible	No Pre-Provisioning & Self-Deploying
ESP Tracking	BootStrapper Tracking (status/apps/scripts)
Hybrid support	NO hybrid
Windows 10 & 11	Windows 11

Requirements

Windows 11 22H2 with KB5035942
Windows 11 23H2 with KB5035942
User security group
Device security group with a particular owner

For more details, read the official Microsoft documentation
Windows Autopilot device preparation requirements | Microsoft Learn

In Part 2 I will go through the steps in setting up ADP.