> 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/user-installed-an-application-in-microsoft-teams-via-graph-api.md).

# User installed an application in Microsoft Teams via Graph API

### Synopsis

| Field                | Value                                         |
| -------------------- | --------------------------------------------- |
| Activation Period    | 14 Days                                       |
| Training Period      | 30 Days                                       |
| Test Period          | N/A (single event)                            |
| Deduplication Period | 1 Day                                         |
| Required Data        | Microsoft Graph Logs                          |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection |
| Detector Tags        | Microsoft Teams                               |
| ATT\&CK Tactic       | Persistence (TA0003)                          |
| ATT\&CK Technique    | Cloud Application Integration (T1671)         |
| Severity             | Informational                                 |

### Description

A user who rarely uses the Graph API to install Microsoft Teams applications has installed one using it.

### Attacker's Goals

Attackers may leverage Teams applications to maintain persistent access to compromised Teams accounts.

### Investigative actions

* Verify the user's role and typical usage of Microsoft Graph API.
* Check if the user's account has recently logged in from unusual locations or devices.
* Review recent email and chat activity to identify any phishing or suspicious messages sent.
* Examine the Graph API call logs to see what actions were performed and their timestamps.
* Correlate with endpoint logs to detect any malware or suspicious processes running on the user's device.
* Check for signs of account compromise, such as password changes or MFA bypass attempts.
* Follow further actions done by the account.

### Variations

<details>

<summary>User installed an application in Microsoft Teams via Graph API from a first seen ASN</summary>

**Synopsis**

| Field             | Value                                 |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                  |
| ATT\&CK Technique | Cloud Application Integration (T1671) |
| Severity          | Low                                   |

**Description**

A user who rarely uses the Graph API to install Microsoft Teams applications has installed one using it.

**Attacker's Goals**

Attackers may leverage Teams applications to maintain persistent access to compromised Teams accounts.

**Investigative actions**

* Verify the user's role and typical usage of Microsoft Graph API.
* Check if the user's account has recently logged in from unusual locations or devices.
* Review recent email and chat activity to identify any phishing or suspicious messages sent.
* Examine the Graph API call logs to see what actions were performed and their timestamps.
* Correlate with endpoint logs to detect any malware or suspicious processes running on the user's device.
* Check for signs of account compromise, such as password changes or MFA bypass attempts.
* Follow further actions done by the account.

</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 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/user-installed-an-application-in-microsoft-teams-via-graph-api.md?ask=<question>&goal=<user_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.