> 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 |
| Detector Tags | Microsoft Teams |
| ATT\&CK Tactic | Defense Evasion (TA0005), Persistence (TA0003) |
| ATT\&CK Technique | Impair Defenses (T1562), 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
A user changed the Microsoft Teams application setup policy for the first time
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005), Persistence (TA0003) |
| ATT\&CK Technique | Impair Defenses (T1562), 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.
---
# 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-application-setup-policy-was-modified.md?ask=&goal=
```
`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.