Share via

Does Microsoft Graph API Throttle When Triggering More Than 200 On-Demand Remediation Calls?

Swahela Mulla 100 Reputation points
2025-08-13T10:18:07.4333333+00:00

Hi Everyone,

I'm using the following Microsoft Graph API endpoint to trigger proactive remediation scripts on Intune-managed devices:

POST https://graph.microsoft.com/beta/deviceManagement/managedDevices/{managedDeviceId}/initiateOnDemandProactiveRemediation

My scenario involves triggering this API for e.g. 200+ devices, each with multiple scripts. I have a few concerns and would appreciate guidance:

  1. Are there any throttling limits specific to this endpoint or Intune service that I should be aware of?
  2. If I send 200+ POST requests in a short time window, will I hit rate limits or get 429 errors?
  3. What is the recommended approach to avoid throttling—should I batch requests, add delays, or use retry logic?
  4. Is there any official documentation or best practices for handling bulk remediation triggers?

I’ve reviewed the general Microsoft Graph throttling guidance and service-specific throttling limits, but I’m unsure how they apply to this specific endpoint.

Any help or examples would be greatly appreciated!

Thanks,
Swahela Mulla

Microsoft Security | Intune | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pauline Mbabu 1,410 Reputation points Microsoft Employee
    2025-08-19T06:52:27.1566667+00:00

    Hello @Swahela Mulla ,
    As per the Microsoft Graph service-specific throttling limits there is no Specific throttling Limit Published for that endpoint, so the throttling limit will fall under the Microsoft's Graph Global Throttling Limit as indicated on this doc -Microsoft Graph service-specific throttling limits.

    To avoid throttling when triggering proactive remediation scripts on Intune-managed devices via the Microsoft Graph API, it's recommended to batch requests using JSON batching, add short delays between requests to reduce burst load, and implement robust retry logic based on the HTTP 429 error code. When throttling occurs, use the Retry-After header to determine how long to wait before retrying the request, and continue retrying with the specified delay until the request succeeds. If no Retry-After header is provided, apply an exponential backoff strategy. Avoid immediate retries and high-frequency polling patterns, as these can worsen throttling and degrade performance. Instead, use change tracking or notifications when available. - https://learn.microsoft.com/en-us/graph/throttling#best-practices-to-handle-throttling

    Unfortunately, I could not find any official doc for handling bulk remediation triggers. But you can look at this doc for https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/remediations which touches on running on demand Remedition Scripts.

    If you find the answer above helpful, please Accept the answer to help anyone in the community who might have a similar question to quickly find the solution.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.