Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.1.2. Autopilot Deployment Modes and Device Name Templates

💡 First Principle: A deployment mode answers "who is in front of the device during setup?" — the user, a technician followed by the user, or nobody. The fewer people involved, the more the device has to prove about itself, which is why the modes with no user at the keyboard demand a physical TPM 2.0 that can attest to the hardware's identity.

Classic Autopilot offers four modes, and device preparation offers two.

ModeExperienceJoin typesHardware requirementTypical use
User-driven (classic)User signs in with Entra credentials; device ESP, then user ESPEntra join or hybrid joinNo TPM attestation stepStandard employee laptops
Pre-provisioned (classic)Technician phase first, then a shorter user phaseEntra join or hybrid join (user-driven)Physical device, TPM 2.0 with attestation; VMs not supportedLarge rollouts where users shouldn't wait for app installs
Self-deploying (classic)No user interaction (none at all over Ethernet)Entra join onlyPhysical device, TPM 2.0 with attestation; VMs fail with 0x800705B4Kiosks, digital signage, shared devices, Teams Rooms
Existing devices (classic)Configuration Manager task sequence applies a JSON profileEntra join or hybrid joinUser-driven profiles onlyReimaging devices already in service
User-driven (device preparation)User signs in; essentials install during OOBEEntra join onlyWindows 11New corporate devices with no pre-registration
Automatic (device preparation)Apps install before the user signs inWindows 365 Cloud PCsCloud PCCloud PC provisioning

User-driven is the default: the user enters Entra credentials on a branded sign-in page, the device joins and enrolls, the device phase of ESP runs, then the user phase. Hybrid join adds a Domain Join profile, the Intune Connector for Active Directory and line of sight to a domain controller — though Microsoft now says hybrid join for new devices "isn't recommended, including through Windows Autopilot".

Pre-provisioning (formerly "white glove") splits the work. A technician, partner or the OEM runs the slow technician phase; the user later runs a short user phase.

The technician phase applies every device-targeted policy and installs device-context Win32 and LOB apps. Wait at least 90 minutes before the user flow so tokens refresh, and run it within six months or the Intune Management Extension certificates may expire. The profile's Allow pre-provisioned deployment setting must be Yes; otherwise the technician can still start the flow, but it fails with 0x80180005.

Self-deploying mode runs userless, so no primary user is set: user self-service BitLocker recovery and user-assigned Company Portal apps aren't available, and only device-targeted ESP profiles and compliance policies apply.

Device name templates follow different rules per feature:

  • Classic deployment profile: Apply device name template requires the Microsoft Entra join type. Names are at most 15 characters (letters, numbers and hyphens, not all numbers) with the macros %SERIAL% and %RAND:x%. KIOSK-%RAND:6% produces 6 + 6 = 12 characters, within 15.
  • Hybrid join: you can only give a computer name prefix, in the Domain Join profile; variables such as %SERIAL% aren't supported.
  • Device preparation and device association: names can be up to 63 characters, and the template applies only to associated devices.
  • Windows 365: 5–15 characters, covered in 3.1.5.

Hybrid join needs a current connector. The Intune Connector for Active Directory runs on Windows Server 2016 or later. Versions older than 6.2501.2000.5 are deprecated and can no longer process enrollment requests, and there's no automatic upgrade — you uninstall the legacy connector and install the new one. Since February 2025 it runs as a low-privileged Managed Service Account (msaODJ plus five random characters) that by default can create computer objects only in the Computers container; to use OUs, add them to the connector's configuration and delegate Create computer accounts on each. Each domain needs its own connector, with at most one per server.

⚠️ Exam Trap: Testers often assume that because user-driven deployments work in a lab, every mode does. Self-deploying and pre-provisioning both require a physical device with TPM 2.0 and device attestation. Virtual machines — including Hyper-V with a virtual TPM — fail with a timeout error (0x800705B4), so "test self-deploying mode in a VM" is never a valid plan.

Reflection Question: Your service desk wants new laptops to reach users with every device app already installed, and the laptops must be hybrid joined to the on-premises domain. Which mode do you choose, what does the hybrid requirement add to the setup, and why can't the technician test the flow on a Hyper-V virtual machine first?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned