> 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-application-setup-policy-was-modified.md).

# Microsoft Teams application setup policy was modified

### 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       | Persistence (TA0003), Defense Impairment (TA0112)                      |
| ATT\&CK Technique    | Disable or Modify Tools (T1685), Cloud Application Integration (T1671) |
| Severity             | Informational                                                          |

### Description

Microsoft Teams the application setup policy, which is responsible for application management, was modified.

### Attacker's Goals

Attackers may modify the application setup policy to maintain persistent access to compromised Teams accounts and conversations.

### Investigative actions

* Determine if it is within the user's role to modify the policy.
* Verify whether the modification of the policy is both legitimate and necessary.
* If the policy change causes an application installed for the whole organization, confirm that the application was created by a certified and trusted entity.
* Correlate the event with its sign-in event to get additional information on the identity performing the action using the session ID or the unique token identifier.

### Variations

<details>

<summary>A user changed the Microsoft Teams application setup policy for the first time</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Defense Impairment (TA0112)                      |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Cloud Application Integration (T1671) |
| Severity          | Low                                                                    |

**Description**

Microsoft Teams the application setup policy, which is responsible for application management, was modified.

**Attacker's Goals**

Attackers may modify the application setup policy to maintain persistent access to compromised Teams accounts and conversations.

**Investigative actions**

* Determine if it is within the user's role to modify the policy.
* Verify whether the modification of the policy is both legitimate and necessary.
* If the policy change causes an application installed for the whole organization, confirm that the application was created by a certified and trusted entity.
* Correlate the event with its sign-in event to get additional information on the identity performing the action using the session ID or the unique token identifier.

</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/microsoft-teams-application-setup-policy-was-modified.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.