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

Swahela Mulla 100 Reputation points
2026-09-11T14:49:34.2933333+00:00

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.

Intune_OnDemand_Remediation_Detailed_Question.pdf

Microsoft Security | Intune | Configuration
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-09-11T14:49:54.86+00:00

    Supported facts from the available documentation:

    • The on-demand action is available as Run remediation (preview) in the Intune admin center and as the Microsoft Graph action initiateOnDemandProactiveRemediation.
    • The action is for Windows devices.
    • Required Intune permissions include Remote tasks/Run Remediation plus permissions that provide device visibility and access.
    • Remediations are executed by the Microsoft Intune Management Extension service.
    • Policy retrieval for Remediations occurs after device restart, after user sign-in, and once every 8 hours. The 8-hour retrieval schedule is fixed from when the Intune management extension service starts.
    • Reporting behavior is not immediate in every scenario. For scripts set to run once, results are reported after the script runs. For recurring scripts, reporting follows a seven-day cycle, with change-based reporting in the first six days and a full report every seven days.
    • Monitoring is available in the Intune admin center under Devices > Manage devices > Scripts and remediations > Device status. Output can also be exported to .csv.

    For verifying delivery and execution, the documented path is:

    1. In the Intune admin center, go to Devices > Manage devices > Scripts and remediations.
    2. Review the remediation overview.
    3. Select Device status to see per-device status details.
    4. Use Export to save results to .csv for analysis.

    For manually triggering the action from the portal:

    1. Go to Devices > All devices.
    2. Select the device.
    3. Select Run remediation (preview).
    4. Select the script package.
    5. Select Run remediation.

    The available context does not document:

    • reliability percentages for large-scale parallel use
    • queueing behavior
    • throttling limits
    • known intermittent delivery issues
    • GA timeline or roadmap for the preview API
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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