Study guide

3.2 Autopilot Modes, ESP, and Naming

MD-102 Endpoint Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Exam Overview and MD-102 Study Strategy

Current Exam Facts Audience Profile and Endpoint Admin Mental Model Domain Map and Weighting Strategy Six-to-Ten-Week Study Plan and Readiness Checklist

2 Prepare Infrastructure for Devices

Microsoft Entra Device Identity and Grouping Intune Enrollment by Platform Compliance and Conditional Access Admin Roles, Windows Hello, Windows LAPS, and Local Groups

3 Deploy and Configure Managed Devices

3.1 Autopilot vs. Provisioning Packages 3.2 Autopilot Modes, ESP, and Naming 3.3 Windows 11 Upgrades and Windows 365 Cloud PCs 3.4 Configuration Profiles and Assignment Filters

4 Intune Suite, Remote Actions, and Operational Troubleshooting

4.1 Endpoint Privilege Management and Enterprise App Catalog 4.2 Advanced Analytics, Remote Help, Cloud PKI, and Tunnel for MAM 4.3 Remote Actions and Bulk Actions 4.4 Defender Intelligence, BitLocker Key Rotation, and KQL Device Query Troubleshooting

5 Manage Applications with Intune

5.1 App Deployment Decision Matrix and Packaging 5.2 Microsoft 365 Apps, Office Policies, ODT, OCT, and Admin Center 5.3 App Stores and Update Lifecycle 5.4 App Protection, App Configuration, and Conditional Access

6 Protect Devices, Manage Updates, and Final Review

6.1 Endpoint Security Policies and Security Baselines 6.2 Defender for Endpoint Integration and Onboarding 6.3 Update Rings, Feature Updates, Platform Updates, and Delivery Optimization 6.4 Final Seven-Day Review Plan and Mixed Scenario Priorities

3.2 Autopilot Modes, ESP, and Naming

Key Takeaways Explain This Topic AI

User-driven Autopilot is for devices primarily used by one person and supports Microsoft Entra join and hybrid Microsoft Entra join.

Self-deploying Autopilot is for kiosks and shared devices, requires supported TPM attestation, and supports Microsoft Entra join only.

Pre-provisioned Autopilot splits deployment into a technician flow and a user flow so required device work can complete before the user receives the device.

The Enrollment Status Page can block desktop access until required apps and profiles complete, but blocking app design must avoid fragile dependencies.

Autopilot naming templates apply differently by join type; hybrid scenarios rely on the Domain Join profile computer name prefix rather than the Microsoft Entra join name-template variables.

Last updated: June 2026

Autopilot mode selection

Windows Autopilot is not one deployment mode. It is a set of cloud-driven deployment scenarios that reuse the OEM Windows installation and enroll the device into management. On MD-102, the correct mode usually follows from the device ownership model, user interaction, join type, and whether IT wants to pre-stage the device.

Mode Best scenario Join support Key operational detail

User-driven One primary user, direct shipment, minimal IT touch Microsoft Entra join or hybrid Microsoft Entra join User signs in during OOBE with organizational credentials

Pre-provisioned IT, OEM, or reseller stages device before delivery Microsoft Entra join or hybrid Microsoft Entra join Technician flow completes device work, then device is resealed for the user

Self-deploying Kiosk, shared, or no assigned user Microsoft Entra join only Requires supported TPM attestation and no user sign-in during deployment

Existing devices Reinstall, repurpose, migrate, or use Configuration Manager task sequence User-driven Entra join or hybrid join through JSON Prepares an existing device for an Autopilot deployment

Autopilot Reset Return a known Autopilot device to business-ready state Existing Microsoft Entra joined devices Keeps enrollment path cleaner for reassignment than full troubleshooting

Microsoft recommends new cloud-native endpoints use Microsoft Entra join . Hybrid Microsoft Entra join can still appear in exam scenarios when on-premises Active Directory or legacy Group Policy remains required, but remote hybrid deployments need domain controller connectivity at the right point in the flow, which is a frequent reason remote hybrid Autopilot fails. A key discriminator: self-deploying mode supports Microsoft Entra join only , so any scenario that pairs self-deploying with hybrid join is wrong.

