What’s changed
Windows Autopilot device preparation now supports managed installer policy for apps installed during the provisioning phase. Previously, app control policies could interfere with how apps were delivered during the device preparation window. With managed installer policy applied, apps that are delivered through an approved installer are trusted, which makes supported app installations during provisioning more reliable.
Why it matters for IT admins
If your organisation uses application control alongside Autopilot, this reduces the risk of provisioning-time app failures caused by policy blocking. Approved apps install more consistently across the fleet, which is particularly valuable where the device preparation policy includes several required apps or where app control is enforced from day one.
What to do next
Treat this as an opportunity to validate your existing configuration rather than a change that needs immediate action. Confirm your app control and managed installer settings line up with what Autopilot device preparation expects, then prove the end-to-end flow before you touch production.
- Review your current managed installer and app control policies for compatibility with Autopilot device preparation.
- Confirm the apps assigned to your device preparation policy are delivered through an approved installer.
- Run a full provisioning test on pilot hardware and check that each required app installs and reports success.
- Watch enrolment status and app install results for the first production batch before scaling out.
Bottom line
This is a quiet but useful reliability improvement for anyone combining application control with Autopilot device preparation. The work on your side is verification: check the policies, test a provisioning run, then roll forward with confidence.
Source: Microsoft Learn. Summarised independently — check the source for the latest detail.