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

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