> 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-application-consent.md).
# Azure application consent
### 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 | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Phishing (T1566), Phishing: Spearphishing Link (T1566.002), Steal Application Access Token (T1528), Trusted Relationship (T1199) |
| Severity | Informational |
### Description
An identity consented permissions to an application.
### Attacker's Goals
Get access to credentials, data or an organization via applications with sufficient permissions.
### Investigative actions
* Follow further actions by the consenting user.
* Check for new resource creations by the new user.
* Check how the consenting user got to the application.
* Verify the application creators.
* Check what permissions the application requested.
* Check for possible phishing in the organization.
### Variations
First seen Azure admin consent to an application
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Phishing (T1566), Phishing: Spearphishing Link (T1566.002), Steal Application Access Token (T1528), Trusted Relationship (T1199) |
| Severity | Low |
**Description**
An administrative identity consented permissions to an application.
**Attacker's Goals**
Get access to credentials, data or an organization via applications with sufficient permissions.
**Investigative actions**
* Follow further actions by the consenting user.
* Check for new resource creations by the new user.
* Check how the consenting user got to the application.
* Verify the application creators.
* Check what permissions the application requested.
* Check for possible phishing in the organization.
---
# 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-application-consent.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.