1. Resources
  2. Detection rules
  3. Defender for Cloud Alert Suppression Rule Created or Changed

Defender for Cloud Alert Suppression Rule Created or Changed detection rules

Someone creates or edits an alert suppression rule in Microsoft Defender for Cloud, so that matching security alerts are dismissed automatically and notify no one. The activity that would have raised them stays unseen.

Platform
Azure
Severity
Medium
Log source
Azure Activity log
Last updated
MITRE ATT&CK technique
T1685Disable or Modify Tools
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
A role with Microsoft.Security/alertsSuppressionRules/write on the subscription, for which Microsoft names Security Admin and Owner.
Impact
Alerts that match the rule are dismissed as they arrive and notify no one, so activity that Defender for Cloud detected goes unanswered.
Response
Disable or delete the rule, review every alert it dismissed as if it were active, and remove the caller's Security Admin or Owner role.
Mitigation
Limit Security Admin and Owner on subscriptions, require an expiry date on suppression rules, and review the rules and the dismissed alerts on a schedule.
Operation
MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE

How the attack works

Microsoft Defender for Cloud raises security alerts when it detects threats to resources in a subscription. A suppression rule dismisses alerts automatically when they match its conditions: specific alert types or all of them, optionally limited to certain entities, on the subscriptions the rule applies to, until an optional expiry date. Microsoft documents that a matching alert gets the status Dismissed. It still appears in the security alerts list, but it no longer triggers notifications or appears in active alert views. The feature is meant for alerts that are expected or not relevant.

An attacker who holds Security Admin or Owner on a subscription uses the same feature to silence the alerts their next steps would raise, without turning off a Defender plan and without deleting anything. The rule is written with Microsoft.Security/alertsSuppressionRules/write, a control-plane request recorded in the Azure Activity log with its caller. The event shows that a suppression rule was created or updated, not which alerts it dismisses, so the rule itself has to be read.

What an attacker needs

  • Microsoft.Security/alertsSuppressionRules/write on the subscription. Microsoft names Security Admin and Owner as the roles that can create and delete suppression rules.

Impact

Alerts that match the rule are dismissed as they arrive, on every subscription the rule covers and for as long as it stays active. Nobody is notified, and activity that Defender for Cloud detected goes unanswered. A rule that covers all alert types and has no expiry date keeps dismissing them indefinitely.

Detection rules

Defender for Cloud Alert Suppression Rule Created or Updated

Detects a successful create or update of an alert suppression rule in Microsoft Defender for Cloud (Microsoft.Security/alertsSuppressionRules/write). Alerts that match an active suppression rule are dismissed automatically and no longer trigger notifications. The event does not say which alert types the rule covers, so read the rule in Defender for Cloud or through the REST API.

LevelMediumStatusExperimentalLog sourceAzure Activity log
title: Defender for Cloud Alert Suppression Rule Created or Updated
id: c8c957a3-5346-450f-8350-ddaef82adba2
status: experimental
description: >-
  Detects a successful create or update of an alert suppression rule in
  Microsoft Defender for Cloud
  (Microsoft.Security/alertsSuppressionRules/write). Alerts that match an
  active suppression rule are dismissed automatically and no longer trigger
  notifications. The event does not say which alert types the rule covers, so
  read the rule in Defender for Cloud or through the REST API.
references:
  - https://attack.mitre.org/techniques/T1685/
  - https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-suppression-rules
  - https://learn.microsoft.com/en-us/azure/role-based-access-control/permissions/security
author: Forestall
date: 2026-11-16
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    OperationNameValue: MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE
    ActivityStatusValue:
      - Success
      - Succeeded
  condition: selection
falsepositives:
  - Security teams that suppress alerts for known benign activity, such as penetration tests or expected administrative tooling. Match each event to a request, and check that the rule is limited to specific alert types and entities and has an expiry date.
  - Suppression rules deployed to many subscriptions by a central identity. Exclude that identity in a filter_ selection by Caller once confirmed.
level: medium

False positives

  • Security teams that suppress alerts for known benign activity, such as penetration tests or expected administrative tooling. Match each event to a request, and check that the rule is limited to specific alert types and entities and has an expiry date.
  • Suppression rules deployed to many subscriptions by a central identity. Exclude that identity in a filter_ selection by Caller once confirmed.

Triage

  • Identify the Caller and the subscription, and check whether this identity normally maintains Defender for Cloud and whether a request explains the change.
  • Open the rule under Security alerts, Suppression rules in Defender for Cloud, or read it with the REST API. Look at the alert types, the entity conditions, the state, the reason, the comment and the expiry date. A rule for all alert types, without entity conditions or without an expiry date, needs a strong justification.
  • List the alerts that were dismissed since the rule was written and judge them as if they were active.
  • Review the caller's other activity around that time, in particular on the resources that the suppressed alert types concern.

Response

Once the attack is confirmed:

  1. Disable or delete the rule. Deleting it does not change the status of the alerts it already dismissed, so list those alerts and work through them as active alerts.
  2. Contain the caller. Revoke its sessions, rotate its credentials and remove its Security Admin or Owner role until the change is explained.
  3. Investigate the resources and entities named in the rule's conditions and in the dismissed alerts. They show where the attacker expected to be detected.
  4. Check the other Defender for Cloud settings that the same role can change on the affected subscriptions, such as other suppression rules, the enabled Defender plans and the alert notification settings.
  5. Look in every other subscription the caller can reach for suppression rules it wrote or rules with the same conditions.

Mitigation

  • Limit Security Admin and Owner on subscriptions and assign them through Privileged Identity Management, so that changing Defender for Cloud settings needs an elevation.
  • Review the suppression rules of every subscription on a schedule. Check the alert types, the entity conditions, the reason and the comment, and require an expiry date.
  • Review dismissed alerts as well as active ones. A suppressed alert still appears in the security alerts list with the status Dismissed.
  • Send the Azure Activity log to your SIEM, alert on every write of a suppression rule and match each one to a request.

Frequently asked questions

Does an alert disappear when a suppression rule matches it?

No. Microsoft documents that the alert's status changes to Dismissed. The alert still appears in the security alerts list, but it no longer triggers notifications or appears in active alert views. A review of dismissed alerts therefore shows what a suppression rule has hidden.

Does the detection show which alerts the new rule suppresses?

No. The rule on this page matches the operation and its outcome, which tell you that a suppression rule was created or updated, by whom and in which subscription. To see the alert types, the entity conditions and the expiry date, open the rule in Defender for Cloud or read it with the Alerts Suppression Rules REST API.

Does deleting a malicious suppression rule bring the alerts back?

No. Microsoft documents that deleting a suppression rule does not change the status of alerts that the rule already dismissed. List the alerts that were dismissed while the rule was active and review each of them as if it had been raised normally.

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.