Study guide

17.1 DLP Policies for Microsoft 365 Workloads

Microsoft 365 Administrator Expert MS-102

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide

2 Tenant Setup, Domains & Org Settings

2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile

3 Service Health, Network & Software Updates

3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates

4 Adoption, Usage & Microsoft 365 Backup

4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup

5 Users, Contacts, Groups & Shared Mailboxes

5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes

6 Licensing & Bulk User Management

6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell

7 Roles, Admin Units & Privileged Identity Management

7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM

8 Identity Synchronization with Entra Connect

8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization

9 Authentication, SSPR & Password Protection

9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues

10 Identity Protection, Conditional Access & MFA

10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access

11 Defender XDR Posture, Incidents & Threat Intelligence

11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence

12 Defender for Office 365: Policies, Alerts & Investigation

12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats

13 Attack Simulation & Restricted Entities

13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users

14 Defender for Endpoint

14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard

15 Defender for Cloud Apps

15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery

16 Purview Information Protection & Data Lifecycle

16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer

17 Purview Data Loss Prevention

17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports

18 Final Review & Exam Strategy

18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps

17.1 DLP Policies for Microsoft 365 Workloads

Key Takeaways Explain This Topic AI

Microsoft Purview DLP policies protect sensitive information across Exchange Online, SharePoint Online, OneDrive, Teams, Power BI, and Microsoft 365 Copilot prompts and responses

DLP conditions evaluate sensitive information types (SITs), sensitivity labels, and keywords with configurable matching logic and minimum instance counts

Policy actions include audit-only, block with business-justification override, block without override, and Teams-specific encryption of messages containing sensitive content

A DLP policy runs in one of three modes: test with policy tips, test without notifications, or enforce immediately — Microsoft recommends starting in test-with-tips before enforcing

Microsoft 365 Copilot DLP protects both the prompt the user submits and the response Copilot returns from exposing sensitive content surfaced through groundings

Last updated: August 2026

Microsoft Purview Data Loss Prevention (DLP) is a compliance feature that identifies sensitive information across Microsoft 365 services and enforces rules that prevent it from being shared inappropriately. For the MS-102 administrator, DLP is a central Domain 4 skill: you must be able to configure policies that span Exchange Online, SharePoint Online, OneDrive for Business, Teams chat and channel messages, Power BI, and Microsoft 365 Copilot prompts and responses.

What DLP Protects

DLP policies scan content for sensitive information types (SITs) — built-in classifiers like U.S. Social Security Number, credit card number, or EU debit card number — and for sensitivity labels (such as Confidential or Highly Confidential) that you publish through Purview Information Protection. When a policy's conditions are met, the configured action fires: audit the event, show a policy tip, block the action, or block with a user override.

The supported workload locations for Microsoft 365 DLP are:

  • Workload What is scanned
  • Exchange Online Email messages and attachments (including transport rules integration)
  • SharePoint Online Site documents and lists
  • OneDrive for Business Files stored in user OneDrives
  • Teams chat & channel messages 1:1 chats, group chats, and channel posts
  • Power BI Datasets and reports in workspaces
  • Microsoft 365 Copilot Prompts submitted by users and responses returned by Copilot
  • Creating a DLP Policy in the Purview Compliance Portal

Author policies in the Microsoft Purview compliance portal under Data loss prevention → Policies → + Create policy . The wizard walks through five decision points.

Step 1 — Choose a Template or Start Custom

Templates pre-configure SITs and conditions for common regulatory regimes. Frequently used templates include:

  • U.S. Financial Data — U.S. PII, U.S. bank account, ABA routing numbers
  • HIPAA / U.S. Health Insurance Act — protected health information identifiers
  • GDPR / EU General Data Protection Regulation — EU national ID, passport, debit card numbers
  • Custom policy — start from scratch when no template fits
  • Step 2 — Select Workloads / Locations

Choose where the policy applies. You can scope to all instances of a workload or to specific include/exclude lists:

  • Exchange Online — all mailboxes, or include/exclude distribution groups
  • SharePoint Online — all sites, or include/exclude site URLs
  • OneDrive — all accounts, or include/exclude specific users
  • Teams chat and channel messages — all users, or include/exclude groups

Power BI — all workspaces, or include/exclude specific workspaces (Power BI DLP requires the workspace to be in a Premium capacity in supported configurations)

