> 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-account-deletion-by-a-non-standard-account.md).

# Azure account deletion by a non-standard account

### Synopsis

| Field                | Value                          |
| -------------------- | ------------------------------ |
| Activation Period    | 14 Days                        |
| Training Period      | 30 Days                        |
| Test Period          | N/A (single event)             |
| Deduplication Period | 1 Day                          |
| Required Data        | AzureAD Audit Log              |
| Detection Modules    | Identity Threat Module         |
| ATT\&CK Tactic       | Impact (TA0040)                |
| ATT\&CK Technique    | Account Access Removal (T1531) |
| Severity             | Low                            |

### Description

An Azure AD account deletion was performed by a user that doesn't typically delete users.

### Attacker's Goals

Interrupt availability and access to Azure by deleting access accounts.

### Investigative actions

* Follow further actions by the initiator.
* Check what services, groups and applications are affected by the deleted user being removed.
* Check if the deleted user had a privileged role.

### Variations

<details>

<summary>Azure account deletion by a non-standard account with high administrative activity</summary>

**Synopsis**

| Field             | Value                          |
| ----------------- | ------------------------------ |
| ATT\&CK Tactic    | Impact (TA0040)                |
| ATT\&CK Technique | Account Access Removal (T1531) |
| Severity          | Informational                  |

**Description**

An Azure AD account deletion was performed by an identity with high administrative activity that doesn't typically delete users.

**Attacker's Goals**

Interrupt availability and access to Azure by deleting access accounts.

**Investigative actions**

* Follow further actions by the initiator.
* Check what services, groups and applications are affected by the deleted user being removed.
* Check if the deleted user had a privileged role.

</details>

<details>

<summary>A suspicious Azure account deletion by a non-standard account</summary>

**Synopsis**

| Field             | Value                          |
| ----------------- | ------------------------------ |
| ATT\&CK Tactic    | Impact (TA0040)                |
| ATT\&CK Technique | Account Access Removal (T1531) |
| Severity          | Medium                         |

**Description**

An Azure AD account deletion was performed by a user that doesn't typically delete users in a suspicious manner.

**Attacker's Goals**

Interrupt availability and access to Azure by deleting access accounts.

**Investigative actions**

* Follow further actions by the initiator.
* Check what services, groups and applications are affected by the deleted user being removed.
* Check if the deleted user had a privileged role.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-account-deletion-by-a-non-standard-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
