Integrations
Windows Autopilot
Enlist reads each Windows PC's hardware hash and registers the PC in the client's own Windows Autopilot, so a reset or replacement PC sets itself up for the client.
Windows Autopilot lets a PC that is reset, or a new one straight from the box, set itself up for your client from the first Windows screen. For that, Microsoft needs the PC's hardware hash in the client's tenant. Enlist reads the hash on every Windows PC it manages and registers the PC for you, so nobody runs a script or uploads a CSV.
Before you start #
Connect the client's Microsoft 365 tenant on the client's page (see Microsoft 365 tenants). The app needs the Microsoft Graph application permission
DeviceManagementServiceConfig.ReadWrite.All, with admin consent in the client's tenant.The PC needs the Windows agent release that adds Autopilot (after 01.24.04). The agent reads the hash once a day, so a PC shows No hash yet until its next full inventory.
Register PCs #
- One PC
- On the device's page, Windows Autopilot shows when the hash was read. Choose Register in Autopilot. Microsoft usually takes a few minutes; the badge shows Microsoft is importing and then Registered.
- Every PC of a client
- On the client's page, under Windows Autopilot, choose Register to send every PC that has a hash and isn't registered yet.
- Automatically
- Tick Register every Windows PC in Autopilot once its hash arrives. Each new PC is registered after its first full inventory.
A PC that is already in the client's Autopilot (for example, registered by the reseller) is found by its serial number and shown as registered. Enlist sets your group tag on it if it has another one.
Group tag #
Intune dynamic groups and Autopilot deployment profiles can pick PCs by their group tag (for example (device.devicePhysicalIds -any (_ -eq "[OrderID]:HD-Standard"))). Set the client's tag on the client's page. It goes with each registration from then on; a PC already registered keeps its tag until you register it again.
Remove a PC from Autopilot #
On the device's page choose Remove from Autopilot and approve with your passkey. Microsoft forgets the PC; Enlist keeps managing it. To remove PCs when you retire them in Enlist, tick Remove a PC from Autopilot when it is retired in Enlist on the client's page. It is off by default, because a retired PC that is wiped and given to someone else at the same client should still set itself up.
Export the hashes #
For a tenant Enlist can't reach, choose Export hashes (CSV for Intune) on the client's page and approve with your passkey. The file has Microsoft's columns (Device Serial Number, Windows Product ID, Hardware Hash, Group Tag, Assigned User). In the Intune admin center, open Devices → Windows → Enrollment → Devices → Import. Treat the file as sensitive: each export is logged.
When it doesn't work #
| What you see | What to do |
|---|---|
| This edition of Windows can't give its hash | Windows Home and Server editions have no Autopilot hash. Upgrade to Pro, Enterprise or Education. |
| Microsoft didn't add the device to Autopilot (ZtdDeviceAssignedToOtherTenant …) | The PC is registered in another organization's Autopilot. That organization (or the reseller) has to release it first. |
| The app needs the permission DeviceManagementServiceConfig.ReadWrite.All | Add the permission to the app registration, then grant admin consent again from the client's page. |
| The PC got a new motherboard | Autopilot knows the PC by its old hardware. Choose Remove from Autopilot, wait until it shows Removed, then Register again. |
Last updated 2026-11-17. Something wrong or missing? Email [email protected].