> 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-started-a-microsoft-teams-conversation.md).

# External user started a Microsoft Teams conversation

### Synopsis

| Field                | Value                   |
| -------------------- | ----------------------- |
| Activation Period    | 14 Days                 |
| Training Period      | 30 Days                 |
| Test Period          | 1 Hour                  |
| Deduplication Period | 1 Day                   |
| Required Data        | Office 365 Audit        |
| Detection Modules    | Identity Threat Module  |
| Detector Tags        | Microsoft Teams         |
| ATT\&CK Tactic       | Initial Access (TA0001) |
| ATT\&CK Technique    | Phishing (T1566)        |
| Severity             | Informational           |

### Description

An external user started a Microsoft Teams conversation with users in the organization.

### 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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

### Variations

<details>

<summary>An external user started multiple conversations in Microsoft Teams with suspicious chat names</summary>

**Synopsis**

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

**Description**

An external user started a Microsoft Teams conversation with users in the organization.

**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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

</details>

<details>

<summary>An external user started a conversation in Microsoft Teams with a suspicious user or chat name</summary>

**Synopsis**

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

**Description**

An external user started a Microsoft Teams conversation with users in the organization.

**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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

</details>

<details>

<summary>An external user started multiple conversations in Microsoft Teams</summary>

**Synopsis**

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

**Description**

An external user started a Microsoft Teams conversation with users in the organization.

**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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

</details>

<details>

<summary>External user started a Microsoft Teams conversation and sent a message</summary>

**Synopsis**

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

**Description**

An external user started a Microsoft Teams conversation with users in the organization.

**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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check external domain reputation.
* Review past communication from the external user.
* Follow further actions done by the account.

</details>

<details>

<summary>An external user started conversations in Microsoft Teams with many internal users</summary>

**Synopsis**

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

**Description**

An external user started a Microsoft Teams conversation with users in the organization.

**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 tenant and user are authorized to start a conversation 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 might have been sent in the conversation.
* Check 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 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/external-user-started-a-microsoft-teams-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.
