Microsoft splits the problem into two parts: how fast a change reaches a device, and how fast the result shows up in the Intune admin center. That second part matters as much as the first. A policy that applied in four minutes doesn't help much if the report says "pending" for six hours.
The eight-hour myth, revisited
Microsoft's main point is that the familiar eight-hour check-in describes routine maintenance. It is not how long every change takes to arrive. When something changes on the service side, Intune can find the affected devices and send a push notification that prompts them to check in. Examples include an admin editing a policy, a change to Microsoft Entra group membership, or an App Store app update.
The new part is that push notifications now cover workloads handled by the Intune Management Extension (IME): Win32 apps, scripts and remediations. Until now, those often had to wait for the IME's own polling cycle. Microsoft Learn's IME documentation still says the agent checks for new or updated installations every eight hours, separately from the MDM check-in. Push notifications are meant to get changes through between those polls.
Intune's "What's new" page lists these as separate updates, "Faster delivery of Win32 apps" and "Faster delivery of Windows scripts". It notes that neither one requires a new admin workflow.
For Windows, Intune now adds a second notification channel through the IME alongside Windows Push Notification Services (WNS). This applies to devices that are online. A device that is offline or that misses a notification picks up its changes at the next scheduled check-in.
The new Intune post builds on an April 2026 Intune Customer Success post about how the service prioritizes time-sensitive actions. Admins in the replies to that post were not fully convinced. One said the problem wasn't raw speed but the lack of feedback: they wanted Intune to explain why something hadn't applied, such as a pending restart, and said they'd accept an eight-hour wait if they could see the reason. Another compared Intune unfavorably with gpupdate and gpresult. Microsoft's new post responds to some of those complaints, but not all of them.
Section summary: Push-driven delivery now reaches Win32 apps, scripts and remediations. Offline devices still depend on scheduled check-ins.
Enrollment: removing the dynamic group wait
Enrollment time grouping
Enrollment time grouping (ETG) tackles the slowest step in setting up a new device. Normally, Intune must place a device into groups based on inventory properties and group tags before it knows which apps and policies to send. Microsoft Learn says this can take up to eight hours after enrollment. ETG names a static Microsoft Entra security group in the enrollment policy, so the device joins that group during enrollment.
According to Microsoft Learn, ETG is supported on Windows 11, Android Enterprise, macOS, iOS/iPadOS, tvOS and visionOS. Supported enrollment methods are:
- Windows Autopilot device preparation
- Apple automated device enrollment
- Android Enterprise fully managed, corporate-owned work profile and dedicated enrollment
Setup, in outline:
- In the Intune admin center, create a static Microsoft Entra security group with the Assigned membership type.
- Add the Intune Provisioning Client service principal as an owner of the group. Its AppId is
f1346770-5b25-470b-88bd-d5744ab7952c. In some tenants it appears as Intune Autopilot ConfidentialClient. - Make sure the group is a scope group for the admin's Intune role.
- Under Devices > Device onboarding > Enrollment, create or edit the enrollment policy for your platform and select the group. Each policy takes one static group.
- Assign required apps and policies to that group.
Points to watch:
- ETG applies only to new enrollments.
- Changes to the group settings don't affect devices that are already enrolled.
- The Android staging token isn't supported.
- ETG for Apple automated device enrollment isn't available in some sovereign clouds, including Azure Government and Azure operated by 21Vianet.
Microsoft recommends monitoring Devices > Monitor > Enrollment time grouping failures. If a device fails to join the group, configuration might change or be removed after enrollment. That report can take up to 20 minutes to update.
Immediate app checks after ESP and Autopilot device preparation
Microsoft also says that when the Enrollment Status Page (ESP) or Autopilot device preparation finishes, Windows and macOS devices now check right away for any remaining required app assignments. Microsoft Learn's IME documentation confirms this for Windows: required Win32 apps that weren't installed during provisioning start installing sooner. The IME must be version 1.58.103.0 or later. Older versions don't receive Win32 apps, scripts or remediations at all.
For macOS, Intune's "What's new" page describes more frequent check-ins by the Intune management agent:
- During onboarding, the agent checks in every three minutes for the first 15 minutes, then every 15 minutes for two hours.
- After enrollment, its regular check-in interval drops from about eight hours to one hour.
Section summary: ETG removes the dynamic group delay, and the post-provisioning app check removes the wait for the next routine check-in.
Compliance that notices changes on its own
Before, if a user turned off the firewall, Intune might not notice until the next scheduled evaluation. Windows now combines scheduled monitoring with event-driven detection. When a supported setting changes, the device can request a check-in and a compliance reevaluation. If protection is turned back on, the device can also request a recheck so it returns to compliant sooner. Microsoft lists these supported settings:
- Firewall
- Antivirus
- BitLocker
- Microsoft Defender status
- Operating system build version
- Real-time protection
- Secure Boot
Microsoft Learn adds two caveats:
- Throttling: Intune limits compliance-triggered reevaluations, so if several changes happen close together, some may be handled in a later cycle.
- BitLocker: this setting is measured at boot time, so a reboot may still be needed before a newly encrypted device shows as compliant.
For custom compliance scripts on Windows and macOS, admins can now set how often scripts are evaluated: 15 minutes, 30 minutes, or anywhere from one to eight hours. Shorter intervals mean faster detection but more work for the device.
Section summary: The device can now report compliance changes itself, but throttling and the BitLocker reboot requirement still apply.
Reporting: timestamps and consistent counts
On the reporting side, Microsoft says it has changed backend processing to cut delays in supported policy-related reports. Some reports now combine recent changes with data that was already processed. Report timestamps are rolling out so admins can see how fresh the data is. Microsoft has also made changes so summary views, device details and reports show the same counts, and says more work is underway to separate the configuration admins intended from the state devices actually report.
These are Microsoft's own claims. The post gives no benchmark numbers, no list of affected reports and no general-availability dates, so treat them as direction rather than guarantees.
The Sync button gets more useful
On Windows, Intune management runs through two clients: the built-in MDM client and the IME. According to Microsoft, the old remote Sync action mainly reached the MDM side through WNS and didn't necessarily wake the IME. In practice, clicking Sync to fix a Win32 app could do nothing for the Win32 app.
The improved Sync starts check-ins on both clients with a single request. Microsoft Learn describes the procedure:
- Go to Devices > All devices and select the device.
- Select Sync in the action bar, then confirm with Yes.
- Open the Device sync status tab in the device overview to follow progress.
Platform scope is narrower than it may look. Microsoft Learn says the multi-workload sync behavior and the Device sync status tab apply only to Windows and iOS/iPadOS. The Sync action itself still works on Android, macOS, tvOS and visionOS, but without these improvements. The Sync documentation also says the "Preview new device view" toggle must be on. However, "What's new" now states that the new single-device page is the default, so check what your tenant shows.
A completed sync doesn't mean the underlying problem is fixed. If a device is still noncompliant, look at its compliance evaluation. If a Win32 app still hasn't arrived, check its deployment state, requirements, dependencies and detection rules. On the device itself, the IME logs in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs (especially AppWorkload.log) remain the most useful evidence.
Enhanced app inventory: delta uploads and two timestamps
Enhanced app inventory has to be turned on. Discovered Apps collected data the moment a device enrolled, App Inventory sits dormant until you build a Properties catalog policy and assign it. Microsoft Learn describes the setup: create a policy with Platform: Windows 10 and later; Profile type: Properties catalog. MSEndpointMgr adds that you then go to Configuration settings, click + Add Properties, tick ApplicationProperties, and choose your properties. Assigning the policy also installs a collection agent. Peter van der Woude notes that the Microsoft Device Inventory Agent will be installed when a Properties catalog profile is assigned.
After setup, eligible devices report inventory several times a day. The first upload is a full list. After that, devices send only additions, updates and removals. Each record carries two dates:
- Last updated: when that app record last changed.
- Last checked: the date the device last reported app inventory data.
Comparing the two tells you whether an entry is old because nothing changed or because the device hasn't reported recently. Besides name and version, records can include architecture, install scope, install location and estimated size, for both device-level and per-user installs.
The documentation currently lists Windows 10/11 devices that are enrolled in Intune and Microsoft Entra joined. That leaves out hybrid-joined devices, which still make up a large share of many fleets. Microsoft Learn calls enhanced inventory the long-term replacement for Discovered apps, but for now the two run side by side.
The bottom line
None of these changes is a dramatic launch, and together they matter more than any one of them would alone. Taken as a whole, they address real problems that admins have raised about Intune's speed and visibility.
Some limits remain:
- Push notifications only help devices that are online and can reach the notification endpoints. Proxies and firewalls still need to allow that traffic.
- Real-time compliance is subject to throttling.
- The improved Sync and the new app inventory have platform and join-type restrictions.
- Microsoft's reporting claims come without numbers.
Even so, many admins should see shorter waits on a new hire's first morning, and the Sync button now has a status tab that shows what happened after you click it.
References
- Intune’s journey to faster device management Microsoft Intune Blog · 2026-11-18T18:15:23+00:00
- Introducing Intune's New App Inventory Feature - MSEndpointMgr msendpointmgr.com
- Intune’s journey to faster device management techcommunity.microsoft.com