https://www.sikich.com

Autopilot: Directly Uploading the Hardware Hash to Intune

Josh Reese

Mar 26 2025

3 min read

For IT professionals managing Windows Autopilot, the process of adding devices has traditionally involved coordinating with your hardware vendor to have the hashes automatically uploaded to Intune during the purchase process. Although that is the optimal way, you’ve probably found yourself in a situation where you need to manually export the hardware hash to a CSV and upload it. While this method works, it is cumbersome, error-prone, and time-consuming.

Fortunately, Microsoft has introduced a better way: directly uploading the hardware hash to Intune, streamlining the entire onboarding process.

The Old Way: Exporting to CSV

Previously, to register a device with Windows Autopilot, I had to extract the hardware hash using a PowerShell script and then save it as a CSV file. The process looked like this:

Boot the device into Windows.
Open PowerShell with administrator privileges.
Run the following command to collect the hardware hash:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted Install-Script -Name Get-WindowsAutoPilotInfo Get-WindowsAutoPilotInfo.ps1 -OutputFile C:\AutoPilotHWID.csv
Manually upload the CSV file to Microsoft Intune.

While functional, this approach had several drawbacks. First, it required multiple steps, increasing the likelihood of human error. If the CSV format wasn’t correct or an incorrect hash was uploaded, the device wouldn’t register properly. Additionally, this method introduced unnecessary delays, especially when deploying multiple devices.

The Better Way: Direct Upload to an MDM Service

With Microsoft’s enhancement, we can now bypass the manual export step and directly upload the hardware hash to Intune. This method automates the process, making device enrollment faster, more secure, and less prone to errors.

Here’s why this approach is better:

Eliminates Manual Handling: No more dealing with CSV files, ensuring fewer mistakes due to formatting errors or incorrect uploads.
Improved Security: Manually handling the hardware hash files introduces a risk of data exposure. Direct upload minimizes this risk by keeping the data within a controlled pipeline.
Saves Time: Especially in large-scale deployments, directly uploading the hardware hash accelerates the onboarding process, making IT teams more efficient.
Better Integration with Intune: Since Microsoft Intune supports this feature, it provides a more seamless experience, ensuring that enrolled devices are immediately ready for Autopilot provisioning.

How to Upload the Hardware Hash Directly

To take advantage of this new method, simply run the following command on a new device undergoing Windows Setup & Out of Box Experience (OOBE) after the screen connecting the device to a network (Wi-Fi or Ethernet):

Shift + F10 to open Command Prompt Powershell.exe [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Install-Script -Name Get-WindowsAutopilotInfo -Force Get-WindowsAutopilotInfo -Online

You’ll need to sign in with an account that is at least an Intune Administrator.

This command automatically retrieves the hardware hash and sends it directly to Intune, eliminating the need for CSV file handling.

Devices will now be registered faster and with fewer manual steps. IT admins can then proceed with assigning Autopilot profiles, ensuring devices are set up according to corporate policies.

Conclusion

The ability to directly upload the hardware hash to Intune is a game-changer for Windows Autopilot deployments. It simplifies the process, reduces errors, and speeds up device provisioning. If you’re still using the old CSV export method, it’s time to embrace the more efficient approach and make your Autopilot deployments smoother than ever.

By leveraging this improved workflow, IT teams can focus on what really matters—delivering a seamless and secure experience for end-users.

Have any questions about how to directly upload the hardware hash to Intune? Please reach out to our experts at any time!

This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.

About the Author

Josh Reese

Josh Reese is a Senior Network Consultant at Sikich, assisting clients in achieving their business objectives through technology and trusted advice. He holds a Bachelor’s degree in Computer Information Systems from The University of Akron, as well as several Microsoft certifications. His primary area of focus revolves around Microsoft’s Cloud services. This includes working with both Azure and Microsoft 365 environments in order to drive clients toward full cloud enablement.