This week I’m going to show the import experience of Windows AutoPilot devices in Microsoft Intune. About three months ago, this wasn’t possible yet and it was still required to use the Windows Store for Business (see this blog post). Even up until a few weeks ago it was still required to perform additional steps with the formatting. Now the experience is really straight forward.
I was planning on showing that experience during my session last week, at the Microsoft Tech Summit, but after speaking to many people onsite I noticed that it would be better to spent more time on explaining what Windows AutoPilot is and what Windows AutoPilot is not. Setting the expectations. An easy comparison with car and aircraft functionality helped a lot (together with some statements about what Windows AutoPilot does and what Windows AutoPilot does not do).
Now, back to the subject of this post, let’s have a look at the latest import experience by getting the device information and than importing that information in Microsoft Intune.
Get device information
To get the required device information, I’m using the latest version of the Get-WindowsAutoPilotInfo PowerShell script. That script is the easiest method to get the required information, especially for testing purposes. An alternative could be the Windows AutoPilot Device Information report in Configuration Manager, version 1802 or later. The script can create a CSV with a column for the Device Serial Number, the Windows Product ID and the Hardware Hash of the device. With the latest version of the script the value for the Windows Product ID will be skipped. Simply follow the next four steps.
Note: Keep in mind that the script can also run with a Partner switch, which will make sure that also the Manufacturer name and Device model are collected and reported.
Import device information
Now import the Windows AutoPilot device information into Microsoft Intune. The import process in Microsoft Intune can now also handle a header row in the CSV and an empty column for the Windows Product ID. This wasn’t possible until a couple of weeks ago. To import the device information, simply follow the next five steps.
|1||Open the Azure portal and navigate to Intune > Device enrollment > Windows Enrollment;|
|2||On the Devices enrollment – Windows enrollment blade, click Devices below Windows AutoPilot devices (Preview) to open the Windows AutoPilot devices (Preview) blade;|
|3||On the Windows AutoPilot devices (Preview) blade, click Import to open the Add Windows AutoPilot devices blade;|
|4||On the Add Windows AutoPilot devices blade, select the just created CSV (MyComputer.csv) and click Import to trigger the import process;
Note: Selecting the CSV will immediately trigger a check on the formatting of the CSV.
|5*||Back on the Windows AutoPilot devices (Preview) blade, click Sync followed by Refresh to speed up the process to show the devices in Microsoft Intune;|
*At this moment the Microsoft Intune experience might still be a bit out of sync (it’s still preview) with the Windows AutoPilot deployment service, which is why I’ve added this step to manually trigger the sync.
21 thoughts on “Import Windows AutoPilot devices in Microsoft Intune”
At mr Niehaus session about Autopilot advice was to still use the Business Portal cause the Intune Portal was not as ‘Stable’. Furthermore you can also use the Partner Portal. Benefit of this is you dont need to run the script and harvest the Hardware Hash. You only need to upload the device serial no. (Only Works with newer hardware 2018 January and up).
PS. If you followed the session sorry for repeating 🙂
Yes, I’m familiar with that information. At this moment the Intune experience is still preview.
This is the most valuable page for modern Windows 10 deployment. You’re great. Do you by any chance have any ideas on how to rename a machine through Intune? I’ve been back and forth with Microsoft on this and the obvious PowerShell method will not work because it seems Intune cannot handle any PS Script that requires a restart. Any ideas would be extremely helpful.
Thank you, Steve!
At this moment there are not that many options. Either script something fancy, or package something fancy. However, in both cases you need to find something custom to handle reboot behavior. It won’t be pretty for the status in the console of the used policy.
is there a way to delete an entry?
Yes! However, at this moment that needs to be done by using the Microsoft Store for Business.
As you noticed they fixed the Intune CSV format so you can upload the CSV file created by Get-WindowsAutoPilotInfo directly 🙂
Yes! Great improvement 🙂
Intune will now accept a standard CSV file (just like the Microsoft Store for Business) when uploading devices for Windows AutoPilot
Thanks RKast! That’s exactly what I’m doing in this post 🙂
Great blog! The -partner switch for Get-WindowsAutoPilotInfo wasn’t introduced untill v1.3, so you might want to update the link to the PowerShell script. (currently linking to v1.2)
Thank you, Wesley. That was indeed still the old link. I’ve just updated it.
Hi Rkast – short question concerning the “serial” method. We tried this already various times and it does not work for us (even with involvement of MS support). Did you test that yourself?
No i have not tested this yet. I just learned this at the tech summit. Do you use the Partner Portal as this is only possible in that Portal? And is the hardware newer than Jan/Feb 2018?
How to create a dynamic group for machines enrolled thru AutoPilot?
Not at this moment, but I wouldn’t be surprised if that’s coming soon.
Excellent write up, works perfectly. Thanks
so i dont need to edit the CSV file right? just upload it?!
Is the Windows Product ID no longer needed? Do we know the reason why the scrip no longer get that information?
That’s indeed not required anymore in many scenarios.