Skip to content

Compliance Policy Strength

The question it answers: Which compliance policies are too weak to trust - long grace periods, no password or encryption, no minimum OS?

Conditional Access trusts ‘compliant’ devices - so compliance is only as strong as the policies behind it. A long grace period, no password or encryption requirement, no minimum OS or allowed jailbroken devices make ‘compliant’ mean little. Compliance Setting Failures shows which devices fail; this report shows how high the bar is.

Where in the appIntune › Device Operations & Hardening › Compliance Policy Strength
WorkloadIntune
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceMicrosoft Intune.
Report id (API and MCP)intune.operations.compliance-policy-strength
ColumnKeyType
SeveritySeverityStatus
PlatformCategoryText
PolicySubjectLink
CheckSettingText
Grace periodValueText
FindingFindingText
Assignment / min OSDetailText
ModifiedWhenDate
GapsNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

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?$expand=scheduledActionsForRule($expand=scheduledActionConfigurations),assignments
GET /ir-api/v1/reports/intune.operations.compliance-policy-strength?size=100

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