Study guide
9.1 Design Data Loss Prevention Policies
SC-401: Administering Information Security in Microsoft 365 Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current SC-401 Exam Facts 1.2 Scoring, Retakes, and Annual Renewal 1.3 Role, Blueprint, and Prep Path
2 Data Classification Foundations
2.1 Identify Sensitive Information Requirements 2.2 Translate Requirements into Sensitive Info Types 2.3 Create and Manage Custom Sensitive Info Types
3 Specialized Classification Methods
3.1 Document Fingerprinting 3.2 Exact Data Match Sensitive Info Types 3.3 Trainable Classifiers
4 Classification Monitoring and OCR
4.1 Monitor Classification with Data Explorer and Content Explorer 4.2 Configure OCR Support for Sensitive Info Types
5 Sensitivity Label Design
5.1 Roles and Permissions for Sensitivity Labels 5.2 Define and Create Sensitivity Labels for Items and Containers 5.3 Protection Settings and Content Marking
6 Label Policies, Containers, and Defender for Cloud Apps
6.1 Configure Publishing Policies for Sensitivity Labels 6.2 Configure Auto-Labeling Policies 6.3 Apply Sensitivity Labels to Containers 6.4 Apply Sensitivity Labels with Microsoft Defender for Cloud Apps
7 Information Protection Client and Scanner
7.1 Plan and Implement the Microsoft Purview Information Protection Client 7.2 Manage Files with the Information Protection Client 7.3 Bulk Classification with the Information Protection Scanner
8 Microsoft Purview Message Encryption
8.1 Design and Implement Microsoft Purview Message Encryption 8.2 Design and Implement Advanced Message Encryption
9 DLP Policy Design
9.1 Design Data Loss Prevention Policies 9.2 Roles and Permissions for Data Loss Prevention 9.3 Create and Manage DLP Policies
10 Adaptive Protection, DLP Precedence, and MDCA File Policies
10.1 Configure DLP Policies for Adaptive Protection 10.2 Interpret DLP Policy and Rule Precedence 10.3 Create File Policies in Defender for Cloud Apps Using DLP
11 Endpoint DLP Configuration
11.1 Device Requirements for Endpoint DLP Including Extensions 11.2 Configure Advanced DLP Rules for Devices 11.3 Configure Endpoint DLP Settings
12 Just-in-Time Protection and Endpoint Monitoring
12.1 Configure Just-in-Time Protection 12.2 Monitor Endpoint Activities
13 Retention Labels and Adaptive Scopes
13.1 Plan Information Retention and Disposition with Retention Labels 13.2 Create and Manage Adaptive Policy Scopes 13.3 Create Retention Labels for Data Lifecycle Management
14 Publishing, Auto-Apply, and Retention Precedence
14.1 Publish Retention Labels 14.2 Auto-Apply Retention Labels 14.3 Retention Precedence and Policy Lookup
15 Retention Policies and Recovering Retained Content
15.1 Create and Configure Retention Policies 15.2 Recover Retained Content in Microsoft 365
16 Insider Risk Management Foundation
16.1 Roles and Permissions for Insider Risk Management 16.2 Plan and Implement Insider Risk Management Connectors 16.3 Integrate Insider Risk Management with Microsoft Defender for Endpoint
17 IRM Settings, Indicators, and Templates
17.1 Configure Insider Risk Management Settings 17.2 Configure Policy Indicators 17.3 Select an Appropriate Policy Template
18 IRM Policies, Forensic Evidence, and Adaptive Protection
18.1 Create and Manage Insider Risk Management Policies 18.2 Manage Forensic Evidence Settings 18.3 Enable Insider Risk Levels for Adaptive Protection
19 IRM Alerts, Cases, and Workflow
19.1 Manage Insider Risk Alerts and Cases 19.2 Insider Risk Workflow and Notice Templates
20 Purview Audit and Activity Explorer
20.1 Assign Microsoft Purview Audit (Premium) User Licenses 20.2 Investigate Activities with Microsoft Purview Audit 20.3 Configure Audit Retention Policies 20.4 Analyze Purview Activities with Activity Explorer
21 DLP, Insider Risk, and Defender XDR Alert Response
21.1 Respond to DLP Alerts in the Microsoft Purview Portal 21.2 Investigate Insider Risk Activities in the Microsoft Purview Portal 21.3 Respond to Purview Alerts in Microsoft Defender XDR
22 MDCA File Policy Alerts and eDiscovery
22.1 Respond to Defender for Cloud Apps File Policy Alerts 22.2 Perform Searches by Using eDiscovery
23 Protecting Content Used by AI Services
23.1 Implement Purview Controls for AI Services 23.2 Implement Microsoft 365 Workload Controls for AI
24 Data Security Posture Management for AI
24.1 Prerequisites for DSPM for AI 24.2 Manage Roles and Permissions for DSPM for AI 24.3 Configure DSPM for AI Policies 24.4 Monitor Activities in DSPM for AI
9.1 Design Data Loss Prevention Policies
Key Takeaways Explain This Topic AI
Write a single policy intent statement that answers what to monitor, policy scoping, where to monitor, match conditions, and the action to take
Microsoft Purview DLP locations for Enterprise applications and devices include Exchange Online, SharePoint, OneDrive, Teams chat and channel messages, Devices, Fabric and Power BI, and Microsoft 365 Copilot and Copilot Chat
When a policy includes more than one location, a location that cannot use a content definition (sensitive information type, sensitivity label, or retention label) wins: SharePoint plus Teams is SIT-only
The Microsoft 365 Copilot and Copilot Chat location is available only in the Custom policy template, cannot be combined with other locations, and does not support administrative units
Adaptive Protection, policy and rule precedence, and Defender for Cloud Apps file policies exist; they are the next chapter, not this design pass
Last updated: August 2026
The first DLP bullet on the July 28, 2026 SC-401 outline is Design data loss prevention policies based on an organization's requirements . Microsoft's design article (Learn: Design a data loss prevention policy) is blunt: document the policy before you open the wizard. A written policy intent statement is faster than trial-and-error clicks, and it is the artifact you reuse in stakeholder reviews, incident investigations, and later tuning.
Data loss prevention (DLP) in Microsoft Purview identifies, monitors, and automatically protects sensitive items. Detection is not a keyword grep. DLP uses primary matches (keywords, regular expressions, checksum-style function validation), secondary matches near the primary hit, machine learning, and, when you choose them, sensitivity labels or retention labels. Protective actions can warn with a policy tip , block sharing with or without override, lock or quarantine files at rest, or hide sensitive text in Teams chat. Those actions only make sense after you can say, in one sentence, why the policy exists.
The five questions every intent statement must answer
Microsoft's DLP configuration overview requires every policy to choose:
What to monitor (Office documents, email, device files, Copilot prompts, and so on).
Policy scoping — full directory versus administrative units (preview-era wording still appears as Policy scoping in the reference).
Where to monitor (locations).
Conditions that must match before the rule fires.
Actions when those conditions match.
If you cannot summarize those five answers in one statement, you are not ready to create the policy. Microsoft's own first-draft example is the HIPAA story you should be able to reconstruct on the exam:
"We're a U.S. based organization, and we need to detect Office documents that contain sensitive health care information covered by HIPAA that are stored in OneDrive/SharePoint and to protect against that information being shared in Teams chat and channel messages and restrict everyone from sharing them with unauthorized third parties."
That sentence is not marketing copy. It already names the template family (U.S. Health Insurance Act / HIPAA Enhanced), the locations (OneDrive, SharePoint, Teams), a sharing condition (people outside the organization), and an action (restrict access or encrypt content in Microsoft 365 locations). As you design, you will extend it with confidence levels, instance counts (leakage tolerance), include/exclude scopes, and whether the first production state is simulation or enforcement. The statement still stays one sentence plus a mapping table.
Map the statement to configuration
Work the mapping with stakeholders who own the business process, not only with security. The legal team can tell you which regulation applies; the process owner tells you who must still share the data. Microsoft's planning article uses internal auditors who export credit card numbers to a third-party auditor: a zero-leakage block would break that review unless you add an exception or a narrower action.
Fragment of the intent statement Configuration mapping
Detect Office documents with HIPAA-covered health information What : start from the U.S. Health Insurance Act (HIPAA) Enhanced template, then confirm the preconfigured sensitive information types (SITs) such as ICD-9-CM, ICD-10-CM, All Full Names, All Medical Terms And Conditions, and U.S. Physical Addresses
Stored in OneDrive/SharePoint; protect Teams chat and channel sharing Where : include SharePoint sites, OneDrive accounts, and Teams chat and channel messages; set policy scoping to the full directory unless administrative units are in play
Shared with unauthorized third parties Conditions : content contains the HIPAA SITs and content is shared with people outside the organization; set confidence and instance-count thresholds with the process owner
Restrict everyone from sharing them Actions : Restrict access or encrypt the content in Microsoft 365 locations; decide separately whether users get a policy tip, an override, and an incident-report alert
Locations change what you can configure. Microsoft's design article warns you to check the policy reference before you promise a sensitivity-label condition or a device-only action on a multi-location policy.
Locations you actually pick
Create DLP policies for Enterprise applications & devices in the Microsoft Purview portal. Microsoft's Learn about DLP article (updated 2026-06-26) lists these locations and sources: Exchange, SharePoint, OneDrive accounts, Teams chat and channel messages, Office apps (Word, Excel, PowerPoint), devices running Windows 10, Windows 11, and the three most recent macOS versions, non-Microsoft cloud apps, on-premises file shares and on-premises SharePoint, Microsoft Fabric and Power BI workspaces, Microsoft 365 Copilot and Copilot Chat (still labeled preview in that overview), and managed cloud apps. A separate Inline web traffic path (Edge for Business and Network Data Security, preview) targets unmanaged cloud apps; that is a different policy family, not a checkbox you add to a classic Exchange policy.
The policy-reference location table (the one you should memorize for include/exclude and administrative-unit support) currently documents:
Location Administrative units Typical include/exclude Data state
Exchange Online Yes Distribution groups, security groups, Microsoft 365 groups (assigned or dynamic) Data in motion
SharePoint Yes Sites (and, in preview, adaptive scopes). If the policy is scoped to an administrative unit that already includes SharePoint sites, it applies to all sites in that unit — no further site include/exclude Data at rest and in use
- OneDrive Yes Groups and users (group members, not the group as an entity) Data at rest and in use
- Teams chat and channel messages Yes Groups (members only) Data in motion and in use
- Devices Yes Users/groups and devices/device groups; both must be in scope Data in use and in motion
- Fabric and Power BI No Workspaces Data in use
- On-premises repositories No Repository Data at rest
- Instances (non-Microsoft cloud app instances) No Cloud app instance Data at rest
- Microsoft 365 Copilot No Account or distribution group Data at rest and in use
- Managed / unmanaged cloud apps No Account or distribution group Data in motion
Published scoping limits you should not invent beyond: Exchange policies support no more than 50 distribution-list / group inclusions and exclusions; OneDrive supports up to 100 individual users, or up to 50 groups if you need more people; SharePoint supports up to 100 specific sites. If you need more than 100 OneDrive users, put them in groups first. Mixing OneDrive users and groups in the same include list uses the intersection , not the union — User4 who is listed but not in the listed groups is dropped. Endpoint DLP device requirements, browser extensions, and endpoint settings are later chapters; this chapter only places Devices on the location list.
Combining locations shrinks the condition list
DLP can define content with a sensitive information type , a sensitivity label , or a retention label . Support is per location. SharePoint and OneDrive can use all three. Exchange can use SITs and sensitivity labels, not retention labels. Teams chat and channel messages can use SITs only. When you select multiple locations, Microsoft's rule is that a "no" takes precedence over a "yes." SharePoint plus Teams therefore becomes SIT-only even though SharePoint alone could have used labels. That is a design decision, not a portal bug.
Trainable classifiers are documented as a content condition for Exchange, SharePoint, OneDrive, Teams, Devices, and unmanaged cloud apps — not as a substitute for choosing the right locations.
Conditions, exceptions, and actions
A DLP policy is a container. The business logic lives in rules . A rule has conditions (what the item looks like and the context of the activity), actions (audit, notify, restrict, encrypt, quarantine, Copilot processing controls), user notifications / policy tips , optional user overrides , incident reports , and additional options such as rule priority. Conditions are where leakage tolerance lives: five Social Security numbers emailed outside the organization is a different rule from one SSN in an internal draft.
Context options change with location. Pick Exchange and you see sender/recipient predicates. Pick SharePoint and you see sharing and site context. Pick several locations and you keep only the conditions those locations share.
Exceptions as a separate designer surface are gone. Microsoft's design article states that existing exceptions are replaced with a NOT condition in a nested group inside Conditions . You create groups to combine AND, OR, and NOT. Example: block mail that contains credit card numbers or the Highly Confidential label, unless the sender is on the finance team and the recipient is a named mailbox. Nested NOT is the exception.
Office desktop trap: when Word, Outlook, Excel, or PowerPoint matches a policy that uses complex conditions, users see policy tips only for rules that use Content contains sensitive information . A beautifully nested label-or-SIT rule can enforce in the service and still look silent in the Win32 client.
Actions also follow location. SharePoint, Exchange, and OneDrive can restrict access or encrypt Microsoft 365 content and show a tip. Teams can block sensitive text in the chat. Devices can audit or restrict copy-to-USB and similar activities ( Allow as an action exists only on Devices). On-premises repositories can move a file to a quarantine folder. You configure the action now even if the first state will be simulation — simulation is a deployment control, not a reason to leave the action blank.
Microsoft 365 Copilot and Copilot Chat
The dedicated Copilot DLP article (updated 2026-06-11) is the current behavior to study. The Microsoft 365 Copilot and Copilot Chat location exists, and it is only in the Custom policy template . Turning it on disables every other location on that policy. It does not support administrative units. DLP alerts, notifications, and simulation mode are supported . Policy updates can take up to four hours to show in Copilot.
You cannot put Content contains SITs and Content contains sensitivity labels in the same rule . Use two rules in the same policy. Documented actions under Prevent Copilot from processing content include blocking Processing prompts (no response; prompt not used for internal or web search), blocking Performing Web Searches (response still generated from permitted internal Microsoft 365 sources), excluding labeled files and emails from grounding (citations may still list the item), and, in preview, excluding Email is received from > External users using sender-domain metadata only. DLP does not scan the contents of files users upload into a prompt ; it evaluates typed prompt text.
What this chapter does not design
Three neighboring blueprint skills are real and they are the next chapter : DLP for Adaptive Protection (Insider Risk Management risk levels as a condition), policy and rule precedence (including how multiple matching policies combine actions), and Defender for Cloud Apps file policies that use DLP. Do not stuff those controls into the intent statement yet. Mention them in the design review as follow-on work so stakeholders do not think one HIPAA policy also scores insider risk or replaces an MDCA file policy.
Design process you should be able to recite
Finish planning: stakeholders, categories of sensitive information, goals, deployment plan.
Read the policy reference so every component's effect is known.
Review what the DLP templates already include before you build Custom.
Write the intent statement with the process owner.
Place the policy in the overall DLP strategy (one regulation, one location family, or one department — not one giant policy that tries to be all three).
Map each clause to a configuration control.
Choose predefined template or Custom (Copilot forces Custom).
Collect every setting the wizard will ask, including ones the first draft omitted.
Document the full setting list and get sign-off.
Create a draft policy (next section) and keep it Keep it off until that sign-off exists.
If the item gives you a regulation, a location, a sharing story, and a desired user experience, your job is to produce that intent sentence and the mapping — not to skip ahead to Adaptive Protection or MDCA.