Forum Discussion

Swahlea's avatar
Swahlea
Copper Contributor
Sep 11, 2026

Intune On-Demand Proactive Remediation API Reliability for Large-Scale Usage

Hi Team,

We are testing the Intune On-Demand Proactive Remediation API:

POST /deviceManagement/managedDevices/{managedDeviceId}/initiateOnDemandProactiveRemediation

In our environment, the remediation package works correctly, and the API generally triggers the remediation as expected. However, during repeated testing, we noticed that a small percentage of requests do not seem to reach the endpoint.

For example:

  • 20 remediation requests sent
  • 18-19 execute successfully
  • 1-2 never trigger on the target device
  • Devices are online and managed by Intune
  • Added a 30-second delay between requests, but the behavior still occurs intermittently

Before adopting this in production for a large client base, we'd like to understand:

  • Has anyone observed similar behavior?
  • Is this API reliable for triggering remediation across multiple devices in parallel?
  • Are there any known limitations, queueing mechanisms, throttling considerations, or best practices?
  • Is there a recommended way to verify that a remediation request was actually delivered to the device?
  • Since this API is still in the beta/preview stage, is there any information on its roadmap or GA timeline?

Note: For additional context, detailed test results, observations, and environment information, a PDF containing the complete analysis has been attached.

Any guidance or real-world experience would be greatly appreciated.

 

Thank you.

https://learn-attachment.microsoft.com/api/attachments/1ad5bea4-9038-4b25-9a2a-a9e66a870f6a?platform=QnA
https://learn.microsoft.com/en-us/graph/api/intune-devices-manageddevice-initiateondemandproactiveremediation?view=graph-rest-beta

Graph API
intune
Intune API
Intune Reports
mobile device management (mdm)

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Sep 12, 2026

    Your 18–19 successful executions out of 20 requests warrant investigation, but an HTTP 204 response is not endpoint execution evidence. Microsoft documents that repeated Run remediation actions for the same device can overwrite each other, and delivery requires working Intune and Windows Push Notification Service connectivity at submission time. A fixed 30-second delay therefore does not guarantee delivery. Serialize actions per device, verify its Remediations monitoring status, and correlate timestamps with Intune Management Extension logs before retrying. For HTTP 429 responses, honor Retry-After; use exponential backoff when that header is absent. Across devices, pilot bounded concurrency and measure confirmed execution rather than request acceptance. Microsoft supports Intune beta APIs, but this on-demand feature remains documented as preview. The cited documentation provides neither a fleet-scale delivery guarantee nor a GA date. Escalate the reproducible misses with request IDs and logs before treating it as a guaranteed production orchestrator