Autopilot Error 808 – ZtdDeviceAssignedToOtherTenant on HP Device

The error 808 (ZtdDeviceAssignedToOtherTenant) indicates that the hardware hash being uploaded matches a device record that already exists in another tenant. A local wipe, reinstall, or regenerating the hash does not affect that cloud-side registration.

Answers to the specific questions:

1. Identifying which tenant holds the registration The tenant that currently owns the Autopilot registration is not exposed to other tenants. There is no supported way in Intune/Autopilot for an admin in one tenant to see which other tenant the device is registered to.
2. Releasing the hardware hash without knowing the previous tenant When a device is already registered to another tenant (808/ZtdDeviceAssignedToOtherTenant), the record must be removed from that tenant or by Microsoft Support. The documented path is:
   • First confirm the device is not already present in the current tenant (Intune admin center → Devices → Windows → Enrollment → Windows Autopilot → Devices). If it is present, delete it and re-import.
   • If the device record does not exist in the current tenant, Microsoft Support can remove the conflicting record after validating ownership.
   • For Microsoft Support to remove the record, the following must be provided:
     • The device CSV that triggers the error.
     • Proof of ownership (original bill of sale/invoice with serial number or other unique identifier and the company name).
     • Autopilot diagnostics logs from the device (Mdmdiagnosticstool.exe -area Autopilot -cab c:\out.cab). Microsoft Support does not need to disclose the previous tenant to remove the record; they only need to verify that the requesting organization owns the device.
3. Whether OEM escalation is the only supported path OEM escalation is not the only supported path. The supported options are:
   • If the device is visible in the current tenant’s Windows Autopilot devices list, delete it there and re-import.
   • If the device is not visible in the current tenant, open a support request with Microsoft, provide proof of ownership, the CSV, and diagnostic logs, and request removal of the existing Autopilot registration.

Practical steps based on the documented process:

1. In the Microsoft Intune admin center, go to:
   • Devices → Windows → Enrollment → Windows Autopilot → Devices.
   • Search by serial number and confirm the device is not already listed. If it is, delete it and wait for deletion to complete, then re-import the CSV.
2. If the device is not listed:
   • Collect the CSV that fails with error 808.
   • Collect proof of ownership that meets the documented requirements (original document, includes serial/chassis ID, includes company name).
   • On the device, run:

          Mdmdiagnosticstool.exe -area Autopilot -cab c:\out.cab
     

   • Open a support request from the Intune admin center and attach the CSV, proof of ownership, and the out.cab file, asking for the Autopilot record to be removed from the other tenant.

Once Microsoft Support removes the existing record, the hardware hash can be imported into the current tenant without error 808.

References:

• Error 806 or 808 when you import Windows Autopilot device CSV files in Intune
• Manually register devices with Windows Autopilot