trio.so
Explained

Windows Autopilot: What It Is and How to Set It Up

What Windows Autopilot is, how it works, what it costs, how to set it up step by step, and how to use it with an MDM other than Intune.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

Windows Autopilot is Microsoft's cloud service for setting up new Windows PCs without IT touching them. A PC is registered to your organization when you buy it; when the employee unboxes it, connects to the internet and signs in with their work account, Windows joins Microsoft Entra ID, enrolls in your device management (MDM) service and installs your settings and apps. It uses the Windows already on the device, so there is no image to build or maintain.

If you want new laptops to ship straight to employees and set themselves up, this guide explains how Autopilot works, how it differs from the newer Autopilot device preparation, what it costs, how to set it up step by step and how to use it with an MDM other than Intune.

What Is Autopilot Used For?

Windows Autopilot is used to prepare company Windows devices for work, and to reset or repurpose them later. The main uses are:

  • New PCs for new hires. The reseller ships the laptop to the employee's home or desk, and it sets itself up at first sign-in.
  • Replacing old PCs. A refresh project becomes a shipping task rather than a day of imaging per batch.
  • Shared and kiosk devices. Self-deploying mode sets up a device with no user sign-in, for meeting rooms, kiosks and shared PCs.
  • Resetting devices. A PC that is reset goes back through Autopilot and returns to a managed, work-ready state.

Autopilot also works for HoloLens 2. For setting up devices across Apple, Windows and Android, see zero-touch deployment.

How Does Autopilot Work?

  1. Registration. Each PC's hardware identity (its hardware hash) is registered to your Microsoft Entra tenant. Resellers and manufacturers that take part in the programme can do this when you buy; you can also collect the hash from an existing PC and upload it.
  2. Profile. You assign an Autopilot deployment profile to the device. It sets how setup runs: the join type, which setup screens to skip, the device name and whether the user is a standard user.
  3. First start-up. The employee turns on the PC and connects to the internet. Windows contacts the Autopilot service, finds the registration and shows your company's sign-in page.
  4. Entra join and enrollment. The user signs in with their work account. The device joins Microsoft Entra ID, and automatic enrollment hands it to your MDM service.
  5. Configuration. The MDM service applies your policies and installs apps. The user reaches the desktop with a ready-to-use work PC.

Microsoft recommends joining new devices to Microsoft Entra ID only (cloud-native). Autopilot still supports Microsoft Entra hybrid join for devices that must join on-premises Active Directory, but that path needs the device on the internal network and isn't recommended for new deployments.

Autopilot Deployment Modes

ModeHow it worksBest for
User-drivenThe user signs in during setup, and the device is assigned to themLaptops for individual employees
Self-deployingThe device sets itself up with no user sign-in; needs TPM 2.0Kiosks, meeting rooms and shared PCs
Pre-provisioningIT or a partner runs the device part of setup in advance, so the user's part is shortPCs with many apps that take long to install

Windows Autopilot vs. Autopilot Device Preparation

Windows Autopilot device preparation is a newer, rebuilt version of the experience. Microsoft's documentation lists these requirements: Windows 11 version 24H2 or later, or versions 23H2 and 22H2 with the KB5035942 update or later, and Microsoft Entra join only.

The main differences from classic Autopilot:

  • No hardware hash registration is needed. The device is placed in a device group when the user signs in, and receives the apps, scripts and policies assigned to that group.
  • One profile holds the deployment and setup settings, and setup shows a percentage progress indicator.
  • Reporting shows near real-time status for each deployment, including which apps and scripts installed.
  • It is configured in Microsoft Intune, using Intune's enrollment time grouping.

Classic Autopilot remains supported and is still the option for self-deploying mode and for devices that need hybrid join. If a device is registered for classic Autopilot, Microsoft's rules decide which experience runs, so check the device's registration state before you switch.

Benefits and Drawbacks of Using Windows Autopilot

Benefits

  • No imaging. You use the Windows that came on the device instead of building and updating images.
  • Ship anywhere. Devices go straight from the reseller to the employee, wherever they work.
  • Managed from the first sign-in. The device is enrolled and protected before the user starts work.
  • Consistent setup. Every device in a group gets the same configuration.
  • Reset and reuse. A reset device returns to a managed state without IT handling it.

Drawbacks

  • It needs the internet during setup, and firewalls or captive Wi-Fi portals can stop it.
  • It needs Microsoft Entra ID and a supported licence, which small companies sometimes lack.
  • Devices must be registered, so buying from a participating reseller matters.
  • Troubleshooting a failed setup can be slow, because the problem may sit in the network, the licence, the profile or the MDM.

Is Windows Autopilot Free?

Autopilot has no separate price, but it isn't free on its own. Microsoft lists these requirements:

  • A supported edition of Windows 11 or Windows 10: Pro, Pro Education, Pro for Workstations, Enterprise or Education. Windows Home isn't supported.
  • Microsoft Entra ID P1 or P2 and an MDM service, either Microsoft Intune or an alternative MDM. These come with Microsoft 365 Business Premium, Microsoft 365 E3 or E5, Microsoft 365 F1 or F3, Microsoft 365 A1, A3 or A5, Enterprise Mobility + Security E3 or E5, or Intune for Education, or can be bought separately.

Windows 10 reached end of support on 14 October 2025, so new deployments should use Windows 11.

How Can Businesses Enroll Devices Using Windows Autopilot?

