Windows Autopilot rollout checklist: user-driven Microsoft Entra join

Last reviewed: November 21, 2026 · 13 min read

Windows Autopilot is how you turn a new, factory-installed Windows PC into a business-ready, Microsoft Entra joined, Intune-managed device without imaging it first. The user-driven Microsoft Entra join path is the usual starting point for organization-owned laptops: the user powers the device on, connects to a network, signs in with their work account, and waits while apps and policies apply.

When this path is the right one

Microsoft's Windows device enrollment guide is clear that Windows Autopilot is for organization-owned devices, not personal or BYOD devices. For BYOD, use a different Windows enrollment option.

User-driven Microsoft Entra join is the simplest Autopilot scenario: the device joins Microsoft Entra ID (not on-premises Active Directory), enrolls in Intune, and is associated with a user. Choose a different Autopilot mode if you need:

This checklist follows Microsoft's official user-driven Microsoft Entra join tutorial. Confirm each step against the current Learn article before you run it in production.

Prerequisites to confirm first

Software

The device must run a currently supported version of Windows 10 or Windows 11 in a supported edition (Pro, Pro Education, Pro for Workstations, Enterprise, Education, or Enterprise LTSC; IoT Enterprise only for Microsoft Teams Rooms). See the Windows Autopilot requirements article. Autopilot does not support Windows versions that are past their support lifecycle, and Home edition is not on the supported list.

Licensing

The same requirements article lists the licensing combinations that include the needed capabilities. The minimum pairing is Microsoft Entra ID P1 or P2 plus a Microsoft Intune subscription (or another MDM service). Those capabilities are also included in Microsoft 365 Enterprise E3 or E5, and in Enterprise Mobility + Security E3 or E5. Automatic MDM enrollment, which Autopilot depends on, is an Entra ID P1/P2 feature.

Assign the Intune license (and the Microsoft 365 license the user needs) to every user who will enroll a device. A subscription sitting unassigned on the tenant is not enough.

Networking

The device needs internet access during the out-of-box experience (OOBE), including DNS resolution and outbound access to the Autopilot, Microsoft Entra, Intune, Windows Update and related endpoints documented in the requirements article. If users will unbox at home, test on a typical home network, not only on the corporate LAN. Captive portals and proxies that require authentication before the device is enrolled are a common cause of first-day failures.

The official eight-step workflow

Microsoft's tutorial lists these steps. In a lab you may do them in this order; in production, creating the device group before you import a large hardware-hash list often scales better.

  1. Set up Windows automatic Intune enrollment. In Microsoft Entra ID, configure Mobility (MDM) for Microsoft Intune and set the MDM user scope to the users (or groups) who should enroll automatically. Details: Set up Windows automatic Intune enrollment.
  2. Allow users to join devices to Microsoft Entra ID. In Entra device settings, confirm that the users in scope are allowed to join devices, and that any device-join limit will not block the rollout.
  3. Register devices as Windows Autopilot devices. Each device's hardware hash must be uploaded and associated with your tenant. Ideally the OEM, reseller or distributor registers the device before it ships. For existing or pilot devices, use manual registration. See also the registration overview.
  4. Create a device group. Use a dynamic device group based on the Autopilot device attribute, or assigned groups per rollout wave, so profiles and apps target the right devices.
  5. Configure and assign the Enrollment Status Page (ESP). ESP can keep the user on a progress screen until required apps and policies install. Configure it carefully: an app that never finishes will leave the user stuck. See Windows Autopilot Enrollment Status Page.
  6. Create and assign a Windows Autopilot profile. For this scenario, choose user-driven deployment and Microsoft Entra ID join. Set OOBE options such as hiding privacy settings, skipping the EULA if your licensing allows it, and whether the user is a standard user or a local administrator. Assign the profile to the device group. See Configure Windows Autopilot profiles.
  7. Optionally assign a user to the device in the Autopilot devices list if you want the pre-assigned user's name to appear during OOBE.
  8. Deploy the device. Factory-reset or new devices should reach OOBE, receive the Autopilot profile (this can take a short time after registration), join Entra ID, enroll in Intune, and complete ESP before the desktop appears.

Policies and apps to have ready, but not company-wide yet

Autopilot enrollment is only useful if the device then receives a sensible baseline: a compliance policy, BitLocker with key escrow, Windows Hello for Business, update rings, required apps, and (later) a Conditional Access policy that requires a compliant device. Assign those to the pilot group first, not to "All devices" or "All users."

Do not switch a "require compliant device" Conditional Access policy from report-only to on until Autopilot devices actually reach compliant, and until emergency access accounts are excluded. Our Conditional Access starter guide covers that sequence.

How this fits a wave-based rollout

Autopilot is the enrollment method. It does not replace a rollout plan. Pilot with IT and a few volunteers covering every hardware model you support, then expand in waves sized to what the help desk can absorb. Between waves, watch enrollment failures, ESP timeouts, app-install errors and compliance. The method is in our guide on planning an Intune device rollout in waves.

Want the dates calculated for you? Try the free rollout wave calculator, or get the Device Rollout Planner workbook with a readiness checklist, wave schedule, device tracker and dashboard.

Test the full OOBE path on a spare device of each model before the first user unboxes one. A profile that looks correct in the admin center can still fail on a specific NIC, firmware, or home Wi-Fi setup.
Windows editions, required endpoints and licensing combinations change. Confirm them against the current Windows Autopilot requirements article before you buy hardware or promise a go-live date.

Sources (Microsoft Learn, reviewed November 2026): Overview of Windows Autopilot; Windows Autopilot requirements; User-driven Microsoft Entra join tutorial; Registration overview; Manual registration; Enrollment Status Page; Configure Windows Autopilot profiles; Windows device enrollment guide. Always follow the current version of those articles.

This guide was drafted with AI assistance and checked against public Microsoft documentation. How we use AI. Spotted an error? Email [email protected].