1. Resources
  2. Detection rules
  3. Intune Compliance Policy Changed or Deleted

Intune Compliance Policy Changed or Deleted detection rules

An attacker edits or deletes an Intune compliance policy so that a device they control, or every device, counts as compliant and passes Conditional Access policies that require a compliant device.

Platform
Microsoft Intune
Severity
Medium
Log source
Microsoft Intune audit logs
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
An identity with the Device compliance policies permissions in Intune, and no Multi Admin Approval access policy for compliance policies.
Impact
Unencrypted, unpatched or Defender-flagged devices keep their access, and a device enrolled by the attacker can satisfy policies that protect administrator portals.
Response
Contain the actor and remove its Device compliance policies permissions, then restore the policy and its assignments to the approved configuration.
Mitigation
Create a Multi Admin Approval access policy for compliance policies, and mark devices with no compliance policy assigned as not compliant.
Operation
*CompliancePolicy*
Threat groups
None listed in MITRE ATT&CK for this technique

How the attack works

Conditional Access can require that a device is marked as compliant. Intune decides that state from the compliance policies assigned to the device and from the tenant-wide compliance policy settings. Whoever can change those policies controls the answer Conditional Access receives: removing a requirement such as encryption, a minimum operating system version or a Defender risk level, lengthening the grace period of the action for noncompliance, or deleting a policy all make more devices compliant without touching Conditional Access itself.

One tenant-wide setting matters most. Mark devices with no compliance policy assigned as is set to Compliant by default, so where that default is still in place, deleting a policy or its assignment turns every device it covered into a compliant one. Compliance policies can be changed by Intune Administrator, by the Intune roles Endpoint Security Manager and Policy and Profile Manager, and by an application with DeviceManagementConfiguration.ReadWrite.All. The rule reads the Intune audit log, which reaches a SIEM only after an Intune diagnostic setting (category AuditLogs) sends it to a Log Analytics workspace or an event hub. It does not cover a change of the tenant-wide setting, whose operation name Microsoft does not document.

What an attacker needs

  • Control of an identity with the Device compliance policies permissions in Intune, or an application with DeviceManagementConfiguration.ReadWrite.All.
  • A Conditional Access policy that relies on the compliant device state, and a device or stolen session the attacker wants to get through it.
  • No Multi Admin Approval access policy for compliance policies, or a second compromised approver.

Impact

The compliant device requirement stops meaning what the organization thinks it means. Devices that are unencrypted, unpatched or flagged by Defender keep their access, and a device enrolled by the attacker can satisfy policies that protect administrator portals and sensitive applications.

Detection rules

Intune Compliance Policy Changed or Deleted

Detects a successful update or deletion of an Intune device compliance policy in the Intune audit log. Microsoft does not publish the list of OperationName values, so the rule matches the text CompliancePolicy inside the name (the Microsoft Graph resource types deviceCompliancePolicy and deviceManagementCompliancePolicy) and leaves out the creation of new policies and assignments. Confirmed from the sample events of Splunk Threat Research: a name is an action followed by a Graph resource type, for example Patch DeviceManagementConfigurationPolicy. Inferred: that compliance policy events carry these resource type names; no Microsoft or Splunk sample shows one, so confirm the names in your tenant. The rule cannot tell a weakening from a tightening; compare the old and new values. A change of the tenant-wide compliance policy settings is not covered.

LevelMediumStatusExperimentalLog sourceMicrosoft Intune audit logs
title: Intune Compliance Policy Changed or Deleted
id: 121e6834-61ff-4b72-9ded-dbf499b584e0
status: experimental
description: >-
  Detects a successful update or deletion of an Intune device compliance policy
  in the Intune audit log. Microsoft does not publish the list of OperationName
  values, so the rule matches the text CompliancePolicy inside the name (the
  Microsoft Graph resource types deviceCompliancePolicy and
  deviceManagementCompliancePolicy) and leaves out the creation of new policies
  and assignments. Confirmed from the sample events of Splunk Threat Research:
  a name is an action followed by a Graph resource type, for example Patch
  DeviceManagementConfigurationPolicy. Inferred: that compliance policy events
  carry these resource type names; no Microsoft or Splunk sample shows one, so
  confirm the names in your tenant. The rule cannot tell a weakening from a
  tightening; compare
  the old and new values. A change of the tenant-wide compliance policy
  settings is not covered.
references:
  - https://attack.mitre.org/techniques/T1484/
  - https://learn.microsoft.com/en-us/intune/device-security/compliance/overview
  - https://learn.microsoft.com/en-us/intune/governance/integrate-azure-monitor
  - https://research.splunk.com/cloud/3c49e5ed-625c-408c-a2c7-8e2b524efb2c/
author: Forestall
date: 2026-11-11
tags:
  - attack.defense-impairment
  - attack.privilege-escalation
  - attack.t1484
logsource:
  product: intune
  service: audit
detection:
  selection:
    OperationName|contains: CompliancePolicy
    ResultType: Success
  filter_create:
    OperationName|startswith: Create
  condition: selection and not filter_create
falsepositives:
  - Routine maintenance of compliance policies, for example raising the minimum operating system version; confirm a change record.
  - Tenants that manage compliance policies from a pipeline should filter its identity by Identity.
level: medium

False positives

  • Routine maintenance of compliance policies, for example raising the minimum operating system version; confirm a change record.
  • Tenants that manage compliance policies from a pipeline should filter its identity by Identity.

Triage

  • Identify the actor (Identity, and Actor in Properties) and the policy (TargetDisplayNames in Properties).
  • Compare the old and new values in the modified properties under Properties.Targets, or open the policy in the admin center, and decide whether the change weakens a requirement.
  • For a deletion, check the tenant-wide setting for devices with no compliance policy and which devices lost their only policy.
  • Review sign-ins that satisfied a compliant device requirement after the change, especially from recently enrolled devices and for privileged users.

Response

Once the attack is confirmed:

  1. Contain the actor. Revoke the sessions of the account, or disable the application and remove its credentials, and remove its Device compliance policies permissions.
  2. Restore the policy and its assignments to the approved configuration, or create the deleted policy again. Check the tenant-wide compliance policy settings by hand, because the rule does not cover a change there.
  3. List the devices that became compliant or were enrolled while the policy was weakened. Remove the devices that are not yours from Intune and from Microsoft Entra ID.
  4. Revoke the sessions of the users who signed in from those devices during that period, privileged users first, and review what those sessions accessed.
  5. After the restore, confirm in the compliance reports that devices which do not meet the requirements are shown as not compliant again.

Mitigation

  • Set Mark devices with no compliance policy assigned as to Not compliant, as Microsoft recommends for tenants that use Conditional Access with device compliance.
  • Create a Multi Admin Approval access policy for Compliance policies.
  • Limit the Device compliance policies permissions to a small team, scoped with scope tags.
  • Do not rely on device compliance alone for privileged access; also require phishing-resistant authentication.

Frequently asked questions

Can the rule tell whether a change weakened or tightened the policy?

No. It matches every successful update or deletion of a compliance policy. Compare the old and new values in the modified properties of the event, or open the policy in the admin center, and decide whether a requirement was removed or a grace period was lengthened.

Why does deleting a compliance policy make devices compliant?

The tenant-wide setting Mark devices with no compliance policy assigned as is set to Compliant by default. Where that default is still in place, deleting a policy or its assignment turns every device it covered into a compliant one. Microsoft recommends Not compliant for tenants that use Conditional Access with device compliance.

Does the rule see a change of the tenant-wide compliance policy settings?

No. Microsoft does not document the operation name of that change, so the rule does not cover it. Check the setting by hand after any incident that involves an identity with compliance policy permissions, and during regular reviews.

Why are there no Intune audit events in our SIEM?

The Intune audit log reaches a SIEM only after an Intune diagnostic setting with the category AuditLogs sends it to a Log Analytics workspace or an event hub. Without that setting the rule has nothing to read. The events are still visible in the Intune admin center.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.