Windows 10 AutoPilot is a recently released collection of technologies from Microsoft that provides a simple process to setup and configure new devices, requiring minimal to no infrastructure. The premise is that this greatly reduces the required effort from IT admins usually spent on building and customising images. And from the user’s perspective, it only takes a few simple operations to make their device ready to use. This feature allows IT admins to:
To be clear, some of the above concepts aren’t new, for example auto-join devices to Azure or auto-enrol devices in Intune, however, the above points are a ‘collection’ of technologies which together provide a new method/experience for provisioning devices.
For more information, start at Overview of Windows AutoPilot.
For this blog post, we will go through the required steps to set up a simple deployment of Windows Autopilot and observe the user experience and behaviour (in a cloud-driven deployment scenario). Additionally, for this scenario, we will configure the Windows device to enrol in Intune, configure the device via an Intune configuration profile and automatically install Office Pro Plus.
As detailed on the overview of AutoPilot page mentioned earlier, the prerequisites for Autopilot are:
Expanding on the above, other prerequisites and my lab environment setup to facilitate this activity are:
Below are the steps I used to setup for this activity. There are alternate ways to do most of the following steps, but in the interest of brevity I will stick with what I did.
Upload the CSV file under the Devices tab.
Create an AutoPilot deployment profile.
Assign the AutoPilot deployment profile to the machine.
Intune must be set up as your MDM authority.
Ensure Windows device enrolment is enabled (it is by default).
In order for your devices to be auto-enrolled into MDM management in Intune, MDM auto-enrolment needs to be configured in Azure AD. To do that with Intune, please see Enrol Windows devices for Microsoft Intune.
Restrict MDM enrolment to specific users if you want to (I scoped to group shown below).
Check that DNS is correct for device enrolment.
I also configured Windows Hello as shown below.
You can set up a device configuration profile for Windows 10 in your Intune tenant as shown below. Remember to assign to a group containing your users.
You can create an Office Pro Plus deployment for Windows 10 as shown below. Remember to assign to a group containing your users.
With all the prerequisites set up, you can now power up your virtual machine to simulate the OOBE for the user. Below are the screen grabs from my lab, based on the above configuration.
In my lab, the VM connected to the Internet automatically. In real world scenario you may have to select a wireless network and enter passphrase for example.
It will also search for updates and apply them if any, as below screen grab indicates.
Note that instead of the default Microsoft Windows sign in screen, you will have your organisation’s customisations.
At this point enter the email address (identity) of a user in your tenant’s (Azure) AD.
Because I configured Windows Hello, I am prompted to set it up.
My lab user was configured for MFA, so I had to approve a second factor authentication request.
In the device settings, we can see that it is connected to Azure AD.
And in Intune in the Azure portal, we can see and manage the device.
My Intune Windows 10 device configuration policy simply added a desktop background image and default Edge browser home page to demonstrate that the policy is being applied.
And in between 10-15 minutes, Office 365 Pro Plus was installed.
Playing around with this in my lab, I noticed that I could log on to the device (from OOBE) with an account from another organisation, and with the exception of the AutoPilot configuration, provided the other tenant had all the prerequisites set up Intune and Azure AD, the device was joined to that tenant’s Intune and could be managed from there. The only difference was the AutoPilot features weren’t configured because the other tenant did not have this set up. So it appears that registering a device in Store for Business (at least) for a specific organisation doesn’t restrict enrolment for that device to that organisation only!
Microsoft says it is working to add additional options to further personalize and streamline the setup experience in future releases, and I think addressing the above behaviour should be high on the list. Also, for a higher level of control over the provisioning process, provisioning packages can be created with Windows Configuration Designer, see Create a provisioning package for Windows 10.
Overall the I think Autopilot is a pretty cool concept and am looking forward to future feature enhancements.