Enrollment Status Page behavior

The Enrollment Status Page (ESP) is the user-facing progress page during enrollment and first sign-in. It can show progress, block device use, enforce timeout behavior, allow log collection, and control what the user can do if installation fails.

ESP tracks three phases:

Device preparation - enrollment and early setup work.

Device setup - device-targeted apps, certificates, network profiles, and tracked policies.

Account setup - user-targeted work after the user signs in.

Blocking is powerful but easy to overuse. If you set Block device use until all apps and profiles are installed to Yes, the user cannot reach the desktop until the tracked work completes or fails according to the configured behavior. You can choose All required apps or a selected blocking-app list. The selected list only filters which already-assigned apps are blockers; it does not assign the apps by itself. If you add an app to the blocking list but never assign it as required to that device or user, ESP simply will not track it.

Operational ESP details that show up on MD-102:

Device-targeted ESP profiles take precedence over user-targeted ESP profiles.

In pre-provisioning and self-deploying scenarios, target ESP to devices because there may be no user context.

If multiple ESP profiles apply, priority controls which profile wins.

Blocking-app lists can contain up to 100 apps.

Mixing line-of-business MSI apps and Win32 apps during ESP can create installer contention because both can use TrustedInstaller.

Installing Windows quality updates during OOBE improves freshness but can add significant time and may require restarts.

Device naming

Autopilot naming belongs to the deployment profile or to the hybrid domain-join path, depending on join type. For Microsoft Entra joined Autopilot devices, use the Autopilot deployment profile option to apply a device name template such as a serial-number or random-character pattern (for example, a %SERIAL% or %RAND:x% variable).

For hybrid Microsoft Entra join , naming is handled through the Domain Join configuration profile . That profile uses a computer name prefix and does not support the same variables used by the Microsoft Entra join device name template. If a question says the device name template field is unavailable in a hybrid profile, the answer is the Domain Join profile with a computer name prefix.

Assignment sequence to remember

A clean Autopilot deployment usually follows this order:

Register the device with Autopilot or ensure the OEM/reseller did it.

Place the device into the correct Microsoft Entra device group.

Assign the Autopilot deployment profile to that device group.

Assign ESP, required apps, compliance, security, and configuration policies.

Verify device deployment status and policy installation after enrollment.

That order matters. An app in the ESP blocking list is not enough if the app is not also assigned as required to the user or device that will receive it. The most common ESP failure is a blocking app that was never actually assigned, so the page either ignores it or, if the app genuinely fails, holds the user at the progress screen until the configured failure behavior releases them.

Pre-provisioned mode in depth

Pre-provisioned mode (formerly called white glove) deserves special attention because it splits the deployment into two flows. In the technician flow , IT, an OEM, or a reseller runs the device-targeted portion of setup, installs device-scoped apps and policies, and then reseals the device. In the user flow , the end user powers on the resealed device and completes only the lighter user-targeted work. The benefit is that time-consuming device setup finishes before the user ever sees the machine, so the user experience at first sign-in is fast.

Because there may be no user context during the technician flow, target the ESP and required apps to device groups for pre-provisioning, not user groups. A pre-provisioning scenario that assigns blocking apps only to users is a setup error the exam may ask you to spot.

Choosing a mode quickly

Use this shortcut. No user signs in and the device is a kiosk or shared with supported TPM attestation: self-deploying (Entra join only). One primary user, direct shipment, minimal IT touch: user-driven . IT wants to finish heavy device setup before handing over the device: pre-provisioned . An already-deployed device must be returned to a clean business-ready state for reuse: Autopilot Reset . An existing or reimaged device must be prepared for Autopilot through a configuration: Autopilot for existing devices .

Pair the mode with the join type the scenario requires, and reject any answer that pairs self-deploying with hybrid join, because self-deploying supports Microsoft Entra join only.