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.3. The Enrollment Status Page

💡 First Principle: A new device is most vulnerable, and most frustrating, in the gap between "enrolled" and "configured". The Enrollment Status Page closes that gap by holding the user at a progress screen until the apps and profiles you care about have arrived — trading a few minutes of waiting for a device that is complete and secure the first time the user sees the desktop.

The ESP works with the default Microsoft Entra join OOBE and with every classic Autopilot scenario. It does not work with Autopilot device preparation, which has its own progress indicator and no ESP. You create profiles at Devices > Device onboarding > Enrollment > Windows > Windows Autopilot > Enrollment Status Page, up to 51 per tenant (the Default profile plus 50).

ESP tracks setup in three phases: Device preparation, Device setup and Account setup; the last runs when the user signs in. The settings that matter most:

  • Show app and profile configuration progress turns the ESP on; No hides it.
  • Show an error when installation takes longer than specified number of minutes defaults to 60. Hybrid Autopilot deployments get 40 minutes more, so the connector has time to create the Entra device record.
  • Only show page to devices provisioned by OOBE shows the user phase only to the first user who signs in.
  • Block device use until all apps and profiles are installed unlocks three more settings: allow users to reset the device if installation fails, allow users to use the device if installation fails, and which apps are blocking — All, or up to 100 Selected.
  • Install Windows quality updates (might restart the device) is the newest setting, enforced from the January 13, 2026 quality update. It defaults to Yes on new profiles and No on existing profiles until you edit them.

The quality-updates setting deserves attention because it changes long-held assumptions. When it's on, the device installs the monthly quality update during OOBE, adding 20–40 minutes and possibly a restart. It needs Block device use set to Yes, doesn't install over a metered network, and doesn't support user-targeted ESP profiles. It isn't honored in the pre-provisioning technician flow but is honored in the user flow. For autologon scenarios such as kiosks and Teams Rooms, set it to No. ESP honors update ring deferrals and pauses.

Blocking apps filter tracking; they don't assign. An app must already be assigned to the device or user to install. The blocking list only decides which assigned apps the ESP waits for. In user-driven and self-deploying modes, a Win32, Store or Enterprise App Catalog app that isn't on the list installs after ESP finishes. For pre-provisioning, Only fail selected blocking apps in technician phase (the default for pre-provisioned deployments) attempts every required app but only fails the technician phase if a blocking app fails; non-blocking failures retry in the user flow.

Priority. Profile 1 is the highest priority. The highest-priority device-targeted profile applies first, then the highest-priority user-targeted one, then Default; in pre-provisioning and self-deploying, only device-targeted profiles apply.

What ESP tracks, and what breaks it. It tracks certificates, Wi-Fi and VPN profiles, LOB MSI, Store, Win32 and WinGet apps, but not security policies such as device restrictions. The documented failures are worth recognizing:

  • Mixing LOB (MSI) and Win32 apps. Both use TrustedInstaller; the Win32 install fails with "Another installation is in progress" and ESP fails. If you need both, use device preparation, which supports mixing.
  • The Microsoft 365 Apps (Windows 10 and later) app type can hang ESP. Microsoft recommends deploying Microsoft 365 Apps as a Win32 app instead.
  • A user with no Intune license can leave ESP stuck at "Identifying".
  • Restarts inside app packages can hang ESP. Restarts are supported in Device setup, not in Account setup.

⚠️ Exam Trap: "Configure the Enrollment Status Page to block until apps install" is a wrong answer for any scenario built on Autopilot device preparation, because device preparation has no ESP. Its equivalent is selecting the essential apps (up to 25) and scripts (up to 10) in the device preparation policy itself.

Reflection Question: A pilot group's laptops reach the desktop before a required VPN client installs, and a second group's deployments fail with "Another installation is in progress". What ESP setting fixes the first problem, what is causing the second, and which two remedies does Microsoft suggest?

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