To redeploy an existing Windows device using Windows Autopilot, you must first register it with the Autopilot service. This process involves three sequential steps: Capture the device identity: On the existing computer (Computer1), a PowerShell script (Get-WindowsAutopilotInfo.ps1) is run to collect the unique hardware hash. This script saves the hardware hash and other device information into a CSV file. Register the device: The generated CSV file is then imported into the Windows Autopilot service. This is done through the Microsoft Intune admin center by navigating to Devices > Enrollment > Devices and selecting the "Import" option. This action registers the computer's hardware hash with your tenant. Initiate redeployment: Once the device is registered in Autopilot and a profile is assigned, the computer must be reset to the Out-of-Box Experience (OOBE). When the reset computer starts up and connects to the internet, it will contact the Windows Autopilot service, recognize its hardware hash, and automatically apply the assigned deployment profile for the new user. Incorrect Options: Generate a JSON file that contains the computer information: The standard process for manually collecting a device's hardware identity for Autopilot registration uses a PowerShell script that outputs a CSV file, not a JSON file. JSON files are used by Autopilot to store configuration profiles that are downloaded to the device during OOBE, not for uploading the hardware hash. Upload the file by running azcopy.exe: The azcopy.exe command-line tool is used for copying data to and from Azure Storage accounts. It is not the correct tool for importing device hardware hashes into the Windows Autopilot service. The import is performed directly through the Microsoft Intune portal's user interface or via the Microsoft Graph API.

Microsoft Learn | Manually register devices with Windows Autopilot: This document details

the process for registering existing devices.

URL: https://learn.microsoft.com/en-us/autopilot/add-devices

Reference: Under the "Add devices" section, Step 3 states, "Collect the hardware hash from

the new devices." and explains using the Get-WindowsAutopilotInfo script to create a CSV

file. Step 4, "Import the hardware hashes to Autopilot," instructs to "sign in to the Microsoft

Intune admin center" and use the import function.

Microsoft Learn | Windows Autopilot for existing devices: This guide covers the scenario of

repurposing a device.

URL: https://learn.microsoft.com/en-us/autopilot/existing-devices

Reference: The "Create the hardware hash file" section explicitly states to create a CSV file

containing the device information. The process then requires importing this file into Intune.

The final step is to reset the device using a task sequence or manually, which triggers the

Autopilot OOBE.