Skip to content

Compliance Failures by Setting

The question it answers: Which compliance settings make devices non-compliant, and on how many devices?

Non-compliant devices are blocked by Conditional Access, but the device list does not say why. This breaks compliance down by setting - OS version, BitLocker, password, Defender, jailbreak - so you fix the one cause behind hundreds of tickets.

Where in the appIntune › Endpoint Security & Readiness › Compliance Failures by Setting
WorkloadIntune
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Intune.
Report id (API and MCP)intune.endpoint.compliance-setting-failures
ColumnKeyType
SettingSettingNameText
PolicyPolicyNameText
FailingFailingStatus
Non-compliantNonCompliantCountText
ErrorErrorCountText
ConflictConflictCountText
CompliantCompliantCountText
FilterKey (API)On when the page opens
Only settings with failuresfailingYes

Licence: Microsoft Intune.

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

PermissionAPIWhat it allowsNote
DeviceManagementConfiguration.Read.AllMicrosoft GraphRead Microsoft Intune device configuration and policies
Data sources it reads
  • GET /v1.0/deviceManagement/deviceCompliancePolicies
  • GET /v1.0/deviceManagement/deviceCompliancePolicies/{id}/deviceSettingStateSummaries
GET /ir-api/v1/reports/intune.endpoint.compliance-setting-failures?size=100
GET /ir-api/v1/reports/intune.endpoint.compliance-setting-failures?filter=failing

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