Imaging every new laptop and joining it to the domain means the IT team spends its week preparing devices. Windows Autopilot reverses this: the device goes to the user straight out of the box and pulls the corporate configuration from the internet on first boot. The IT team doesn’t touch the device; it joins Entra ID, enrolls in Intune and installs its own policies and apps. Below we go through device registration, profile choice, the join type decision, Enrollment Status Page settings and the troubleshooting steps where people often get stuck.
What Autopilot changes: provisioning instead of imaging
In the classic method, the IT team prepares a reference image, reloads the device with WDS, MDT or USB, joins it to the domain and hands it to the user. The cost of this model is keeping the image current, managing driver packs and physically touching every device. An image that hasn’t been updated for six months downloads updates for hours after setup.
Autopilot uses the Windows installation the manufacturer put on the device. During OOBE (the out-of-box experience), the device queries the Autopilot service, receives the organization’s deployment profile if it is registered and continues setup through Intune. The configuration now lives in policy, not in an image. Prerequisites:
- A license for users that includes Entra ID P1 and Intune (for example Business Premium or Microsoft 365 E3); for choosing one, see our article on choosing a Microsoft 365 license.
- Automatic MDM enrollment (MDM user scope) for Windows enabled in Intune.
- Users allowed to join devices in Entra ID, with a per-user device limit that fits your needs.
- Internet access from devices to Microsoft’s Autopilot and Intune endpoints during OOBE; an authenticating proxy causes problems at this stage.
- Windows Pro, Enterprise or Education edition; Home edition is not supported.
Registering devices with Autopilot: manufacturer, reseller and hash methods
For a device to receive an Autopilot profile, its hardware ID must be registered in the organization’s tenant. There are three ways:
| Method | How it works | When it fits |
|---|---|---|
| Manufacturer (OEM) | The manufacturer registers the device in the tenant at order time | Bulk purchases directly from the manufacturer |
| Reseller / CSP | An authorized partner registers it through Partner Center | Purchases through a reseller |
| Hardware hash | The hash is collected from the device and uploaded to Intune as a CSV | Existing devices, pilots, small purchases |
To collect the hash from an existing device, open an administrator PowerShell session in Windows. You can do the same on the OOBE screen by opening a command prompt with Shift+F10 and typing powershell:
New-Item -Type Directory -Path C:\HWID -Force
Set-Location C:\HWID
$env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned -Force
Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo -OutputFile C:\HWID\AutopilotHWID.csv
# Alternative: upload directly to Intune and assign a group tag
Get-WindowsAutopilotInfo -Online -GroupTag "HQ-OFFICE"
The CSV file is imported in the Intune admin center under Devices > Windows > Enrollment > Windows Autopilot > Devices. The group tag is the cleanest way to route devices to different profiles. Profiles are assigned with dynamic device groups:
# All Autopilot devices
(device.devicePhysicalIDs -any (_ -startsWith "[ZTDid]"))
# Only devices with a specific group tag
(device.devicePhysicalIds -any (_ -eq "[OrderID]:HQ-OFFICE"))
Calculating dynamic group membership and assigning the profile to the device takes time. Don’t send a device into OOBE until its profile status in Intune is “Assigned.” A rushed device falls into the standard Windows setup instead of the corporate screen.
Deployment profile types and how to choose
- User-driven: The user turns on the device, connects to the network and signs in with their corporate account; setup continues under that identity. This is the default mode for laptops assigned to a person.
- Self-deploying: The device enrolls itself with no user interaction. Suitable for kiosks, meeting room displays and shared devices. It requires TPM 2.0 hardware attestation and works only with Entra join.
- Pre-provisioning: The IT team or reseller starts the technician flow by pressing the Windows key five times at OOBE; device policies and most apps are installed before the device goes to the user. When the user signs in, only the user-specific part remains. It requires TPM 2.0 hardware attestation and doesn’t work on virtual machines. Use a wired network in the technician flow; it rules out Wi-Fi profile problems from the start.
Microsoft also offers the Autopilot device preparation model, which doesn’t require registration and reports setup progress in more detail. This model supports only Entra join scenarios and lacks some features of the classic profiles; check the current feature scope in Microsoft’s Windows Autopilot documentation.
Entra join or hybrid join?
With hybrid Entra join, the device joins both on-premises AD and Entra ID. For this scenario with Autopilot, Intune Connector for Active Directory must be installed on an on-premises server, a Domain Join configuration profile created in Intune and the device must be able to reach a domain controller during OOBE. The device object reaching Entra ID also depends on device sync with Entra Connect Sync; this feature isn’t in Cloud Sync (see our Entra Connect Sync versus Cloud Sync comparison). The number of moving parts grows. So does the number of failure points.
| Criterion | Entra join | Hybrid Entra join |
|---|---|---|
| On-premises DC access | Not needed for setup | Needed during OOBE |
| Additional component | None | Intune Connector for AD |
| Setup for remote users | Internet is enough | Requires a pre-logon VPN |
| GPO application | None; Intune policies | Yes |
| SSO to on-premises resources | Possible with Kerberos | Native |
Entra-joined devices can access on-premises file shares and Kerberos-based applications with single sign-on as long as the user is synced with hybrid identity. Unless there is a concrete blocker such as a GPO dependency, legacy applications that work by device name or authorization based on the computer account, prefer Entra join for new devices. “We’ve always done it this way” is not a concrete blocker.
The Enrollment Status Page and app order
The Enrollment Status Page (ESP) is the progress screen that stops the user reaching the desktop until setup is complete. If it is set up wrongly, either the user signs in to a half-configured device or setup times out.
- Show app and profile configuration progress: Yes.
- Timeout: 60 minutes by default; set it based on network speed and the number of required apps.
- Block device use until setup completes: Block only for selected required apps (VPN client, security agent, Office), not for all apps.
- Allow reset on error: No during the pilot; the device should stay on the error screen so logs can be collected.
Win32 packaging, detection rules and dependency definitions are explained in detail in our article on Win32 app deployment with Intune. If the detection rule of an app the ESP is waiting for is wrong, the ESP times out even if the installation succeeded. In the field, a large share of ESP problems are really packaging problems.
Troubleshooting enrollment errors
The first job is to find out at which stage the error happens. If the profile never arrived, it’s registration and assignment; if Entra join fails, it’s identity and enrollment restrictions; if it’s waiting at the ESP, it’s a policy or app problem. Reading logs without knowing the stage wastes time.
Collect the diagnostics package on the device with this command (it also works from the command prompt opened with Shift+F10 during OOBE):
MDMDiagnosticsTool.exe -area "DeviceEnrollment;DeviceProvisioning;Autopilot" -zip C:\Temp\autopilot-diag.zip
The main sources to look at in the package and in Event Viewer:
Microsoft-Windows-ModernDeployment-Diagnostics-Provider/Autopilot: Profile download and Autopilot stages.Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin: MDM enrollment and policy application errors.C:\ProgramData\Microsoft\IntuneManagementExtension\Logs: Win32 apps and scripts.
Common situations and what to check:
- The device doesn’t show the corporate screen: It may not be registered, the profile may not be assigned, or the device may have started OOBE before the profile was assigned. Check the profile status in Intune and reset the device.
- Enrollment restriction error: Devices registered with Autopilot count as corporate, so a personal device block doesn’t stop them. The usual reasons for a rejection are a Windows (MDM) platform restriction, the per-user device limit (Intune enrollment limit or Entra ID device limit) being reached and stale objects left over from the device’s previous enrollment. Check restriction policies and limits, and clean up old Intune and Entra ID device objects.
- Stuck at hybrid join: Check the status of Intune Connector, the OU where the connector account has rights to create device objects, and the device’s access to a DC.
- Authenticating proxy: Components running in device context during OOBE can’t enter proxy credentials; define exceptions for the required endpoints.
Pilot and rollout checklist
- Licenses, automatic MDM enrollment and Entra ID device join settings verified.
- Group tags and dynamic device groups defined; profile assignment shows “Assigned.”
- Device naming template defined (for example
ERT-%SERIAL%; mind the 15-character limit for computer names). - The blocking app list in the ESP kept short; all apps tested as Win32.
- User-driven and, if needed, pre-provisioning flows tried with at least two different hardware models.
- Verified that the device receives the profile again after a reset (Autopilot Reset or Wipe).
- A short setup guide prepared for users: network connection, sign-in, MFA registration.
- A step to delete the Autopilot registration of retired devices added to the inventory process.
For Autopilot pilot and rollout stages and periodic tracking of the device lifecycle, see the scope on our technical support and scheduled maintenance and Microsoft 365 services pages. If compliance conditions and corporate access settings are to be designed along with device deployment, address them together as part of Microsoft 365 security consulting.
Frequently asked questions
Do you always have to collect the device’s hardware hash for Autopilot?
With classic Autopilot deployment profiles, the device must be registered with the Autopilot service; registration can be done by the manufacturer, reseller or CSP, or manually by collecting the hardware hash. Microsoft’s newer Autopilot device preparation model doesn’t require registration, but the scenarios it supports are more limited.
Does an Autopilot device get the same profile after a reset?
Yes. As long as the device stays registered with the Autopilot service, it receives the same deployment profile during OOBE after a reset or a fresh Windows installation. That is why the Autopilot registration of devices that are sold, returned or transferred to another organization should be deleted.
Does hybrid Entra join with Autopilot work over VPN?
With a hybrid join profile, the device must be able to reach a domain controller during initial setup. For remote users, the profile needs the option to skip the AD connectivity check and a VPN client that connects before sign-in. Because of this complexity, Microsoft recommends Entra join for new devices.
What should be done if the Enrollment Status Page times out?
First determine at which stage the ESP is waiting (device preparation, device setup or account setup). Then collect a log package with MDMDiagnosticsTool and check the Intune Management Extension logs to see which app it is waiting for. Rather than extending the timeout, shortening the list of apps required by the ESP is usually the lasting fix.