> For the complete documentation index, see [llms.txt](https://msdocs.aohwv.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://msdocs.aohwv.com/quick-start/step-6-purview.md).

# Step 6 — Purview

Microsoft Purview protects sensitive data. Its **data loss prevention (DLP)** policies flag when sensitive information, such as credit card numbers or confidential files, is shared or sent where it shouldn't be. Sending these events to your SIEM helps your SOC spot data theft.

{% hint style="info" %}
**Time:** about 10 minutes. There's no new connection to set up. Purview uses the same app registration as [**Step 4 — Microsoft 365**](/quick-start/step-4-microsoft-365.md).
{% endhint %}

### Before you start

* **Step 4 — Microsoft 365** is complete
* DLP policies set up in Purview. If you don't use DLP yet, skip this step for now

### 1. Add the DLP permission

1. In the [Microsoft Entra admin center](https://entra.microsoft.com), go to **App registrations** and open **siem-m365-audit** from Step 4.
2. Go to **API permissions** → **+ Add a permission**.
3. Select **Office 365 Management APIs** → **Application permissions**.
4. Under **ActivityFeed**, check **ActivityFeed.ReadDlp**.
5. Select **Add permissions**, then **Grant admin consent**.

### 2. Turn on DLP in your SIEM

In your SIEM's Microsoft 365 connector, add the **DLP.All** content type alongside the ones from Step 4.

{% hint style="warning" %}
**DLP events can include sensitive details,** such as part of the data that matched a policy. Make sure access to these events in your SIEM is limited to the SOC.
{% endhint %}

### What about Purview alerts?

**DLP alerts** (and **Insider Risk alerts**, if you use Insider Risk Management) can appear in **Defender XDR**, so they reach your SIEM through **Step 3**. Check that they show up there, so they aren't collected twice.

### What your SOC can detect with these logs

* Sensitive data emailed or shared outside the organization
* Files with confidential labels uploaded or copied where they shouldn't be
* Repeated DLP policy matches from one user, a sign of possible data theft

## Related

* [Step 4 — Microsoft 365](/quick-start/step-4-microsoft-365.md) — The app registration Purview uses
* [Step 7 — Azure](/quick-start/step-7-azure-defender-for-cloud.md) — Defender for Cloud and the Azure Activity Log
* [Get Extra Help](/get-expert-help/overview.md) -Need help setting up data loss prevention? RedLegg Advisory can help


---

# 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://msdocs.aohwv.com/quick-start/step-6-purview.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.