Force Intune settings sync on computers (updated 2026)

Default intervals

Default refresh intervals for policies and compliance checks

Intune sends a notification to the device to check in with the service. The timing of these notifications can vary, ranging from immediately to several hours. The frequency of these notifications can also differ depending on the platform.

Microsoft documentation states:

But in reality, the concept of 8 hours is more complex than that, and I invite you to read this article:

The Truth About the 8-Hour Intune Sync (and Why It’s a Myth)

Many believe Intune policy delivery happens every eight hours, but it doesn’t. Learn how Intune sync delivers new policies within minutes.

Patch My PCRudy Ooms

And, for a full of how it works, I strongly recommend reading another Rudy Ooms' article :

How Intune Syncs Work: PowerShell and Win32 App Delivery vs Policy Delivery

Intune Sync: Win32Apps vs Policies. This blog explains how IME handles Win32 Apps and PowerShell, while OMA-DM delivers policies.

Patch My PCRudy Ooms

If the device doesn't check in to receive the policy or profile after the initial notification, Intune will attempt to notify the device three more times. If the device is offline, such as if it is powered off or not connected to a network, it may not receive these notifications. In this case, the device will receive the policy or profile during its next scheduled check-in with the Intune service. This also applies to checks for non-compliance, including situations where a device moves from a compliant to a non-compliant state.

If devices have recently enrolled, then compliance, non-compliance, and configuration checks will occur more frequently. The frequency of these checks is roughly as follows:

Default refresh interval for Win32 applications and scripts

The deployment of PowerShell scripts or Win32 applications (.exe via intunewin) follows its own schedule, occurring every 60 minutes.

The Intune management extension agent checks after every reboot for any new scripts or changes.

Once the script executes, it doesn't execute again unless there's a change in the script or policy.

If the script fails, the Intune management extension agent retries the script three times for the next three consecutive Intune management extension agent check-ins.

For policies, check the keys Results et Download Count in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Policies\UserGUID\policyGUID

For Win32Apps and scripts, check : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Win32Apps\UserGUID\ScriptGUID

To get guid for an app/script, use C:\ProgramData\Microsoft\IntuneManagementExtension\Logs

Force the synchronization to Intune

When you worked with on-premise environments, like Active Directory, you often use some commands to force the configuration applying on computers.

For example, in an AD, you use to run gpupdate, but, what is the gpupdate in Intune ?

You should know that even with the execution of these commands, it may take between 8 and 24 hours for everything to be applied.

Method 1 : Company Portal

The Company Portal application allows you to force both the synchronization of settings and the execution of scripts/deployment of Win32 applications.

Method 2: Settings > work & school Account > Sync

This only triggers the synchronization of settings, but not the execution of scripts or the deployment of Win32 applications.

Method 3: Command line

On the computer run Powershell as admin an execute:

Get-ScheduledTask 'PushLaunch' | Start-ScheduledTask

If you deploy Win32 applications (.exe via intunewin) or PowerShell scripts you also have to restart the Microsoft Intune Management Extension service. There are several methods:

# Method 1 : restart the service (admin required)
Restart-Service 'IntuneManagementExtension'

# Method 2 : use the sync command from run/Win+R (admin not required)
intunemanagementextension://syncapp