Export an Autopilot hardware hash and import it into Intune

What you need before step 1

Applies to: Windows 11 and Windows 10 devices registered manually with Windows Autopilot in Microsoft Intune (as documented, Microsoft Learn page updated 29 October 2026).

7 steps

1. 1

   Open an elevated PowerShell on the device

   Where: The Windows device: Start > type PowerShell > right-click Windows PowerShell > Run as administrator

   On a device that has finished setup, open Windows PowerShell as administrator. On a new device still at the out-of-box experience (OOBE), press Shift+F10 at the sign-in prompt to open Command Prompt, then type powershell.exe and press Enter.

   powershell.exe

   You should see: A PowerShell prompt starting with PS C:\ (from OOBE it may start in C:\Windows\System32).
2. 2

   Install the Get-WindowsAutopilotInfo script

   Where: The elevated PowerShell window on the device

   Enable TLS 1.2, create a working folder, add the scripts folder to the path, allow the script for this session only, and install it from the PowerShell Gallery. If prompted to install NuGet from PSGallery, type Y.

   [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
   New-Item -Type Directory -Path "C:\HWID"
   Set-Location -Path "C:\HWID"
   $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
   Install-Script -Name Get-WindowsAutopilotInfo

   You should see: The prompt returns without errors and the script is installed.
3. 3

   Option A: save the hash to a CSV

   Where: The elevated PowerShell window, in C:\HWID

   Run the script with -OutputFile. Copy C:\HWID\AutopilotHWID.csv to a USB drive or share. Add -Append with the same file name when collecting several devices into one file.

   Get-WindowsAutopilotInfo -OutputFile AutopilotHWID.csv

   You should see: C:\HWID\AutopilotHWID.csv exists and contains a header line and one device line.
4. 4

   Option B: upload the hash straight to Intune

   Where: The elevated PowerShell window on the device

   Skip the CSV and upload directly. A Microsoft Entra sign-in prompt appears; sign in with an account that is at least an Intune Administrator. You can add -GroupTag to tag the device.

   [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
   Install-Script -Name Get-WindowsAutopilotInfo -Force
   Get-WindowsAutopilotInfo -Online

   You should see: After sign-in the script reports the device was imported. Skip to the Sync step.
5. 5

   Check and combine the CSV

   Where: Notepad on your admin PC

   Open the CSV in Notepad. The header must be exactly as below (headers are case-sensitive). Serial number and hardware hash are required; product ID, group tag and assigned user are optional. Do not add columns or quotation marks, save as ANSI (not Unicode), and keep each file to 500 device rows or fewer.

   Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User
   <serialNumber>,<ProductID>,<hardwareHash>,<optionalGroupTag>,<optionalAssignedUser>

   You should see: One header line, then one line per device, saved as ANSI text.
6. 6

   Import the CSV into Intune

   Where: Microsoft Intune admin center > Devices > Windows > Enrollment > Windows Autopilot > Devices

   Sign in at https://intune.microsoft.com. Select Devices, under By platform select Windows, under Device onboarding select Enrollment, then under Windows Autopilot select Devices. In the toolbar select Import, browse to the CSV and select Import.

   You should see: Intune shows the import is in progress. It can take several minutes.
7. 7

   Sync and refresh

   Where: Microsoft Intune admin center > Windows Autopilot devices

   When the import finishes, select Sync in the toolbar, then select Refresh until the devices appear.

   You should see: A message says synchronisation is in progress, then the devices appear in the list by serial number.

Expert tips

How to confirm it worked

• In Windows Autopilot devices, search for the device's serial number and confirm it is listed (with the group tag if you set one).

• On the device, compare the serial number shown in Intune with Get-CimInstance Win32_BIOS | Select-Object SerialNumber.

• After you assign a deployment profile, check the device shows the profile as assigned before you reset or start OOBE.

How to reverse it

Errors you might see

Questions

Official sources

Vendors change menus and requirements. Confirm on the source before you rely on a detail. Last checked 4 Nov 2026.