Your Windows device is deployed. But is it really ready?

17/11/2026

A familiar scenario: A device is being provisioned with Autopilot, and the user is ready to start using their new device. The desktop loads, and they’re immediately greeted with several notifications about Windows and application updates. This isn’t ideal—it’s frustrating for both end users and IT departments. Microsoft and Intune are changing the process, shifting the focus from provisioning devices to getting them ready for work and with the latest improvement we now have the options to get to a work ready device. Read on to learn more.


Windows Autopilot: From Zero-Touch to Up-to-Date

Provisioning has evolved with the introduction of Windows Autopilot and Device Preparation, making zero-touch deployment possible. However, gaps remained, particularly when it came to keeping Windows and applications up to date. 

Custom scripts and third-party tools could help address these gaps, but in recent months, Microsoft Intune has introduced built-in capabilities that can turn a zero-touch deployment into a more up-to-date device.

By combining Windows security updates during enrollment with Enterprise Application Management (EAM) auto-update apps, we can move beyond simply provisioning a device and get much closer to delivering a device that is configured, patched, and ready for work

This approach combines several features: some are included in all Microsoft Intune plans, while others are available as add-ons or included in enterprise licenses. Some of these features have been available for quite some time, but it’s their combination that makes the difference. 

In this post, I’ll describe these features and explain how they can take a device from Autopilot-ready to work-ready.


Windows Updates During ESP Autopilot

This highly requested feature has been available for some time. Personally, I saw it as a sign that Microsoft was shifting toward ensuring devices are up to date after enrollment. It lets us control whether quality updates are installed during Autopilot enrollment through the Enrollment Status Page (ESP). As mentioned earlier, this article focuses on the complete solution, so I won’t go into detail about the feature itself. We can enable it directly in the ESP settings in Intune.

In the Intune portal, go to:
Devices > Enrollment > Enrollment Status Page 
Select the slider to Install Windows updates.

Enable Windows Updates during ESP
Enable Windows Updates during ESP

When enabled, Windows monthly security updates are installed during provisioning, allowing the device to receive the latest applicable security update before the user reaches the desktop.

Windows Updates during ESP
Windows Updates during ESP

Auto-Update EAM Apps During Enrollment

This is where things get interesting. Enterprise Application Management and Auto-update apps aren't new, but their integration with Windows Autopilot has taken an important step forward. EAM auto-update apps can now be used as blocking apps during enrollment. Instead of installing an application during Autopilot and updating it afterwards, we can make the current EAM-managed application part of the provisioning experience itself. 

Combined with Windows security updates during enrollment, we can address both sides of the equation: the operating system and the applications running on it.

The configuration depends on the Autopilot deployment method you're using.

AutoPilot ESP Enrollment

For the Autopilot Enrollment Status Page (ESP), go to the following location in the Intune portal: 

Devices > Enrollment > Enrollment Status Page

Under Blocking apps, select the apps to install during enrollment.

ESP Blocking apps
ESP Blocking apps

Device Preparation

For Device Preparation, from the Intune Portal head over to:

Devices > Enrollment > Device Preparation Policies

Add the required applications to the apps assigned through the Device Preparation policy. 

Device Preperation Profile allowed apps
Device Preperation Profile allowed apps
Note: Enterprise Application Management requires additional licensing beyond Intune Plan 1 or Plan 2, unless it's included as part of another eligible Microsoft license in your environment like M365 E5.

Should every application be a blocking app?

Probably not. A work-ready device doesn't necessarily need every application installed before the user reaches the desktop. Adding more blocking applications increases the dependencies during provisioning and can increase deployment time or cause ESP to fail when one application has an installation problem. I would therefore only block applications that are truly required for the user's first sign-in experience. Everything else can be installed after enrollment.

Good Candidates for Blocking Apps

  • Security tooling
  • A required browser
  • VPN or connectivity software
  • Core productivity applications
  • Business-critical applications required immediately

Better Installed After Enrollment

  • Optional utilities
  • Department-specific applications that aren't immediately needed
  • Applications that aren't required on day one

The goal isn't to install as much as possible during Autopilot. It's to install just enough to make the device secure and productive from the first sign-in. This distinction is important. A shorter, reliable provisioning process can provide a much better user experience than making a user wait for every possible application before access to the desktop is allowed.


From zero-touch to work-ready

By combining these capabilities, we can move beyond zero-touch provisioning and get much closer to delivering a truly work-ready device. The process can be summarized in four steps:

AI generated
Four steps from Zero Touch to Work Ready

Final Thoughts

For me, this changes what we should consider a successful Autopilot deployment. Getting a user to the desktop shouldn't be the finish line. Getting them to a desktop that is configured, patched and ready for work should be. Windows security updates during enrollment address the operating system, while EAM auto-update apps help address the application layer. 

Now that those applications can also block enrollment, the pieces fit together much better. That doesn't mean we should make every application blocking.

The goal is to install just enough during provisioning to make the device secure and productive from first sign-in. 

So instead of asking"Did Autopilot complete successfully?", perhaps the better question is: "Is the device actually ready for the user?"