Windows AutoPilot

This document is provided “as-is”. Information and views expressed in this document, including URL and
other Internet Web site references, may change without notice. You bear the risk of using it.
This document does not provide you with any legal rights to any intellectual property in any Microsoft
product. You may copy and use this document for your internal, reference purposes.

Version 1.1 (Updated January 19, 2018)

© 2017 Microsoft. All rights reserved.

Table of Contents
Windows AutoPilot......................................................................................................................................... 4
Prerequisites.................................................................................................................................................. 4
Demo environment setup........................................................................................................................... 4
Demo Device Setup.................................................................................................................................... 5
Hyper-V Virtual Machine Setup................................................................................................. 5
Physical Device Setup............................................................................................................... 6
Demo Device AutoPilot Configuration....................................................................................... 6
User Accounts............................................................................................................................................. 7
AutoPilot Demo.............................................................................................................................................. 8
Initial first-run experience......................................................................................................... 8
Authenticate the user............................................................................................................... 8
Device is ready to use.............................................................................................................. 8
Notes............................................................................................................................................................. 9
 Windows AutoPilot
Windows AutoPilot is a collection of technologies used to set up and configure new devices, getting them
ready for productive use. This solution enables an IT department to achieve the above with little to no
infrastructure to manage, with a process that's easy and simple.
Traditionally, IT pros spend a lot of time on building and customizing images that will later be deployed to
devices with a perfectly good OS already installed on them. Windows AutoPilot introduces a new approach.
From the users' perspective, it only takes a few simple operations to make their device ready to use.
From the IT pros' perspective, the only interaction required from the end user, is to connect to a network
and to verify their credentials. Everything past that is automated.
Windows AutoPilot allows you to:
 Automatically join devices to Azure Active Directory (Azure AD)
 Auto-enroll devices into MDM services, such as Microsoft Intune (Requires an Azure AD Premium
subscription)
 Restrict the Administrator account creation
 Create and auto-assign devices to configuration groups based on a device's profile
 Customize OOBE content specific to the organization
 Enable the complete configuration of the device using Microsoft Intune
Most importantly, Windows AutoPilot helps pull together the Microsoft 365 powered device vision,
leveraging modern deployment and management techniques with Windows 10, Office 365 ProPlus, and
EMS.

Prerequisites
Demo environment setup

For this demo, you will need to create a “Microsoft 365 Enterprise Demo Content” quick tenant from
[Link] (No optional features need to be enabled.) Once the environment has been
created, the following one-time configuration steps need to be performed:
 Configure Azure Active Directory (if desired).
o Sign in to [Link] using the admin credentials provided for the tenant.
(Using an InPrivate browser session may be required.)
o Adjust the tenant name that will be displayed during OOBE by navigating to Azure Active
Directory -> Properties and set the Name field as needed, then click Save.
o Add your own custom branding by navigating to Azure Active Directory -> Company
branding. Click Edit and make the changes required.
 Set up the Microsoft Store for Business.
o Sign into [Link] using the admin credentials provided for the
tenant. (Using an InPrivate browser session may be required.)
o Accept the terms for the Microsoft Store for Business.
 Configure Microsoft Intune
o Sign in to [Link] using the admin credentials provided for the tenant.
(Using an InPrivate browser session may be required.)
o Navigate to the Intune management page via More Services -> Monitoring &
Management -> Intune.
o Create a Windows AutoPilot deployment profile.
 Navigate to Intune -> Device enrollment -> Windows enrollment, and then
click Deployment Profiles. If prompted to add an MDM Management Authority, click
Intune MDM Authority and then click Choose.
 Click + Create Profile and specify a profile name. For Join type, specify Azure AD
joined (the only option at this point). Click on Defaults configured and configure
 the settings as desired. At minimum, hiding the Privacy Settings and EULA (only
supported with Windows 10 1709) is recommended. Click Save and then Create.
o Initiate a sync between Intune and Windows AutoPilot.
 Navigate to Intune -> Device Enrollment -> Windows Enrollment and then click
Devices. Click Sync to initiate a sync with Windows AutoPilot. (Note that no devices
are expected.)
o Create an Office 365 ProPlus app.
 Navigate to Intune -> Mobile Apps -> Apps and select Add. For the app type,
