Skip to content

Remediation & Platform Script Failures

The question it answers: Which remediations and platform scripts fail on devices, or fix issues that keep coming back?

Remediations (detection + fix scripts) and platform scripts quietly keep devices in shape - until they fail. A detection or remediation script erroring on many devices means the problem it was written for is back; issues that keep re-occurring mean the fix does not stick.

Where in the appIntune › Endpoint Security & Readiness › Script Failures
WorkloadIntune
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Intune; Remediations need Windows Enterprise E3/E5 (or equivalent) licences.
Report id (API and MCP)intune.endpoint.script-failures
ColumnKeyType
ScriptDisplayNameText
KindKindText
StatusSeverityStatus
ErrorsErrorCountText
Error %ErrorPercentText
Remediation errorsRemediationErrorCountText
Issue re-occurredReoccurredCountText
SucceededSuccessCountText
Last runLastRunDateTimeDate
FilterKey (API)On when the page opens
Only scripts with errors or recurring issuesproblemsYes

Licence: Microsoft Intune; Remediations need Windows Enterprise E3/E5 (or equivalent) licences.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
DeviceManagementConfiguration.Read.AllMicrosoft GraphRead Microsoft Intune device configuration and policies
DeviceManagementScripts.Read.AllMicrosoft GraphRead Microsoft Intune Scripts
Data sources it reads
  • GET /beta/deviceManagement/deviceHealthScripts/{id}/runSummary
  • GET /beta/deviceManagement/deviceManagementScripts/{id}/runSummary
GET /ir-api/v1/reports/intune.endpoint.script-failures?size=100
GET /ir-api/v1/reports/intune.endpoint.script-failures?filter=problems

An AI assistant reads it with the MCP tool get_report and the id intune.endpoint.script-failures. The client needs the Read grant for Intune. See Using the API.