Autopilot Device Preparation was Microsoft’s admission that the classic Autopilot flow had become fragile — too many moving parts, too much that only failed on a real device. Two recent changes make it genuinely more useful: automatic mode and a much higher app limit.
Automatic mode: no user in the loop
Classic device prep still expects a user to drive the out-of-box experience. Automatic mode removes that entirely — the device is added to its security group at enrolment time and gets its apps and scripts before anyone signs in. That’s exactly what you want for Windows 365 Cloud PCs and shared-device scenarios, where “wait for a user to click through OOBE” was never a sensible model. You build the policy, attach it to the provisioning flow, and the Cloud PC arrives already configured.
The app limit is now 25
The number of apps you can attach to a Device Preparation policy has gone up to 25, for both user-driven and automatic modes. That’s a real change in what’s practical — you can now deliver a proper baseline during provisioning rather than the bare minimum and a prayer.
But it moves the constraint. With 25 apps landing before handover, your deployment timeout is now the thing that bites, not the app cap. Every app you add is time on the provisioning clock, and blow past the timeout and the whole thing fails. So review your timeout when you use the extra headroom, and be honest about which apps genuinely need to be there before first sign-in versus which can trickle in afterwards.
Automatic mode plus 25 apps makes Device Preparation a real provisioning tool rather than a lightweight one. Just remember you’ve traded an app limit for a time limit.
Source: Microsoft Learn. Summarised independently — check the source for the latest detail.