Microsoft Wants Organizations to Adopt Windows Autopilot Device Preparation for These Reasons

Microsoft is asking organizations to start moving eligible Windows Autopilot deployments to Windows Autopilot device preparation. The company says device preparation is now the recommended solution for user-driven scenarios, with future engineering work focused on improving the newer provisioning system.

Microsoft wants IT admins to start moving from Windows Autopilot

The change does not mean organizations have to abandon their existing Windows Autopilot deployments overnight. Microsoft says the two systems can coexist, allowing IT teams to move eligible Microsoft Entra joined Windows 11 devices in controlled waves while keeping unsupported scenarios on the older Autopilot path.

The reason for the shift is the way Microsoft has redesigned device preparation. Instead of spreading deployment settings across multiple Autopilot objects, a device preparation policy brings together OOBE settings, applications, PowerShell scripts, device naming and enrollment-time grouping. Microsoft also replaces the traditional Enrollment Status Page with a device preparation page that provides clearer progress information and more detailed deployment status.

Microsoft says the newer approach is designed to make provisioning simpler and troubleshooting easier. Current Microsoft Learn documentation also describes device preparation as a way to configure Windows devices using the existing OEM installation rather than maintaining custom images for different device models.

Not every Windows Autopilot deployment needs to move

Microsoft is specifically recommending device preparation for eligible user-driven scenarios, including corporate-owned Windows 11 devices, user-driven Microsoft Entra join deployments and Windows 365.

However, several existing Autopilot scenarios should remain on the older system for now. Microsoft lists pre-provisioning, self-deploying mode, hybrid Microsoft Entra join and Autopilot into co-management among the scenarios that should continue using Windows Autopilot.

Microsoft recommends starting with one eligible device population rather than attempting an organization-wide migration. Administrators can create static Microsoft Entra security groups, build device preparation policies around the required configuration and use enrollment-time grouping to place devices into the correct groups during enrollment.

One important part of Microsoft’s migration plan is that existing devices do not have to be reset immediately. Eligible devices can be pre-associated while they remain enrolled and in use. The new provisioning flow takes effect when the device next goes through a natural or required reset.