1. Resources
  2. Detection rules
  3. Defender for Cloud Plans, Notifications or Export Changed

Defender for Cloud Plans, Notifications or Export Changed detection rules

Someone changes a Microsoft Defender for Cloud plan, removes the security contact or deletes an automation or connector. Detection for the subscription stops, or alerts are still raised but no longer reach anyone.

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
Security Admin, Contributor or Owner on the subscription, or a custom role with the write and delete actions of the Microsoft.Security resource provider.
Impact
Threat detection for the subscription stops, or its alerts no longer reach the people and systems that would act on them.
Response
Restore the plan, the security contact and the deleted automations, contain the caller and review the period in which detection was reduced.
Mitigation
Enforce Defender plans and the security contact with Azure Policy at management group scope and limit the roles that can change them.
Operations
MICROSOFT.SECURITY/PRICINGS/WRITEMICROSOFT.SECURITY/PRICINGS/ACTIONMICROSOFT.SECURITY/PRICINGS/DELETEMICROSOFT.SECURITY/DEFENDERFORSTORAGESETTINGS/WRITEMICROSOFT.SECURITY/DEFENDERFORSTORAGESETTINGS/DELETEMICROSOFT.SECURITY/ADVANCEDTHREATPROTECTIONSETTINGS/WRITEMICROSOFT.SECURITY/SECURITYCONTACTS/DELETEMICROSOFT.SECURITY/AUTOMATIONS/DELETEMICROSOFT.SECURITY/SECURITYCONNECTORS/DELETEMICROSOFT.SECURITY/SECURITYCONTACTS/WRITEMICROSOFT.SECURITY/AUTOMATIONS/WRITEMICROSOFT.SECURITY/SETTINGS/WRITE

How the attack works

Microsoft Defender for Cloud protects a subscription through settings that are themselves Azure resources. The Defender plans are pricing configurations (Microsoft.Security/pricings): Microsoft documents two tiers, free and standard, and the tier says whether the plan is enabled on the scope. The security contact (Microsoft.Security/securityContacts) holds who is emailed about alerts and from which severity. Automations (Microsoft.Security/automations) send alerts and recommendations on, to a logic app, an event hub or a Log Analytics workspace. Security connectors link other clouds and DevOps platforms to Defender for Cloud, and a further group of settings switches integrations such as the one with Microsoft Defender for Endpoint.

An attacker who expects to trip a detection changes these settings first, and each change is quieter than disabling a security tool on a server. Setting a plan to the free tier ends its threat detection for the scope. Removing the security contact or raising its severity threshold leaves alerts unread. Deleting an automation cuts the path that carries alerts to the SIEM or to the ticketing workflow. Microsoft documents that Security Admin, Contributor and Owner can enable and disable Defender plans. All of these are write and delete operations recorded in the Azure Activity log with their caller. The log does not hold the new values: an update of a plan looks the same whether the plan was switched on or off.

What an attacker needs

  • Security Admin, Contributor or Owner on the subscription, the roles that Microsoft lists for enabling and disabling Defender plans and for managing email notifications, or a custom role with the Microsoft.Security write and delete actions.

Impact

Threat detection for the affected resource types stops, or its alerts no longer reach the people and systems that act on them. The attacker's later steps in the subscription, such as credential access or data theft, then go unreported by a control the organization believes is in place.

Detection rules

Defender for Cloud Plan Changed

Detects a successful update or deletion of a Microsoft Defender for Cloud pricing configuration (Microsoft.Security/pricings/write, the batch update pricings/action and pricings/delete), or of the Defender for Storage and Advanced Threat Protection settings of a single resource. The pricing tier decides whether a Defender plan is enabled on the scope, so a change to the free tier ends the threat detection of that plan. The rule matches on the event only. Microsoft does not document that the new tier is part of the Activity log record, so the rule cannot tell a plan that was switched off from one that was switched on, and its level is lower for that reason. Plan changes are rare in most subscriptions, so read the plan after each event.

LevelLowStatusExperimentalLog sourceAzure Activity log
title: Defender for Cloud Plan Changed
id: 48a340e4-4ed6-4e6c-b45d-856912f8ccd6
status: experimental
description: >-
  Detects a successful update or deletion of a Microsoft Defender for Cloud
  pricing configuration (Microsoft.Security/pricings/write, the batch update
  pricings/action and pricings/delete), or of the Defender for Storage and
  Advanced Threat Protection settings of a single resource. The pricing tier
  decides whether a Defender plan is enabled on the scope, so a change to the
  free tier ends the threat detection of that plan. The rule matches on the
  event only. Microsoft does not document that the new tier is part of the
  Activity log record, so the rule cannot tell a plan that was switched off
  from one that was switched on, and its level is lower for that reason.
  Plan changes are rare in most subscriptions, so read the plan after each
  event.
references:
  - https://attack.mitre.org/techniques/T1685/
  - https://learn.microsoft.com/en-us/rest/api/defenderforcloud/pricings/update
  - https://learn.microsoft.com/en-us/azure/defender-for-cloud/permissions
  - https://learn.microsoft.com/en-us/azure/role-based-access-control/permissions/security
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    OperationNameValue:
      - MICROSOFT.SECURITY/PRICINGS/WRITE
      - MICROSOFT.SECURITY/PRICINGS/ACTION
      - MICROSOFT.SECURITY/PRICINGS/DELETE
      - MICROSOFT.SECURITY/DEFENDERFORSTORAGESETTINGS/WRITE
      - MICROSOFT.SECURITY/DEFENDERFORSTORAGESETTINGS/DELETE
      - MICROSOFT.SECURITY/ADVANCEDTHREATPROTECTIONSETTINGS/WRITE
    ActivityStatusValue:
      - Success
      - Succeeded
  condition: selection
falsepositives:
  - Onboarding of new subscriptions, where plans are enabled, and planned changes of plan or sub-plan for cost reasons. Match each event to a request and read the pricing tier afterwards.
  - Azure Policy remediation and central deployment identities that set plans on many subscriptions. Exclude those identities in a filter_ selection by Caller once confirmed.
level: low

False positives

  • Onboarding of new subscriptions, where plans are enabled, and planned changes of plan or sub-plan for cost reasons. Match each event to a request and read the pricing tier afterwards.
  • Azure Policy remediation and central deployment identities that set plans on many subscriptions. Exclude those identities in a filter_ selection by Caller once confirmed.

Defender for Cloud Security Contact, Automation or Connector Deleted

Detects a successful deletion of the security contact of a subscription in Microsoft Defender for Cloud, of an automation, or of a security connector. The security contact defines who is emailed about alerts. An automation sends alerts and recommendations on to a logic app, an event hub or a Log Analytics workspace, so it is what carries them to a SIEM or a workflow. A security connector links another cloud or a DevOps platform to Defender for Cloud. After any of these deletions alerts may still be raised, but they no longer reach the people or systems that act on them, or a connected environment is no longer watched.

LevelMediumStatusExperimentalLog sourceAzure Activity log
title: Defender for Cloud Security Contact, Automation or Connector Deleted
id: 3f846816-e333-47a7-8b8d-cc44bc8c4848
status: experimental
description: >-
  Detects a successful deletion of the security contact of a subscription in
  Microsoft Defender for Cloud, of an automation, or of a security connector.
  The security contact defines who is emailed about alerts. An automation
  sends alerts and recommendations on to a logic app, an event hub or a Log
  Analytics workspace, so it is what carries them to a SIEM or a workflow. A
  security connector links another cloud or a DevOps platform to Defender for
  Cloud. After any of these deletions alerts may still be raised, but they no
  longer reach the people or systems that act on them, or a connected
  environment is no longer watched.
references:
  - https://attack.mitre.org/techniques/T1685/
  - https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications
  - https://learn.microsoft.com/en-us/rest/api/defenderforcloud/automations/create-or-update
  - https://learn.microsoft.com/en-us/azure/role-based-access-control/permissions/security
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    OperationNameValue:
      - MICROSOFT.SECURITY/SECURITYCONTACTS/DELETE
      - MICROSOFT.SECURITY/AUTOMATIONS/DELETE
      - MICROSOFT.SECURITY/SECURITYCONNECTORS/DELETE
    ActivityStatusValue:
      - Success
      - Succeeded
  condition: selection
falsepositives:
  - Replacement of an automation or a connector by a new one, and clean-up when a subscription or a connected environment is retired. Match each event to a request and check that a replacement exists.
level: medium

False positives

  • Replacement of an automation or a connector by a new one, and clean-up when a subscription or a connected environment is retired. Match each event to a request and check that a replacement exists.

Defender for Cloud Security Contact, Automation or Integration Settings Written

Detects a successful create or update of the security contact of a subscription in Microsoft Defender for Cloud, of an automation, or of the Defender for Cloud settings that switch integrations such as the one with Microsoft Defender for Endpoint. An update can remove recipients, raise the minimum severity for notifications, disable an automation or point it to another destination, or turn an integration off. The rule matches on the event only, because Microsoft does not document that the new values are part of the Activity log record, so it also fires when a setting is created or improved. Use it for review of unexpected callers and read the setting after each event.

LevelLowStatusExperimentalLog sourceAzure Activity log
title: Defender for Cloud Security Contact, Automation or Integration Settings Written
id: d36566d3-db72-4f08-aedb-347de3bbe4cf
status: experimental
description: >-
  Detects a successful create or update of the security contact of a
  subscription in Microsoft Defender for Cloud, of an automation, or of the
  Defender for Cloud settings that switch integrations such as the one with
  Microsoft Defender for Endpoint. An update can remove recipients, raise the
  minimum severity for notifications, disable an automation or point it to
  another destination, or turn an integration off. The rule matches on the
  event only, because Microsoft does not document that the new values are
  part of the Activity log record, so it also fires when a setting is
  created or improved. Use it for review of unexpected callers and read the
  setting after each event.
references:
  - https://attack.mitre.org/techniques/T1685/
  - https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-email-notifications
  - https://learn.microsoft.com/en-us/rest/api/defenderforcloud/automations/create-or-update
  - https://learn.microsoft.com/en-us/rest/api/defenderforcloud/settings/update
  - https://learn.microsoft.com/en-us/azure/role-based-access-control/permissions/security
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    OperationNameValue:
      - MICROSOFT.SECURITY/SECURITYCONTACTS/WRITE
      - MICROSOFT.SECURITY/AUTOMATIONS/WRITE
      - MICROSOFT.SECURITY/SETTINGS/WRITE
    ActivityStatusValue:
      - Success
      - Succeeded
  condition: selection
falsepositives:
  - Security teams that set up or adjust notifications, exports and integrations, and onboarding of new subscriptions. Exclude the central deployment identity in a filter_ selection by Caller once confirmed.
  - Azure Policy remediation that deploys the export or the contact to subscriptions.
level: low

False positives

  • Security teams that set up or adjust notifications, exports and integrations, and onboarding of new subscriptions. Exclude the central deployment identity in a filter_ selection by Caller once confirmed.
  • Azure Policy remediation that deploys the export or the contact to subscriptions.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Defender plan written and its pricing tier lower than in the last inventory

Detection hypothesisCompares with an earlier value

The write event does not say whether a plan was enabled or disabled. Comparing the tier after the write with the tier recorded before it turns a routine event into a clear one: a plan that was Standard and is now Free was switched off.

  1. Keep a daily inventory of the Defender plans of every subscription with the pricingTier and subPlan of each plan, read from the pricings of the subscription.
  2. In the Azure Activity log, a plan is written or deleted with status Success: MICROSOFT.SECURITY/PRICINGS/WRITE or MICROSOFT.SECURITY/PRICINGS/DELETE. Take the subscription and the plan name from the resource ID.
  3. Read the plan again and compare it with the inventory. Alert when pricingTier went from Standard to Free, or when the sub-plan was reduced.

EventsMICROSOFT.SECURITY/PRICINGS/WRITEMICROSOFT.SECURITY/PRICINGS/DELETE

LimitsIt needs an inventory job and read access to every subscription. A plan that is switched off and on again between two inventory runs is only seen through the events. Planned cost reductions look the same, so match the change with a request.

Triage

  • Identify the Caller, the caller's IP address and the setting from the resource ID of the event. The last segment of a pricing resource ID is the plan name.
  • Read the current value. For a plan, compare the pricing tier and the sub-plan with what your baseline says. For the security contact, read the recipients, the notified roles and the minimum severity.
  • For a deleted automation, find out where it sent alerts, and whether another export to the same destination exists.
  • Check for a change request, and whether the same caller changed other security settings, diagnostic settings or policy assignments in the same period.
  • Review what else the caller did in the subscription after the change, and which Defender alerts were raised for the subscription shortly before it.

Response

Once the attack is confirmed:

  1. Set the plan back to the standard tier, restore the security contact and create the deleted automations and connectors again.
  2. Contain the caller. Revoke its sessions, rotate its credentials and remove its role until the change is explained.
  3. Review the activity in the subscription for the period in which detection or notification was reduced, using the Activity log and the resource logs, because Defender for Cloud did not watch or did not report it.
  4. Review the Defender alerts that were raised but not delivered while the contact or the export was missing.
  5. Put the settings under Azure Policy, so that the same change is reverted or flagged next time.

Mitigation

  • Enforce the Defender plans and the security contact with Azure Policy at management group scope, so that a change in one subscription is reported as non-compliant and can be remediated.
  • Limit Security Admin, Contributor and Owner at subscription scope, and assign them through Privileged Identity Management.
  • Manage plans, contacts and automations from source control, so that a change outside the pipeline stands out.
  • Send the Azure Activity log of every subscription to a SIEM that does not depend on the Defender for Cloud export it is meant to watch.
  • Review the plan coverage of all subscriptions regularly, for example with the coverage workbook of Defender for Cloud.

Frequently asked questions

Does the Activity log show whether a Defender plan was switched on or off?

No. Microsoft does not document that the pricing tier is part of the Activity log record. The event names the operation, the caller and the plan in its resource ID. Read the plan afterwards. The pricingTier property is Free or Standard, and comparing it with a stored inventory of plan settings tells you the direction of the change.

Why does deleting a security contact matter if alerts are still raised?

An alert that nobody receives does not start a response. The security contact defines who is emailed about alerts and from which severity. With the contact removed, or with its threshold raised, Defender for Cloud still raises alerts in the portal, but the notification that brings a person to look at them is gone.

What are automations in Defender for Cloud?

An automation is a resource that reacts to alerts and recommendations of a scope. Its actions are a logic app, an event hub or a Log Analytics workspace, so it is the mechanism behind forwarding alerts to a workflow or to another system. Deleting it silently stops that forwarding, and the alerts stay in Defender for Cloud only.

Is there a public incident report for this technique?

No public incident report describes this at the audit event level as far as this page's sources go. Microsoft's alert reference for Resource Manager describes a Defender for Cloud alert for suspicious invocations of high-risk defense evasion operations, which shows that Microsoft treats changes to the security configuration of a subscription as a signal.

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.