> 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/mailbox-enumeration-activity-by-azure-application.md).
# Mailbox enumeration activity by Azure application
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 10 Minutes |
| Deduplication Period | 5 Days |
| Required Data | Requires one of the following data sources:
Azure Audit Log OR Microsoft Graph Logs
|
| Detection Modules | Cloud |
| Detector Tags | Microsoft Graph Activity Logs |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Cloud Service Discovery (T1526) |
| Severity | Informational |
### Description
Microsoft Graph API was used to enumerate mailboxes in Azure tenant.
### Attacker's Goals
To extract sensitive information stored in mailboxes.
### Investigative actions
* Determine which mailboxes were enumerated and whether they contained any sensitive information.
* Investigate the identity following actions.
### Variations
Mailbox enumeration activity by Azure user
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Cloud Service Discovery (T1526) |
| Severity | Informational |
**Description**
Microsoft Graph API was used by a user to enumerate mailboxes.
**Attacker's Goals**
To extract sensitive information stored in mailboxes.
**Investigative actions**
* Determine which mailboxes were enumerated and whether they contained any sensitive information.
* Investigate the identity following actions.
---
# 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/mailbox-enumeration-activity-by-azure-application.md?ask=&goal=
```
`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.