Microsoft has laid out a clear message for IT administrators: it’s time to move to Windows 11 Autopilot device preparation, and it wants admins to act soon. The company published guidance covering both how to make the transition and why the timing matters for organizations that rely on zero-touch device deployment.
For admins who manage large fleets of Windows machines, the way you provision and configure new hardware is constantly evolving. Microsoft’s latest push centers on a workflow that lets organizations pre-configure devices before they reach end users, and the messaging suggests the window to make the switch is narrowing.
What Autopilot device preparation is
Windows Autopilot has long been Microsoft’s flagship zero-touch deployment solution. It lets organizations deploy and configure new Windows devices—laptops, desktops, and workstations—without manually imaging each one. Devices are registered in the cloud, and when a user powers one up for the first time, it pulls down the correct settings, apps, and accounts automatically.
Autopilot device preparation builds on that foundation for an earlier stage of the lifecycle. It’s designed for the pre-boarding phase, letting IT admins, system integrators, and software vendors install apps and configure settings on devices before they ship to the organization or the end user. In practice, this means a device can arrive already customized to an organization’s standards instead of requiring a separate configuration step after delivery.
Why Microsoft is pushing the transition now
Microsoft’s guidance frames the move to device preparation as something admins shouldn’t delay. While the company hasn’t publicly spelled out a hard deadline in the summary of its announcement, the tone is unmistakable: adopting the newer preparation workflow now beats waiting.
The broader context is Microsoft’s ongoing effort to modernize how Windows devices are provisioned. As the company consolidates and updates its deployment tooling, older approaches to device setup increasingly fall out of favor. Aligning with the current preparation workflow means your deployment practices stay supported and compatible with future Windows releases.
The practical risk of waiting is that your current setup process can quietly drift out of step with where Microsoft is taking device provisioning. Getting ahead of the transition keeps you from being forced into a rushed migration later, when you’d have less time to test and coordinate.
How admins can transition
According to Microsoft, the company has published step-by-step guidance for moving from the standard Windows Autopilot flow to the device preparation approach. The transition targets the admins and partners who pre-configure hardware, so the steps focus on the provisioning and customization side rather than the end-user out-of-box experience.
For organizations that work with system integrators or independent software vendors, the transition often means updating how you hand off configuration responsibilities. The new workflow is intended to fit into the existing Autopilot toolset, so you aren’t necessarily abandoning what you already have—rather, you’re adopting the updated preparation path on top of it.
What this means for you
If you provision Windows devices for an organization, treat this as a nudge to review your current setup process. The practical takeaway is straightforward: get familiar with the device preparation workflow now rather than later, so your deployments don’t fall behind as Microsoft continues to evolve its tooling.
For most end users, there’s nothing to do. The change happens behind the scenes in how devices are prepared and shipped. But for IT teams and partners managing the pre-boarding phase, treating this as a near-term to-do item will keep your deployment practices current.
How to get it
Microsoft’s guidance is available through its official documentation, which walks admins through the transition from Windows Autopilot to device preparation. If you manage devices via Autopilot, the best first step is to read through Microsoft’s published steps and compare them against your current workflow to spot any gaps.
Because the transition touches the pre-configuration stage, it’s worth coordinating with any system integrators or software vendors who customize your hardware before delivery, ensuring everyone is aligned on the updated preparation process.
Source: Neowin
Over to you: As an admin, are you planning to move your device preparation workflow to the new approach this quarter, or do you have reasons to hold off?