select Windows 10 (under Office 365 Suite).
 Click Select Office apps to be assigned and select all the desired apps, then click
OK.
 Click Configure the app suite information under App Suite Information and
specify a name and description, e.g. “Office 365 ProPlus,” then click OK.
 Click Configure the app suite information under App Suite Settings. Select
Semi-Annual under Update channel. Change any other settings as desired, then
click OK.
 Click Add to add the app.
 Click Assignments and then + Select Groups. Select the sg-Sales and
Marketing group from the list. (The user MeganB, used later, is a member of this
group.)
 Specify the type as Required and then click Save.
o Define any other desired Windows 10 settings via Microsoft Intune.

Demo Device Setup

To demonstrate the client-side experience of Windows AutoPilot, a device is needed. This can be a virtual
machine or a physical machine. When possible, a physical machine demo is suggested. Windows 10 Pro,
Enterprise, or Education SKUs can be used. (Windows 10 S is not recommended for the purposes of this
demo, since Windows 10 S cannot run PowerShell scripts.)
Hyper-V Virtual Machine Setup
A virtual machine running in Hyper-V will work fine for demoing Windows AutoPilot, as long as the
minimum specifications can be achieved: the VM should have a minimum of 20GB of disk space available
and at least 4GB of RAM. Ensure Hyper-V is installed on Windows 10 1709 or later, and a network adapter
is available that has access to the internet.
To create a virtual machine, follow these steps:
 Download a Windows 10 Pro, Enterprise, or Education ISO from [Link]
(“Windows 10 (multi-edition), Version 1709” for retail or “Windows 10 (multi-edition) VL, Version
1709” for volume license) or another appropriate location.
 Launch Hyper-V Manager on the host machine.
 Choose “Quick Create…” from the Actions menu.
 Click “Local Installation Source,” then “Change installation source…” to browse and select the ISO
that you downloaded.
 Click “Create virtual machine.” When the process is complete, click “Connect” to start the Virtual
Machine Connection app.
 Click “Start” and then press any key when prompted to start the installation process.
 When Windows Setup starts, click “Next” and then “Install Now.” Optionally, specify an appropriate
product key if prompted. If you skip the product key, choose the SKU to install (e.g. “Windows 10
Pro”).
 Accept the license terms, then choose “Custom: Install Windows Only” and accept the default
installation location.
 When the virtual machine gets to the region selection screen, create a checkpoint from the Action
menu (useful to reset the VM back to this point to repeat the demo).
 Continue with the Demo Device AutoPilot Configuration section below.
Physical Device Setup
Any physical device can be used for Windows AutoPilot. If the existing machine has a functional operating
system on it, it can be prepared for demo use by resetting the device by following these steps:
 Sign in with an account that has admin rights.
 Open the Settings app and navigate to Update & Security -> Recovery. Under “Reset this PC”
click “Get started” and choose “Remove everything.”
 Once the reset process completes and the language selection screen is presented, continue with
the Demo Device AutoPilot Configuration section below.
For Surface devices such as Surface Book or Surface Pro, reapplying the available recovery image is also
an option. These recovery images can be downloaded via
[Link] After restoring the image using the provided
instructions, the device will boot to the language selection screen. At that point, continue with the Demo
Device AutoPilot Configuration section below.
If the recovery image or existing OS is not running at least Windows 10 1709, upgrade the OS to Windows
10 1709 via Windows Update, and then reset the OS.
Demo Device AutoPilot Configuration
Before the device can be deployed using Windows AutoPilot, you must gather the hardware information
from the device. For devices that have wired network connections, or when using a USB key, the following
steps can be used:
 Boot the devices into Windows 10 1709.
 On the first OOBE screen, press Shift-F10 to open a command prompt.
 Run [Link]. Run command Set-ExecutionPolicy Bypass to enable scripts. Then run
command Install-Script Get-WindowsAutoPilotInfo and answer Y to any prompts.
 Execute command Get-WindowsAutoPilotInfo.ps1 -OutputFile [Link] and copy the CSV
file to a USB key, or map a drive to a network location and copy the file to that location.
 Exit from [Link] and the command prompt to remain at the OOBE language selection
screen (ready for the demo).
If this device only has Wi-fi networking and no USB key is available, the steps will need to be modified:
 Boot the devices into Windows 10 1709.
 On the first OOBE screen, press Control-Shift-F3 to reboot the device into audit mode.
 Once the desktop appears, connect to a Wi-fi network.
 Open an elevated command prompt.
 Run [Link]. Run command Set-ExecutionPolicy Bypass to enable scripts. Then run
command Install-Script Get-WindowsAutoPilotInfo and answer Y to any prompts.
 Execute command Get-WindowsAutoPilotInfo.ps1 -OutputFile [Link] then map a drive to
a network location and copy the file to that location.
 Click OK in the Sysprep dialog to reseal the OS and reboot the computer (ready for the demo).
Note that the above instructions do not work for devices running Windows 10 S since Windows 10 S will
not run PowerShell scripts. In this case, you can remotely gather the hardware information, then reset the
computer to get back to the start of the process.
Once you have a CSV file with the device details, perform these steps to define the device to Windows
AutoPilot:
 Sign into [Link] using the admin credentials provided for the tenant.
(Using an InPrivate browser session may be required.)
 Click on Manage and then Devices. Click + Add Devices and browse to the previously-created
CSV file to select it. Click No thanks to specify not to add the device to a group.
 Click Refresh at the top of the page if necessary, until the newly-uploaded CSV is processed.
 Select the newly-uploaded device by checking the box in front of it.
 Under AutoPilot deployment, select the Apply <profile name> option to apply the previously-
created profile.
Note that Microsoft Intune will soon allow importing of devices, management of profiles, and assignment of
profiles to devices. Until then, the Microsoft Store for Business should be used for those tasks.

User Accounts

For this demo, the following tenant user will be used to complete the AutoPilot deployment process:
 Username: MeganB@<tenant>.[Link]
 Password: Obtain the tenant password from your demo card on [Link].
Megan is a member of the Marketing Department.
AutoPilot Demo
The following steps and talking points can be used to complete the end-user demo for Windows AutoPilot.

Talking Points Demo Flow

Initial first-run experience.

1. On the Windows 10 device or VM, click to
Before Windows AutoPilot can set up the machine, choose the language and keyboard layout.
the device needs to be connected to a network. To 2. Skip the additional keyboard layout.
get to that point, you need to choose a language 3. Accept the EULA (if running Windows 10
and keyboard layout (since that information may 1703)
be needed to make the connection). 4. If needed, connected to a wireless network.
If you were connecting to a public wi-fi hotspot,
you might also need to sign into a captive portal, a
web page that requires accepting terms or signing
into an ISP’s service. This is fully supported by
Windows AutoPilot.
1. Windows will check for updates and may
Authenticate the user. apply an update.
Now we can validate the user’s credentials. Notice 2. A customized sign-in screen will be
that the sign-in screen is customized for the presented with company branding.
organization, displaying the organization’s logo 3. Type in Megan’s e-mail address,
and short name (e.g. “Contoso Demo”) so that MeganB@<tenant>.[Link] and
users are guided through the process. then click Next
4. Type in Megan’s password (the demo
At this point, the device is joined to Azure Active environment password) and then click
Directory and enrolled in Microsoft Intune. The Next.
user is then signed in for the first time, showing
the standard first logon experience while one-time
setup steps are performed.
At this point, Intune begins pushing settings and
apps down to the device.
1. In the Settings app, navigate to Accounts ->
Device is ready to use. Access work or school.
Once the first logon tasks are completed, it may 2. Show that the device is joined to Azure AD,
take a while longer for the configuration of the then click Info to see the settings applied by
device to complete. Intune via MDM.
Note that Windows 10 1709, with some additional
support being added in Intune, will soon be able to
display a progress dialog while the device
configuration is progressing, to let the user know
that the process is not done yet.
Notes
Once the demo has completed, the device can be reset in order to repeat the demo. There is no need to
repeat the hardware information gathering steps above as the hardware details will not change.
Note that there is a limit to the number of devices that can be enrolled in Intune for a single user. The
default is five devices, although this can be increased to 15 devices. The demo will fail if you try to enroll
more than the configured number of devices for a particular user. To avoid this, older devices can be
manually removed from Intune.