> 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/microsoft-teams-messages-were-exported-from-conversation.md).

# Microsoft Teams messages were exported from conversation

### Synopsis

| Field                | Value                                                                  |
| -------------------- | ---------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                |
| Training Period      | 30 Days                                                                |
| Test Period          | N/A (single event)                                                     |
| Deduplication Period | 1 Day                                                                  |
| Required Data        | Office 365 Audit                                                       |
| Detection Modules    | Identity Threat Module                                                 |
| Detector Tags        | Microsoft Teams                                                        |
| ATT\&CK Tactic       | Collection (TA0009)                                                    |
| ATT\&CK Technique    | Data from Information Repositories: Messaging Applications (T1213.005) |
| Severity             | Informational                                                          |

### Description

Microsoft Teams messages were exported from conversation.

### Attacker's Goals

Attackers may leverage message extraction from Microsoft Teams to obtain valuable information.

### Investigative actions

* Confirm that the exported messages were extracted from a certified and trusted entity.
* Determine if it is within the user's role to extract messages from Microsoft Teams.
* Follow further actions done by the account and validate that the exported conversations were not sent to an untrusted entity.

### Variations

<details>

<summary>Microsoft Teams messages were exported from conversation by a privileged user for the first time</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Collection (TA0009)                                                    |
| ATT\&CK Technique | Data from Information Repositories: Messaging Applications (T1213.005) |
| Severity          | Low                                                                    |

**Description**

Microsoft Teams messages were exported from conversation.

**Attacker's Goals**

Attackers may leverage message extraction from Microsoft Teams to obtain valuable information.

**Investigative actions**

* Confirm that the exported messages were extracted from a certified and trusted entity.
* Determine if it is within the user's role to extract messages from Microsoft Teams.
* Follow further actions done by the account and validate that the exported conversations were not sent to an untrusted entity.

</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/microsoft-teams-messages-were-exported-from-conversation.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.