These are the steps for classic Windows Autopilot:

  1. Check the requirements: supported Windows editions, Microsoft Entra ID P1 or P2, and an MDM service.
  2. Turn on automatic MDM enrollment in Microsoft Entra ID so devices that join Entra are handed to your MDM. With Intune, this is set in Intune; with another MDM, follow its setup steps.
  3. Allow users to join devices to Microsoft Entra ID, or limit it to a group that includes your users.
  4. Register the devices. Ask your reseller to register new purchases to your tenant, or collect the hardware hash from existing PCs and upload it.
  5. Create an Autopilot deployment profile: Entra join, setup screens to skip, device name template, and standard user rights.
  6. Assign the profile to your devices, usually through a device group.
  7. Prepare policies and apps in your MDM for the same group.
  8. Test with one device: reset it or unbox a new one, sign in, and check that it enrolls and gets its settings.
  9. Roll out to the rest, and ship devices straight to users.

Optionally, add company branding to the Entra sign-in page so users recognise it during setup. For the wider enrollment options on Windows, see Windows device enrollment.

Common Autopilot Problems and Fixes

  • The device shows the normal consumer setup. It isn't registered, the profile isn't assigned yet, or it never reached the internet. Check registration and profile assignment, then reset and retry.
  • Setup stops at sign-in or join. The user isn't allowed to join devices to Entra ID, or a licence is missing. Check the join setting and the user's licences.
  • Enrollment fails after join. Automatic MDM enrollment isn't configured for the user's group, or enrollment restrictions block the device.
  • Network errors during setup. Firewalls, proxies or captive portals block Microsoft's Autopilot, Entra or Windows Update addresses. Use a plain internet connection for first setup.
  • Self-deploying or pre-provisioning fails. These modes need TPM 2.0 and access to the TPM provider's certificate service.

What About MDM and Windows Autopilot?

Autopilot only gets the device ready to be managed; the MDM service applies the actual settings, apps and updates. Microsoft's requirements allow Intune or an alternative MDM service. Autopilot device registrations and profiles are kept in your Microsoft tenant, so check how your MDM reads them before you choose a path. Autopilot device preparation is configured in Intune.

For how Autopilot and Intune fit together, see Autopilot vs. Intune. For setting up new devices on every platform, see device provisioning.

Managing this across many devices

trio.so enrolls Windows PCs through Windows Autopilot, set up once through your Microsoft connection, through Entra join with automatic enrollment, or with a bulk provisioning package. Autopilot devices are read from your Microsoft tenant, which needs a Microsoft Intune licence for that. Policies and apps apply at first sign-in, and Windows PCs sit in the same console as your Macs, iPhones, iPads, Android and Linux devices. Plans start at $5 per device.

The trio.so Integrations catalog with Windows Autopilot connected next to Microsoft Intune, Microsoft Entra ID and Google Workspace.
In trio.so, Windows Autopilot works through your Microsoft connection.

Frequently Asked Questions

What is Windows Autopilot?

Microsoft's cloud service that sets up new Windows PCs for work without IT touching them. At first sign-in, the PC joins Microsoft Entra ID, enrolls in your MDM and receives your settings and apps.

Is Windows Autopilot free?

It has no separate price, but you need a supported Windows edition (Pro, Enterprise or Education), Microsoft Entra ID P1 or P2 and an MDM service, which come with plans such as Microsoft 365 Business Premium or E3.

How do I set up Windows Autopilot?

Turn on automatic MDM enrollment in Entra ID, register your devices, create and assign a deployment profile, prepare policies and apps in your MDM, and test with one device before rolling out.

What is Windows Autopilot device preparation?

A newer version of Autopilot for Windows 11 that needs no hardware hash registration. Devices join a device group at sign-in and receive its apps, scripts and policies, with better progress and reporting. It is configured in Intune.

Do I need Intune to use Windows Autopilot?

Microsoft's requirements accept Intune or another MDM service together with Microsoft Entra ID P1 or P2. Registrations and profiles are kept in your Microsoft tenant, so check how your MDM reads them; Autopilot device preparation is configured in Intune.

Related reading: Autopilot vs. Intune, Windows device enrollment, device provisioning and zero-touch deployment.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Ship PCs that set themselves up

trio.so works with Windows Autopilot so new PCs enroll and get their settings at first sign-in. Plans start at $5 per device.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Microsoft's cloud service that sets up new Windows PCs for work without IT touching them. At first sign-in, the PC joins Microsoft Entra ID, enrolls in your MDM and receives your settings and apps.

It has no separate price, but you need a supported Windows edition (Pro, Enterprise or Education), Microsoft Entra ID P1 or P2 and an MDM service, which come with plans such as Microsoft 365 Business Premium or E3.

Turn on automatic MDM enrollment in Entra ID, register your devices, create and assign a deployment profile, prepare policies and apps in your MDM, and test with one device before rolling out.

A newer version of Autopilot for Windows 11 that needs no hardware hash registration. Devices join a device group at sign-in and receive its apps, scripts and policies, with better progress and reporting. It is configured in Intune.

Microsoft's requirements accept Intune or another MDM service together with Microsoft Entra ID P1 or P2. Registrations and profiles are kept in your Microsoft tenant, so check how your MDM reads them; Autopilot device preparation is configured in Intune.

Related

From the blog

The related industry news, interviews, technologies, and resources.