Windows Autopilot self-deploying mode
Note
For more information about using Windows Autopilot to deploy HoloLens 2 devices, see Windows Autopilot for HoloLens 2.
Tip
For a guided walkthrough of Windows Autopilot self-deploying mode, see Step by step tutorial for Windows Autopilot self-deploying mode in Intune.
Windows Autopilot self-deploying mode allows deployment of a device with little to no user interaction. For devices with an Ethernet connection, no user interaction is required. For devices connected via Wi-Fi, the user must only:
- Select the language, locale, and keyboard.
- Make a network connection.
Self-deploying mode provides all the following features:
- Joins the device to Microsoft Entra ID.
- Enrolls the device in Intune or another mobile device management (MDM) service using Microsoft Entra ID for automatic MDM enrollment.
- Makes sure that all policies, applications, certificates, and networking profiles are provisioned on the device.
- Uses the Enrollment Status Page to prevent access until the device is fully provisioned.
Note
Autopilot self-deploying mode is only supported for Microsoft Entra join devices. Autopilot self-deploying mode isn't supported for Microsoft Entra hybrid join devices.
Self-deploying mode allows deployment of a Windows device as a kiosk, digital signage device, or a shared device.
Autopilot now has a kiosk mode that supports Kiosk Browser, Microsoft Store apps, and specific versions of Microsoft Edge.
The Kiosk Browser can be used when setting up a kiosk device. This app is built on Microsoft Edge and can be used to create a tailored, MDM-managed browsing experience.
The device configuration can be automated by combining self-deploying mode with MDM policies. Use the MDM policies to create a local account configured to automatically sign in. For more information, see:
- Simplifying kiosk management for IT with Windows 10.
- Set up a kiosk or digital sign in Intune or other MDM service.
Optionally, a device-only subscription service can be used that helps manage devices that aren't affiliated with specific users. The Intune device SKU is licensed per device per month.
Note
Intune doesn't automatically configure a primary user when using self-deploying mode in Autopilot to provision a Windows device. Some Intune capabilities rely on a primary user being set on a device. These features include user self-service BitLocker recovery key retrieval and using the Company Portal to install software. Using self-provisioning mode for Autopilot doesn't preclude a licensed user from logging into the device and using features entitled to that user such as Conditional Access. For more information, see Windows Autopilot scenarios and capabilities.
If desired, a primary user can be manually set after device provisioning via the Intune admin center. For more information, see Change a devices primary user.
Requirements
Important
A device can't automatically re-enroll through Windows Autopilot after an initial deployment with self-deploying mode. Instead, delete the device record in the Microsoft Intune admin center. From the Microsoft Intune admin center, select Devices > All devices > select the devices to delete > Delete. For more information, see Updates to the Windows Autopilot sign-in and deployment experience.
Self-deploying mode uses a device's Trusted Platform Module (TPM) 2.0 hardware to authenticate the device into an organization's Microsoft Entra tenant. Therefore, devices without TPM 2.0 can't be used with this mode. Devices must also support TPM device attestation. All new Windows devices should meet these requirements. The TPM attestation process also requires access to a set of HTTPS URLs that are unique for each TPM provider. For more information, see the entry for Autopilot self-Deploying mode and Autopilot pre-provisioning in Networking requirements. For Windows Autopilot software requirements, see Windows Autopilot software requirements.
Important
If a self-deploying mode deployment is attempted on a device that doesn't have support for TPM 2.0 or on a virtual machine, the process fails when verifying the device with an 0x800705B4 timeout error. This limitation includes Hyper-V virtual TPMs.
See Windows Autopilot known issues and Troubleshooting Windows Autopilot device import and enrollment to review other known errors and solutions.
An organization-specific logo and organization name can be displayed during the Autopilot process. To do so, Microsoft Entra Company Branding must be configured with the images and text that need to be displayed. See Quickstart: Add company branding to your sign-in page in Microsoft Entra ID for more details.
Step by step
To deploy in self-deploying mode Windows Autopilot, the following preparation steps need to be completed:
Create an Autopilot profile for self-deploying mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. It isn't possible to create a profile in the Microsoft Store for Business or Partner Center for self-deploying mode.
If using Intune, create a device group in Microsoft Entra ID and assign the Autopilot profile to that group. Ensure that the profile is assigned to the device before attempting to deploy that device.
Boot the device, connecting it to Wi-Fi if necessary, then wait for the provisioning process to complete.
Validation
When using Windows Autopilot to deploy in self-deploying mode, the following end-user experience should be observed:
Once the device connects to a network, the Autopilot profile is downloaded.
If connected to Ethernet, and the Autopilot profile is configured to skip them, the following pages aren't displayed:
- Language and locale.
- Keyboard layout.
Otherwise, manual steps are required:
- If multiple languages are preinstalled in Windows, the user must pick a language.
- The user must pick a locale and a keyboard layout, and optionally a second keyboard layout.
If connected via Ethernet, no network prompt is expected. If no Ethernet connection is available and Wi-Fi is built in, the user needs to connect to a wireless network.
Windows checks for critical out-of-box experience (OOBE) updates, and if any are available they're automatically installed, rebooting if necessary.
The device joins Microsoft Entra ID.
The device enrolls in Intune or other configured MDM services after it joins Microsoft Entra ID.
The enrollment status page is displayed.
Depending on the device settings deployed, the device will either:
- Remain at the sign-on screen, where any member of the organization can sign in by specifying their Microsoft Entra credentials.
- Automatically sign in as a local account, for devices configured as a kiosk or digital signage.
Note
Deploying Exchange ActiveSync (EAS) policies using self-deploying mode for kiosk deployments causes autologon functionality to fail.
In case the observed results don't match these expectations, consult the Troubleshooting Windows Autopilot overview documentation.