> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-monitor-alert-rule-deleted.md).
# Azure Monitor alert rule deleted
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Azure Audit Log |
| Detection Modules | Cloud |
| Detector Tags | Cloud Log Tampering Analytics |
| ATT\&CK Tactic | Execution (TA0002), Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Informational |
### Description
An Azure Monitor alert rule was deleted. Azure Monitor alert rules watch telemetry from cloud resources and fire when suspicious or anomalous activity occurs. Adversaries may delete these rules to blind defenders and avoid detection of follow-on malicious activity.
### Attacker's Goals
* Blind defenders by removing alerts that watch for suspicious cloud activity.
* Avoid detection of subsequent operations such as data exfiltration, lateral movement, or persistence.
### Investigative actions
* Identify which alert rule was deleted (metric, scheduled query, or activity-log alert) and what it was watching.
* Verify whether the identity that performed the deletion is authorized to manage Azure Monitor alert rules.
* Check the Azure Activity Log for the caller's other recent operations in the subscription / resource group.
* Look for correlated suspicious activity such as resource modifications, role assignments, or diagnostic-settings changes that would normally have been alerted on.
* Re-create the alert rule (or restore from infrastructure-as-code) to re-establish monitoring coverage.
### Variations
Unusual Azure Monitor alert rule deletion
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Low |
**Description**
An Azure Monitor alert rule was deleted. Azure Monitor alert rules watch telemetry from cloud resources and fire when suspicious or anomalous activity occurs. Adversaries may delete these rules to blind defenders and avoid detection of follow-on malicious activity.
**Attacker's Goals**
* Blind defenders by removing alerts that watch for suspicious cloud activity.
* Avoid detection of subsequent operations such as data exfiltration, lateral movement, or persistence.
**Investigative actions**
* Identify which alert rule was deleted (metric, scheduled query, or activity-log alert) and what it was watching.
* Verify whether the identity that performed the deletion is authorized to manage Azure Monitor alert rules.
* Check the Azure Activity Log for the caller's other recent operations in the subscription / resource group.
* Look for correlated suspicious activity such as resource modifications, role assignments, or diagnostic-settings changes that would normally have been alerted on.
* Re-create the alert rule (or restore from infrastructure-as-code) to re-establish monitoring coverage.
Azure Monitor alert rule deleted by compute workload
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Low |
**Description**
An Azure Monitor alert rule was deleted. Azure Monitor alert rules watch telemetry from cloud resources and fire when suspicious or anomalous activity occurs. Adversaries may delete these rules to blind defenders and avoid detection of follow-on malicious activity.
**Attacker's Goals**
* Blind defenders by removing alerts that watch for suspicious cloud activity.
* Avoid detection of subsequent operations such as data exfiltration, lateral movement, or persistence.
**Investigative actions**
* Identify which alert rule was deleted (metric, scheduled query, or activity-log alert) and what it was watching.
* Verify whether the identity that performed the deletion is authorized to manage Azure Monitor alert rules.
* Check the Azure Activity Log for the caller's other recent operations in the subscription / resource group.
* Look for correlated suspicious activity such as resource modifications, role assignments, or diagnostic-settings changes that would normally have been alerted on.
* Re-create the alert rule (or restore from infrastructure-as-code) to re-establish monitoring coverage.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-monitor-alert-rule-deleted.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.