Event banner
Windows Office Hours: September 19, 2024
Event Ended
Thursday, Sep 19, 2024, 08:00 AM PDTEvent details
Get answers to your questions about adopting Windows 11 and managing the Windows devices used by remote, onsite, and hybrid workers across your organization. Get tips on keeping devices up to date ef...
Heather_Poulsen
Updated Nov 19, 2024
HeyHey16K
Sep 19, 2024Iron Contributor
Is there a limit on the number of times you can sync a device from the Intune console within a certain timeframe (e.g. an hour)? First couple of device syncs seem to happen very quickly (and the timestamp updates on the device record in Intune) but then successive syncs seems to take up to 30 mins.
- Jason_SandysSep 19, 2024
Microsoft
Hi Michelle, Yes, there is throttling on manually initiated policy refreshes from the console or locally on devices to prevent adding pressure on the service and the device itself. The throttling details are undocumented and subject to change. Is there a specific requirement or expectation on your part? What challenge are you facing where this is significant, and you need or want to attempt to manually initiate policy refreshes rapidly?- HeyHey16KSep 20, 2024Iron ContributorHi Jason, thank you for your response. As Hans says, when you're testing policy changes etc. it gets frustrating to not be able to instantly sync. Could Microsoft consider allowing us to add test devices to a group that would allow more frequent syncs? Or can we force them using "restart-service IntunemanagementExtenstion" perhaps? Thank you
- Jason_SandysSep 20, 2024
Microsoft
So, to be clear here, you can absolutely manually sync the policy and have it update in real-time. What you can't do is initiate a sync over and over again in a very short period of time. This throttle is in place because the end effect of doing this would be to actually slow the process down as it queues up more and more requests. Also, keep in mind that for one-off testing and troubleshooting purposes, policy changes targeted to a small number of devices will automatically be pushed to the devices at the time you make the changes. This is also subject to throttling though for similar reasons.
- Lawrence11Sep 19, 2024Copper Contributor
Hi Jason, Not having rapid policy refresh I feel is a significant challenge in testing scenarios where you need to work effeciently in testing new policies, changes. At minimum it would be nice to see a notification you have been throttled, so it is quickly apparent that things aren't really "broken".
- Jason_SandysSep 20, 2024
Microsoft
Hans, please see the comment I just posted to Michelle. Basically, for testing purposes, ensure that you are targeting the policies to a very small set of devices (<5). This will ensure those changes are immediately sent to those devices. IME troubleshooting issues, these changes always happened almost instantly on my test devices without any need to manually refresh anything. This does assume you have not disabled and are not blocking Windows Notification Services on Windows devices.