120: Autopilot Pre-provisioning
Overview
Windows Autopilot for pre-provisioned deployment is an Autopilot solution that automates the configuration of Windows on a new device delivered directly from an IT department, OEM, or reseller. The deployment is split up between the Technician flow and User flow phases so that the deployment is faster when the end-user receives the device. The deployment is faster because the IT department, OEM, or reseller completed the first portion of the deployment during the Technician flow.
Device ESP phase and user ESP phase are split and occur at two different points in time:
-
The IT department, OEM, or reseller handles the device ESP phase. This phase is known as the Technician flow. Once the Technician flow is complete, the device is powered down and delivered to the end-user.
-
When the end-user receives the device, they turn it on for the first time, and the device undergoes the user ESP phase. A portion of device ESP also reruns to ensure there are no new applications or policies assigned to the device since the Technician flow ran. This phase is known as the User flow.
| Scenario | Pros | Cons |
|---|---|---|
| Pre-provisioned | • Faster for user since IT admin/OEM/reseller handles bulk of device ESP during the technician flow. | • Requires interaction by IT admin/OEM/reseller. • Requires TPM attestation during technician flow so only works on physical devices with supported TPM (doesn't work in VMs even with virtual TPM). |