Validate Autopilot registration CSVs before assigning users

Source facts

Microsoft limits its recommendation for 4K hardware-hash registration through Intune to testing or other limited uses. The import checks the assigned user’s domain, not whether the individual UPN identifies the intended existing user. An invalid assignment can make the device inaccessible until that assignment is removed. Microsoft also requires the CSV to be edited as plain text rather than saved with Excel. Microsoft Learn.

Applicability

Use this review for an approved limited manual-registration exercise. Identify the devices, intended tenant, account assignments, and person responsible for the import before collecting their hardware hashes.

DSE recommendation

Keep the hardware-hash file in a restricted working location. Have a second operator compare each proposed user assignment with the authoritative account record and approved device allocation. Review the complete file against the source’s formatting requirements after editing. Begin with a small, explicitly identified set and keep a record of which rows were submitted.

Verification

Inspect the resulting Autopilot entries and compare serial numbers and user assignments with the approved input. Test the intended sign-in on a designated pilot device before releasing the remainder. If an unexpected assignment appears, stop further imports and have the enrollment owner correct that specific record. Preserve sanitized validation results, not hardware hashes in ordinary support tickets.

Official references

Microsoft Learn: Manually Register Devices with Windows Autopilot.