Autopilot Device Preparation – Overview

This will be the first post on the Autopilot Device Preparation series.

the first post is to provide an overview of the feature, highlighting its differences from normal Autopilot and outlining what is not supported. This post serves as an introduction to the series, with subsequent posts delving into the configuration process from an admin perspective and the user flow.

Simply, Autopilot Device Preparation – What it is ? 🤔

It is a new Autopilot experience that simplifies setting up and configuring devices for your organization.

It improves the onboarding experience by providing a profile experience to deploy configurations efficiently, consistently, and remove the complexity out of troubleshooting.

Supported Operating System: 🚀

• Only Windows 11 version 22H2 and 23H2 with KB5035942 or later included

For other requirements “Network, Configuration, RBAC and licensing” please check MS documentation

https://learn.microsoft.com/en-us/autopilot/requirements?tabs=software

Autopilot Device Preparation – What’s New

1. No Registration required.
   • No hardware hash upload required
   • Device must not be registered for Autopilot, if it is, it will go with normal Autopilot
2. Only “User-driven” deployment flow is currently supported, No Self-deploying , No pre-provisioning “for now”
3. Entra joined only – Hybrid Entra Joined is not supported
4. No separate ESP profile
   • ESP configuration is embedded in ADP profile
5. No Device dynamic group needed
   • Admin need to create a device security group “Enrollment Time grouping” and add it while creating the ADP profile
   • Apps, scripts, policies need to be assigned to this device security group.
6. Only Device based payload can be deployed during OOBE “up to 10”, user-based payload will be deployed when user reaches desktop.
7. ADP profile assigned to user group
   • The profile downloaded after the user sign-in, while with Autopilot V1 it is downloaded before the user sign-in
8. Windows ADP offers near real-time status updates on deployments, including app and scripts details and deployment time.
9. Can mix LOB and Win32 apps, as it will be deployed in sequential during device provisioning

What’s not supported in Autopilot Device Preparation

1. Enrollment status page.
2. Apps which require Managed installed policy.
3. Dynamic grouping during OOBE provisioning.
4. Custom compliance scripts during OOBE provision.
5. Hybrid Entra Joined

Check More articles on IntuneBytes