> 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/unusual-resource-access-by-azure-application.md).

# Unusual resource access by Azure application

### Synopsis

| Field                | Value                                                                                         |
| -------------------- | --------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                       |
| Training Period      | 30 Days                                                                                       |
| Test Period          | N/A (single event)                                                                            |
| Deduplication Period | 5 Days                                                                                        |
| Required Data        | <p>Requires one of the following data sources:<br>Azure Audit Log OR Microsoft Graph Logs</p> |
| Detection Modules    | Cloud                                                                                         |
| Detector Tags        | Microsoft Graph Activity Logs                                                                 |
| ATT\&CK Tactic       | Discovery (TA0007)                                                                            |
| ATT\&CK Technique    | Cloud Service Discovery (T1526)                                                               |
| Severity             | Informational                                                                                 |

### Description

An Azure application had interacted with an unusual resource using the Microsoft Graph API.

### Attacker's Goals

Abuse applications to gain access to the Azure tenant.

### Investigative actions

* Verify whether the application is intended to use the resource in question.
* Investigate any unusual activity originating from the application.

### Variations

<details>

<summary>Suspicious resource access by Azure application</summary>

**Synopsis**

| Field             | Value                           |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic    | Discovery (TA0007)              |
| ATT\&CK Technique | Cloud Service Discovery (T1526) |
| Severity          | Low                             |

**Description**

An Azure application had interacted with an unusual resource using the Microsoft Graph API.

**Attacker's Goals**

Abuse applications to gain access to the Azure tenant.

**Investigative actions**

* Verify whether the application is intended to use the resource in question.
* Investigate any unusual activity originating from the application.

</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/unusual-resource-access-by-azure-application.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.
