> 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/external-user-added-a-link-to-a-microsoft-teams-chat.md).

# External user added a link to a Microsoft Teams chat

### 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, SaaS Threat Detection |
| Detector Tags        | Microsoft Teams                               |
| ATT\&CK Tactic       | Initial Access (TA0001)                       |
| ATT\&CK Technique    | Phishing (T1566)                              |
| Severity             | Informational                                 |

### Description

An external user added a link to a Microsoft Teams chat.

### Attacker's Goals

Attackers may leverage Microsoft Teams to conduct phishing attacks by exploiting trusted communication channels with users inside the organization.

### Investigative actions

* Confirm that the external tenant and user are authorized to share links or files with users in the organization.
* Verify the content of the conversation and validate that there is no phishing attempt being made.
* Inspect links and URLs that have been sent in the conversation.
* Evaluate the external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

### Variations

<details>

<summary>An external user sent a link via Microsoft Teams with suspicious parameters</summary>

**Synopsis**

| Field             | Value                   |
| ----------------- | ----------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566)        |
| Severity          | Low                     |

**Description**

An external user sent a link with suspicious parameters in a Microsoft Teams conversation.

**Attacker's Goals**

Attackers may leverage Microsoft Teams to conduct phishing attacks by exploiting trusted communication channels with users inside the organization.

**Investigative actions**

* Confirm that the external tenant and user are authorized to share links or files with users in the organization.
* Verify the content of the conversation and validate that there is no phishing attempt being made.
* Inspect links and URLs that have been sent in the conversation.
* Evaluate the external domain reputation.
* Review past communication from the external user.
* 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/external-user-added-a-link-to-a-microsoft-teams-chat.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.