Use Windows Autopilot device preparation for the scenarios it actually supports

Source facts: device preparation and classic Autopilot are parallel choices

Microsoft’s current comparison of Windows Autopilot device preparation and Windows Autopilot describes device preparation as a re-architected provisioning option for supported Windows 11 scenarios. Microsoft does not present it as an automatic migration that replaces every classic Autopilot profile.

Windows Autopilot device preparation supports Microsoft Entra join, while classic Autopilot also supports Microsoft Entra hybrid join. Device preparation does not require pre-registering the device in Autopilot. Its policy is assigned to users and names a device group, with the Intune Provisioning Client configured as an owner; the device is added to that assigned group during provisioning. Microsoft identifies faster assignment processing and near-real-time reporting as benefits of this enrollment-time grouping approach.

The current comparison lists up to 25 essential applications and up to 10 essential PowerShell scripts during device-preparation provisioning. Only device-targeted configuration is delivered during the out-of-box phase; user-targeted settings continue afterward. Supported application types and current limits should be checked in Microsoft’s requirements and FAQ before design because the service can evolve.

Important scenario differences remain. Classic Autopilot supports pre-provisioned, self-deploying, and existing-device paths, Windows Autopilot Reset, Microsoft Entra hybrid join, Teams Meeting Room and HoloLens scenarios, DFCI, and broader out-of-box customization. Device preparation and classic Autopilot can coexist in a tenant, but a device runs one path. Microsoft states that a classic Autopilot profile takes precedence when a device is registered and assigned one.

DSE recommendation: decide by provisioning persona

Write a short persona for every deployment path before building policy. Examples include a new employee laptop shipped directly from a distributor, a replacement prepared by the help desk, a shared kiosk, a room system, a hybrid-joined workstation, and an existing device being repurposed. For each persona, record:

• Windows version and edition, ownership, and hardware source;
• Microsoft Entra join or hybrid-join requirement;
• user-driven, pre-provisioned, self-deploying, automatic, reset, or existing-device workflow;
• applications and scripts that truly must finish before the desktop is released;
• user-targeted configuration that may arrive after sign-in;
• network, proxy, licensing, enrollment-limit, local support, and recovery dependencies.

Select device preparation only where its current matrix fits all mandatory requirements. Do not force a hybrid join, Teams Room, technician pre-provisioning, or Autopilot Reset need into the new path because its name sounds more current. Classic Autopilot can remain the governed choice for those personas while device preparation serves eligible user-driven Windows 11 devices.

1. Minimize the blocking payload. Put only applications and scripts needed for first productive use into the essential list. Let nonessential software install after the desktop becomes available.
2. Make dependencies deterministic. Confirm application supersedence, detection, restart behavior, architecture, network sources, installation context, and ordering. Avoid scripts that assume a user-targeted setting already exists.
3. Pilot clean and previously known devices. Test representative models, languages, networks, direct shipment, help-desk staging, failed provisioning, retry, wipe, and reassignment. Verify which path wins when a device still has classic Autopilot registration.
4. Define acceptance. Require successful enrollment, expected Entra and Intune records, assigned group membership, essential applications and scripts, supported Windows build, management check-in, normal sign-in, application launch, and help-desk visibility.
5. Exercise exception handling. Document what the user sees, what support can diagnose, when to retry, when to wipe, and how to remove an obsolete registration without producing duplicate or stale records.

Measure setup duration, first-pass success, failure stage, application and script failures, time to productive desktop, duplicate records, support contacts, and devices routed to the wrong provisioning method. A successful rollout makes the simpler path genuinely simple while preserving other Autopilot modes where their capabilities are still required.

Official references

• Microsoft Learn, Compare Windows Autopilot device preparation and Windows Autopilot, April 2, 2025.
• Microsoft Learn, Windows Autopilot device preparation requirements.