> 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-365-dlp-policy-disabled-or-removed.md).
# Microsoft 365 DLP policy disabled or removed
### 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, Email |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685) |
| Severity | Informational |
### Description
A user disabled or removed a Microsoft 365 data loss prevention (DLP) policy, which may indicate DLP monitoring evasion.
### Attacker's Goals
An attacker is attempting to bypass Microsoft 365 Data Loss Prevention (DLP) policies.
### Investigative actions
* Follow further actions done by the account.
* Verify that the configuration change was expected.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Monitor the user's activity for any access to sensitive data or data exfiltration.
* Investigate if any other security policies have been changed or removed.
### Variations
Rare Microsoft 365 DLP policy removal
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685) |
| Severity | Low |
**Description**
A user disabled or removed a Microsoft 365 data loss prevention (DLP) policy, which may indicate DLP monitoring evasion.
**Attacker's Goals**
An attacker is attempting to bypass Microsoft 365 Data Loss Prevention (DLP) policies.
**Investigative actions**
* Follow further actions done by the account.
* Verify that the configuration change was expected.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Monitor the user's activity for any access to sensitive data or data exfiltration.
* Investigate if any other security policies have been changed or removed.
---
# 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-365-dlp-policy-disabled-or-removed.md?ask=&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.