Step by step tutorial for Windows Autopilot deployment for existing devices in Intune and Configuration Manager
This step by step tutorial guides through using Intune and Microsoft Configuration Manager to perform a Windows Autopilot deployment for existing devices.
The purpose of this tutorial is a step by step guide for all the configuration steps required for a successful Autopilot deployment for existing devices using Intune and Microsoft Configuration Manager. The tutorial is also designed as a walkthrough in a lab or testing scenario, but can be expanded for use in a production environment. This tutorial assumes familiarity with Microsoft Configuration Manager and that Microsoft Configuration Manager is already set up and configured to support operating system deployments.
Windows Autopilot deployment for existing devices overview
The main use case scenario for Windows Autopilot is to automate the configuration of Windows on a new device delivered directly from an IT department, OEM, or reseller. However, sometimes existing devices in an environment need to be repurposed, fixed, or updated to a later version of Windows by reinstalling Windows on the device. Reinstalling of Windows is usually performed via a reimage of the device, which is outside the capabilities of Windows Autopilot. Windows Autopilot also isn't able to perform a fresh install of Windows if the version of Windows is different than the one that is currently installed on the device. There might also be other conditions that prevent Windows Autopilot from performing a fresh install of Windows on the device. For example, corruption of the current Windows install or a hard drive failure.
Windows Autopilot can utilize Microsoft Configuration Manager task sequences tor scenarios where Windows needs to be:
- Reinstalled to a later version of Windows using a fresh installation of Windows.
- Updated to a later version of Windows using a fresh installation of Windows.
Microsoft Configuration Manager task sequences can reimage a device and perform a fresh installation of Windows. The Configuration Manager task sequence can also pre-install a Windows Autopilot profile on the device via a JSON file. Once the Configuration Manager task sequence is done, the device can then automatically run the Windows Autopilot deployment defined in the Windows Autopilot profile JSON file. When the Windows Autopilot profile JSON file is pre-installed on the device, the Windows Autopilot deployment can run on the device without having to first perform the following actions:
- Import the device into Intune as an Autopilot device.
- Assign an Autopilot profile to the device.
Windows Autopilot deployment for existing devices is useful for the following scenarios:
- Repurpose an existing device that isn't yet an Autopilot device.
- Migrate an on-premises domain joined device that isn't part of Microsoft Entra ID to a Microsoft Entra join device.
- Convert an on-premises domain joined device that is Microsoft Entra hybrid joined to a Microsoft Entra join device.
- Reinstall Windows on devices that need to be repaired. For example, a device that has a corrupted Windows installation or where the hard drive was replaced.
- Upgrade older versions of Windows that don't support Microsoft Entra ID (Windows 8.1) to a version of Windows that does support Microsoft Entra ID (Windows 10/Windows 11).
- Using custom Windows images instead of the OEM provided Windows installation.
Windows Autopilot deployment for existing devices can be viewed as a method to prepare an existing device for an Autopilot deployment.
Note
The JSON file for Windows Autopilot for existing devices only supports user-driven Microsoft Entra ID and user-driven hybrid Microsoft Entra Autopilot profiles. Self-deploying and pre-provisioning Autopilot profiles aren't supported with JSON files due to these scenarios requiring TPM attestation. TPM attestation only works where there's an existing Autopilot device since the TPM attestation information is stored in the Autopilot device object.
However, during the Windows Autopilot for existing devices deployment, if the following conditions are true:
- Device is already a Windows Autopilot device before the deployment begins
- Device has an Autopilot profile assigned to it
then the assigned Autopilot profile takes precedence over the JSON file installed by the task sequence. In this scenario, if the assigned Autopilot profile is either a self-deploying or pre-provisioning Autopilot profile, then the self-deploying and pre-provisioning scenarios are supported.
Workflow
The following steps are needed to configure and then perform a Windows Autopilot deployment for existing devices deployment using Intune and Microsoft Configuration Manager:
- 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
Important
If enrollment restrictions are configured to block personal devices from enrolling, Autopilot for existing devices can't be used. For more information, see What are enrollment restrictions?: Blocking personal Windows devices.
Walkthrough
Related content
For more information on Windows Autopilot deployment for existing devices, see the following articles: