With Windows Autopilot, the goal is to simplify deployment of new Windows 10 devices by eliminating the cost and complexity associated with creating, maintaining, and loading custom images. Windows Autopilot will revolutionize how new devices get deployed in your organization—
Self-Deploying mode—Currently, the Windows Autopilot experience requires the user to select basic settings like Region, Language, and Keyboard, and also enter their credentials, in the Windows 10 out-of-the-box experience. With a new Windows Autopilot capability called “Self-Deploying mode,” we’re extending the zero-touch experience from IT to the user deploying the device. Power on* is all it takes to deploy a new Windows 10 device into a fully business-ready state—managed, secured, and ready for usage—no need for any user interaction. You can configure the device to self-deploy into a locked down kiosk, a digital signage, or a shared productivity device—all it takes is power on.*
Windows Autopilot reset—This feature extends the zero-touch experience from deployment of new Windows 10 devices to reset scenarios where a device is being repurposed for a new user. We’re making it possible to completely reset and redeploy an Intune-managed Windows 10 device into a fully business-ready state without having to physically access the device. All you need to do is click a button in Intune!
Video: Windows Autopilot updates
The Cloud-Driven scenario enables you to pre-register devices through the Windows Autopilot Deployment Program. Your devices will be fully configured with no additional intervention required on the users’ side.
The Windows Autopilot Deployment Program experience
The Windows Autopilot Deployment Program enables 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
Devices must be registered to the organization
Company branding needs to be configured
Network connectivity to cloud services used by Windows Autopilot
Devices have to be pre-installed with Windows 10 Professional, Enterprise or Education, of version 1703 or later
Devices must have access to the internet
Azure AD Premium P1 or P2
Users must be allowed to join devices into Azure AD
Microsoft Intune or other MDM services to manage your devices
The end-user unboxes and turns on a new device. What follows are a few simple configuration steps:
Select a language and keyboard layout
Connect to the network
Provide email address (the email address of the user’s Azure AD account) and password
Multiple additional settings are skipped here, since the device automatically recognizes that it belongs to an organization. Following this process the device is joined to Azure AD, enrolled in Microsoft Intune (or any other MDM service).
MDM enrollment ensures policies are applied, apps are installed and setting are configured on the device. Windows Update for Business applies the latest updates to ensure the device is up to date.
I hope it’s of interest.