Trigger an Intune Device Sync/Check-in and Verify Status

When an end user reports that they aren't receiving expected Intune policies, configuration profiles, apps, or compliance updates, the most common first-line remediation is to force the device to check in with the Intune service. By default, Windows, macOS, iOS, and Android devices check in with Intune on a schedule (typically every 8 hours once enrolled for longer than a day). A manual sync collapses that wait window to minutes.

This recipe walks through identifying a user's managed device, issuing the remote syncDevice action, and verifying the check-in completed successfully.

When to run this

• User reports missing apps, Wi-Fi/VPN profiles, or certificates pushed from Intune
• Compliance policy changes aren't reflected on the device
• You've just assigned a new configuration profile and want to validate deployment
• Troubleshooting a stale lastSyncDateTime value

After completing this recipe you will have:

• Located the target user's managed device(s) in Intune
• Issued a remote sync command that forces an immediate MDM check-in
• Confirmed the command was accepted by the Intune service (HTTP 204)
• Verified the device's updated lastSyncDateTime and current compliance state
• A clear status report you can share with the requester

Things to watch for

• Device must be online. The sync command is a push notification — if the device is offline, powered off, or on a restricted network, the action will queue but won't complete until the device connects.
• lastSyncDateTime lag. The timestamp in Graph may take 1–5 minutes to update after the device actually checks in. Don't interpret a stale timestamp as a failure immediately.
• deviceActionResults quirk. The syncDevice action may not always appear in the deviceActionResults array. Use lastSyncDateTime as the authoritative signal that the check-in happened.
• Not a fix for enrollment issues. If the device is unenrolled, broken-trust, or the MDM agent is corrupted, a sync won't help — you'll need to re-enroll.
• Rate limits. Avoid looping sync commands against the same device. One sync, then wait 5–10 minutes before retrying.