| title | description | ms.service | ms.localizationpriority | author | ms.author | ms.reviewer | manager | ms.date | ms.topic | ms.collection | ms.subservice | appliesto | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows Autopilot deployment for existing devices in Intune and Configuration Manager - Step 1 of 10 - Set up a Windows Autopilot profile |
Windows Autopilot deployment for existing devices in Intune and Configuration Manager - Step 1 of 10 - Set up a Windows Autopilot profile. |
windows-client |
medium |
frankroj |
frankroj |
jubaptis |
aaroncz |
06/19/2024 |
tutorial |
|
autopilot |
|
Autopilot user-driven Microsoft Entra join steps:
[!div class="checklist"]
- Step 1: Set up a Windows Autopilot profile
- Step 2: Install required modules to obtain Autopilot profiles from Intune
- Step 3: Create JSON file for Autopilot profiles
- Step 4: Create and distribute package for JSON file in Configuration Manager
- Step 5: Create Autopilot task sequence in Configuration Manager
- Step 6: Create collection in Configuration Manager
- Step 7: Deploy Autopilot task sequence to collection in Configuration Manager
- Step 8: Speed up the deployment process (optional)
- Step 9: Run Autopilot task sequence on device
- Step 10: Register device for Windows Autopilot
For an overview of the Windows Autopilot deployment for existing devices workflow, see Windows Autopilot deployment for existing devices in Intune and Configuration Manager.
Windows Autopilot deployment for existing devices isn't an Autopilot deployment where an Autopilot profile is downloaded and applied to a device during the out-of-box experience (OOBE) of Windows Setup. Instead, it prepares a device to receive an Autopilot profile by performing the following actions:
- Wipes the device.
- Installs a fresh copy of Windows.
- Installs a JSON file that contains the information for an existing Autopilot profile.
The first step in a Windows Autopilot for existing devices deployment is to make sure there's already an existing valid Autopilot profile in Intune so that the JSON file can be created. Since the JSON file only supports the user-driven Microsoft Entra join and user-driven Microsoft Entra hybrid join Autopilot scenarios, one of the following steps from the respective scenario workflows can be used to create a valid Autopilot profile:
- User-driven Microsoft Entra join: Create and assign user-driven Microsoft Entra join Autopilot profile
- User-driven Microsoft Entra hybrid join: Create and assign user-driven Microsoft Entra hybrid join Autopilot profile
Note
In the above steps, it's not necessary to assign the Autopilot profile for Windows Autopilot deployment for existing devices scenario to work. The Autopilot profile only needs to be created so that the JSON file can then be created.
Once a valid Windows Autopilot profile is created and confirmed working on an existing Autopilot device, then proceed to Step 2: Install required modules to obtain Autopilot profiles from Intune.
[!div class="nextstepaction"] Step 2: Install required modules to obtain Autopilot profiles from Intune
[!INCLUDE More information Autopilot profile]