Microsoft 365 Copilot — prompts and responses, scoped to include/exclude users or groups

A single policy can cover multiple workloads, but each workload has its own configurable action set. For example, the same policy can block sharing a SharePoint file and encrypt a Teams message.

Conditions and Matching Logic

DLP conditions decide when a rule fires. A rule can combine:

Content contains — one or more SITs, sensitivity labels, or keyword dictionaries

Matching logic — Match any (any one of the listed SITs triggers) or Match all (every listed item must be present)

Minimum instance count — require at least N occurrences of a SIT before the rule fires (e.g., at least 5 credit card numbers), useful to avoid noise from a single identifier

  • SIT confidence level — High / Medium / Low — higher confidence reduces false positives
  • Document property / metadata conditions — file size, extension, sensitivity label applied

You can also chain conditions with AND/OR grouping, for example: content contains (SSN OR passport number) AND shared with (external recipients).

Actions, Notifications, and Overrides

When a rule matches, the policy can take one of the following actions:

  • Action Behavior
  • Audit only Logs the event to Activity explorer; no user impact

Block with override Blocks the action but allows the user to override with a business justification, which is logged

  • Block without override Hard blocks the action; the user cannot proceed
  • Restrict access / encrypt (Teams, Exchange) Encrypts the message or restricts external access

User notifications (policy tips) surface a banner in the M365 app — Outlook, SharePoint, OneDrive, or Teams — telling the user why content was flagged and what to do. A policy tip can include a link to your internal compliance training.

User overrides let a user bypass a block with a stated business justification. The override is captured in the alert and reviewed by compliance officers; override abuse is a common finding in DLP audits.

Policy Mode and Precedence

Every policy has a mode :

  • Test with policy tips — evaluates and shows tips but does not enforce; recommended first phase
  • Test without notifications — evaluates silently; useful for measuring match volume before informing users
  • Turn on immediately — enforces from the moment the policy is saved

When multiple policies match the same content, policy precedence applies. Within a single policy, rules are evaluated top-down; the first matching rule wins. Across policies, the more restrictive rule (block) generally prevails over the less restrictive (audit). Scope carefully — include/exclude users, groups, distribution lists, and site URLs to avoid overlap.

DLP for Teams, Power BI, and Microsoft 365 Copilot

Teams DLP inspects both 1:1 and group chats plus Teams channel messages. Because Teams content flows through the Exchange transport pipeline for compliance, Teams DLP requires Exchange Online mailboxes for all monitored users. Supported actions include blocking the message from being sent and encrypting the message in transit.

Power BI DLP scans datasets for sensitive data that has been modeled into tables. When a SIT is detected in a dataset, the policy can trigger alerts that let administrators remediate by relocating the dataset, applying sensitivity labels, or restricting workspace access.

Microsoft 365 Copilot DLP is the newest workload and is critical for AI governance. Copilot grounds responses in Microsoft 365 content (SharePoint files, emails, Teams chats, and other graph-grounded sources). Copilot DLP inspects both the prompt the user submits and the response Copilot returns , blocking sensitive content from being surfaced in the response or leaked through the prompt. This prevents, for example, a user asking Copilot to summarize a Confidential HR document and having the response exposed in a shared Teams channel.

Real-World Configuration Walkthrough

Suppose Contoso wants to prevent credit card numbers from leaking through Copilot prompts. The administrator:

  • Creates a custom DLP policy scoped to the Microsoft 365 Copilot location
  • Adds a condition: content contains Credit Card Number SIT, min instance count 1, high confidence

Sets the action to Block with override and enables a policy tip: "This prompt contains credit card information and has been blocked. Override with a business justification if sharing is approved."

Runs the policy in test with policy tips for two weeks, reviews match volume in Activity explorer, then switches to enforce

This is the canonical Microsoft-recommended rollout pattern: test, measure, tune, enforce.

Key Takeaways

DLP policies protect six Microsoft 365 workloads: Exchange Online, SharePoint Online, OneDrive, Teams, Power BI, and Microsoft 365 Copilot prompts/responses

Conditions combine SITs, sensitivity labels, and keywords with Match any / Match all logic and a minimum instance count

Actions include audit-only, block with override, block without override, and message encryption in Teams and Exchange

Start in test with policy tips , measure matches, then enforce — this is the Microsoft-recommended deployment sequence

Copilot DLP inspects both the user's prompt and Copilot's response, blocking sensitive content from being surfaced through groundings