A service that simplifies device provisioning and setup for end users, enabling zero-touch deployment
Windows Autopilot hardware hashes can only be generated from a running Windows OS using the documented Windows methods. The provided documentation lists only Windows-based mechanisms (Configuration Manager, PowerShell script, Diagnostics page hash export, Desktop hash export) and explicitly describes collecting the hardware hash by booting the device into Windows and exporting management logs.
There is no documented method in the context to generate a Windows Autopilot hardware hash from Ubuntu or any other Linux distribution. The supported flow is:
- Boot the device into Windows.
- Collect the hardware hash using one of the supported Windows methods (for example, via the Diagnostics page export or PowerShell).
- Import the resulting CSV into Intune under Devices → Windows → Windows enrollment → Windows Autopilot → Devices → Import.
Because capturing the hardware hash requires Windows, reused devices that currently run Ubuntu would need to be reimaged or booted into Windows (even temporarily) to obtain a valid Autopilot hardware hash that can be checked against Intune/Autopilot registration.
References:
- Manually register devices with Windows Autopilot
- Self-deploying mode: Register devices as Windows Autopilot devices
- Pre-provision Microsoft Entra hybrid join: Register devices as Windows Autopilot devices
- User-driven Microsoft Entra hybrid join: Register devices as Windows Autopilot devices
- User-driven Microsoft Entra join: Register devices as Windows Autopilot devices
- Windows Autopilot