> 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-sent-messages-in-microsoft-teams-to-multiple-conversations-via-graph-api.md).

# User sent messages in Microsoft Teams to multiple conversations via Graph API

### Synopsis

| Field                | Value                          |
| -------------------- | ------------------------------ |
| Activation Period    | 14 Days                        |
| Training Period      | 30 Days                        |
| Test Period          | 1 Hour                         |
| Deduplication Period | 1 Day                          |
| Required Data        | Microsoft Graph Logs           |
| Detection Modules    | Identity Threat Module         |
| Detector Tags        | Microsoft Teams                |
| ATT\&CK Tactic       | Lateral Movement (TA0008)      |
| ATT\&CK Technique    | Internal Spearphishing (T1534) |
| Severity             | Informational                  |

### Description

A user who rarely uses the Graph API for Microsoft Teams messaging sent multiple messages using it.

### Attacker's Goals

Attackers may leverage a compromised user account to send phishing or malicious messages via Graph API to multiple recipients, aiming to propagate the attack while evading detection.

### 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 sent messages in Microsoft Teams to several conversations via Graph API with suspicious characteristics</summary>

**Synopsis**

| Field             | Value                          |
| ----------------- | ------------------------------ |
| ATT\&CK Tactic    | Lateral Movement (TA0008)      |
| ATT\&CK Technique | Internal Spearphishing (T1534) |
| Severity          | Low                            |

**Description**

A user who rarely uses the Graph API for Microsoft Teams messaging sent multiple messages using it.

**Attacker's Goals**

Attackers may leverage a compromised user account to send phishing or malicious messages via Graph API to multiple recipients, aiming to propagate the attack while evading detection.

**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 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/user-sent-messages-in-microsoft-teams-to-multiple-conversations-via-graph-api.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.