Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Windows Autopilot user-driven Microsoft Entra join steps:
- Step 1: Set up a Windows Autopilot profile
- Step 2: Install required modules to obtain Windows Autopilot profiles from Intune
- Step 3: Create JSON file for Windows Autopilot profiles
- Step 4: Create and distribute package for JSON file in Configuration Manager
- Step 5: Create Windows Autopilot task sequence in Configuration Manager
- Step 6: Create collection in Configuration Manager
- Step 7: Deploy a Windows Autopilot task sequence to collection in Configuration Manager
- Step 8: Speed up the deployment process (optional)
- Step 9: Run Windows Autopilot task sequence on device
For an overview of the Windows Autopilot deployment for existing devices workflow, see Windows Autopilot deployment for existing devices in Intune and Configuration Manager.
Run Windows Autopilot task sequence on device
Once the Windows Autopilot for existing devices is created, modified as needed, and deployed, the task sequence can be run on a device by following these steps:
Start the task sequence using the desired method based on how the task sequence deployment was configured:
- Configuration Manager Software Center
- PXE enabled distribution point
- Task sequence bootable media
Allow the task sequence to complete.
Once the task sequence completes, the device either restarts or shuts down depending on the shutdown or restart behavior selected in one of the following two steps:
The behavior of the device after the task sequence completes depends on whether the device restarted or shut down:
Restart: the device restarts as soon as the task sequence completes and then immediately boot into Windows for the first time and run OOBE. When OOBE runs, the Windows Autopilot JSON file is processed and the Windows Autopilot deployment starts.
Shutdown: the device shuts down and power off as soon as the task sequence completes. Shutting down the device gives the option to further prepare the device and then deliver it to an end-user. OOBE and the Windows Autopilot deployment start when the end-user turns on the device for the first time.
Important
A Windows Autopilot profile downloaded from Intune is used instead of the Windows Autopilot profile from the JSON file if the following conditions are met after the task sequence completes:
- Device is registered as a Windows Autopilot device in Intune.
- Device has a Windows Autopilot profile assigned to it in Intune.
The Windows Autopilot profile downloaded from Intune has priority over the local Windows Autopilot profile from the JSON file.
Next step: Register device for Windows Autopilot
Related content
For more information on running the Windows Autopilot task sequence on the device, see the following article: