There is a new Intune release – in the Week of October 16, 2017 – there was announced Windows AutoPilot Integration – there is a preview label on the feature so this means that it is not final and are subject to change.
How does it looks like:
Inside the Intune admin portal go to Device enrollment – Windows Enrollment
Click Create Profile
Create profile
- Enter a Name – Windows AutoPilot Default Profile
- Join Type – Azure AD joined – this is the only join type at the moment, but with the new announcement at Ignite where it is possible to AzureAD and AD join the same device this will be subject to change
- Click to change the OOBE settings
Change the setting for the OOBE experience:
- Privacy Settings – change to Hide
- EULA – change to hide – this will only work on Windows 10 1709 as Microsoft have change the order in the OOBE to show EULA after Windows has connected to Windows AutoPilot
- User account type – change to Standard if you want the End-User to be a Standard – this is at the moment the only way to do it on a AzureAD joined device.
Then you can see the newly created Windows AutoPilot profile.
Note: Windows AutoPilot profiles created in MSfB or CSP portal are not showed in Intune – But the profile created in Intune is shown in MSfB
The Profile are also in Microsoft Store for Business
In the device section of Windows Autopilot Deployment Program – you can import devices.
Click sync – and you will get you devices from the Windows AutoPilot service in MSfB
The sync will require that you click Refresh
Note: You still need to import your devices into MSfB and the sync to Intune
After a refresh your devices from MSfB are now showed in Intune
Then you can select one or more devices and assign the profile you created in Intune.
Read more of my blogpost on Windows AutoPilot here:
How to use Windows Autopilot from Microsoft Windows Store for Business(WSfB)
How to use Windows Autopilot from Microsoft Partner Center (CSP)
Hi,
When I am creating a new autopilot profile and when I am about to save I get an error occurred.
“An error occurred while creating Autopilot profile “Windows AutoPilot Default Profile”. Request ID: ”
and
“An error occurred while fetching Autopilot profile. Request ID: ”
Any ideas?
Regards Johan
Reblogged this on automatizeblog.
If an Intune Deployment Profile is configured, is it necessary to configure and assign a MSfB’ AutoPilot deployment profile to the same device(s)? In what scenario would both need to be configured or one or the other?
I only assign a profile in Intune. But when I started deploying autopilot MSfB was the only option. When creating a autopilot profile and assigment in Intune it will sync back to MSfB. I need to test what is happing when assigning a profile in MSfB but as I remember it synced to Intune.
ah, ok. I just created a new Intune Deployment profile in my tenant, did a sync to MSfB and it did show up in MSfB as a new profile to choose from. It looks like it’s a one way sync though because I had an AutoPilot Deployment profile created and assigned in MSfB but it didn’t show up in Intune under Deployment Profiles. Thanks for clearing that up!
i just saw your note above about the profiles created in MSfB and CSP not being shown in Intune. Sorry about that!
Reblogged this on SCCM Geeks.