Import Windows Devices for AutoPilot using Microsoft Intune

Benoit LecoursIntune7 Comments

Windows Autopilot is a new and emerging solution designed that allows to setup and pre-configure Windows devices for your environment using Azure and Intune. The goal of Autopilot is to reduce the Os deployment complexity. If done correctly, a user logs to an out-of-box computer, logs on his computers with his ADD user account and applications and configurations gets deployed. All that with minimum infrastructure requirements.

When announced a couple of months ago, Autopilot has its flaws but it’s improving very fast. One of those flaws was that device importation was made from the Windows Store for Business or the Microsoft Partner Center. Those days are over since you can now import your device directly from Microsoft Intune.

Update 2018/04/09 – Intune now uses the same format as the Microsoft Store for Business, so you can directly upload a CSV created by the Get-WindowsAutoPilotInfo script.

Microsoft Intune Autopilot device import

  • Log to your Azure Portal and Launch Microsoft Intune
  • From the Intune portal, select Device enrollment / Windows enrollment / Devices
  • In the Windows Autopilot Devices pane, select Import on the top

Microsoft Intune Autopilot device import

 

From there, you need to select a .CSV file. It’s not possible to import a single device manually.

As shown in the portal, the CSV file has some formatting requirements :

  • <Serial Number>, <Windows Product ID>, <Hardware Hash>, <Order ID>
  • 175 rows maximum allowed

This means that you need the Serial Number, Windows Product ID, Hardware Hash and Order ID separated by a comma. You cannot have more than 175 rows/devices in the CSV.

Hopefully, there a good script is already available in Windows to get this information… but it’s not yet adapted for Microsoft Intune. The OrderID is not generated by the script so it needs to be added manually and the header is invalid.

From a Windows 10 1703+ computer

  • Start Windows PowerShell as Administrator
  • Run the following command: Install-Script -Name Get-WindowsAutoPilotInfo

Microsoft Intune Autopilot device import

  • This action places the script into the folder C:\Program Files\WindowsPowerShell\Scripts
  • Run the script : Get-WindowsAutoPilotInfo -Outputfile C:\temp\SCD.csv
  • The script will output the result in the C:\temp\SCD.csv file
  • Open the CSV file add an OrderID at the end (,1) and remove the header
  • Before change : (Invalid header and no OrderID at the end)

Microsoft Intune Autopilot device import

  • After (Remove header and add OderID)

Microsoft Intune Autopilot device import

  • Back in the Microsoft Intune Portal, select your CSV file and select Import at the bottom

Microsoft Intune Autopilot device import

  • You will receive an Import notification. It will take about 5-10 minutes

Microsoft Intune Autopilot device import

  • Device is imported

Microsoft Intune Autopilot device import

It will take a moment to show in your device list but will eventually appear. The device will also be visible from the Windows Store for Business portal. The device is now ready to use in an Autopilot deployment.

Share this Post

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

7 Comments on “Import Windows Devices for AutoPilot using Microsoft Intune”

  1. Is the hardware hash going to be the same for all identical models? If I have to get the machine out of the box, run a powershell script and reset before I can do the automation, it seems such a waste of time…

  2. Unfortunately this failed for me. I receive an ‘Internal Error, ERROR CODE: 640 – StorageError’

    This was after the Importer identified 1 correctly formatted row. So I’m not sure what is going on there..

    1. I got the same error message. In my case, my account has custom permissions in Intune. The import worked when I ran it using the Intune Admin account. Not sure what permission is required to import Window devices though.

  3. The need to modify the file was recently removed – Intune now uses the same format as the Microsoft Store for Business, so you can directly upload a CSV created by the Get-WindowsAutoPilotInfo script.

  4. This is inaccurate. Simply running the script nd performing an import works. No need to modify file!

  5. Thanks a lot, this worked for me! Small question, what is the OrderID for, and does it need to increment?

Leave a Reply

Your email address will not be published. Required fields are marked *