Windows Autopilot deployment for existing devices: Create JSON file for Windows Autopilot profiles

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 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
• 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.

Create JSON file for Windows Autopilot profiles

Once the proper modules are installed to allow exporting of Windows Autopilot profiles from Intune, the next step is to export the Windows Autopilot profiles as JSON files. The JSON files are used to create a package in Configuration Manager.

To export the Windows Autopilot profiles as JSON files, follow these steps:

1. Sign into the Configuration Manager site server or other device where the required modules were installed in the Install required modules to obtain Windows Autopilot profiles from Intune step.

2. On the device, open a PowerShell window as an administrator by right-clicking on the Start menu and selecting Windows PowerShell (Admin)/Windows Terminal (Admin) and then selecting Yes at the User Account Control (UAC) prompt.

3. Copy the following commands by selecting Copy at the top right corner of the below PowerShell code block:

   Connect-MgGraph -Scopes "Device.ReadWrite.All", "DeviceManagementManagedDevices.ReadWrite.All", "DeviceManagementServiceConfig.ReadWrite.All", "Domain.ReadWrite.All", "Group.ReadWrite.All", "GroupMember.ReadWrite.All", "User.Read"
   $AutopilotProfile = Get-AutopilotProfile
   $targetDirectory = "C:\Autopilot"
   $AutopilotProfile | ForEach-Object {
       New-Item -ItemType Directory -Path "$targetDirectory\$($_.displayName)"
       $_ | ConvertTo-AutopilotConfigurationJSON | Set-Content -Encoding Ascii "$targetDirectory\$($_.displayName)\AutopilotConfigurationFile.json"
   }
   

4. Paste the commands into the elevated PowerShell window and then select Enter on the keyboard to run the commands. If the elevated PowerShell command window isn't already signed into Intune, a Sign in to your account window appears. Sign in with a Microsoft Entra account that has access to Intune and the Windows Autopilot profiles.

5. Once signed into Intune, Enter might need to be selected a second time to run the last command in the code block.

6. Once all the commands run successfully, the Windows Autopilot profiles appears in a subfolder under the folder specified by the $targetDirectory variable. By default, the $targetDirectory variable is C:\AutoPilot, but it can be changed to another location if desired. The subfolder has the name of the Windows Autopilot profile from Intune. If there are multiple Windows Autopilot profiles, each profile has its own subfolder. In each folder, there's a JSON file named AutopilotConfigurationFile.json.

Next step: Create and distribute package for JSON file in Configuration Manager

Related content

For more information on creating the JSON file, see the following articles:

• Create the JSON file.
• Get Windows Autopilot profiles for existing devices.