Study guide
10.2 Interpret DLP Policy and Rule Precedence
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
10.2 Interpret DLP Policy and Rule Precedence
Key Takeaways Explain This Topic AI
DLP is not first-match-wins like Exchange mail-flow rules: matching policies and rules are evaluated, matches are logged, and enforcement follows the most restrictive applicable action
On hosted locations such as Exchange, SharePoint, and OneDrive, rules get priority in creation order (first created is highest); the first evaluated rule that has the most restrictive action is enforced
Restrict access with no override is more restrictive than restrict with override, which is more restrictive than notify-only; only that winning rule’s policy tip is shown
Endpoint DLP applies the aggregate of the most restrictive actions across matching policies: identical actions use the highest-priority policy or rule, Turn it on beats simulation, and no override beats allow override
Additional options that stop further rule and policy processing after a match are documented only for Exchange and Teams locations
Last updated: August 2026
The July 28, 2026 outline asks you to interpret policy and rule precedence in data loss prevention . Microsoft’s current published model lives in the Data Loss Prevention policy reference (priority by which rules are evaluated and applied) and in Send email notifications and show policy tips for DLP policies . Adaptive Protection Device DLP even restates the same idea: if the default Adaptive Protection Device policy and an independent Device policy both target a user, the most restrictive policy’s actions apply . Do not import Exchange mail-flow rule folklore. DLP does not stop at the first matching policy the way a transport rule with stop-processing might.
A DLP policy is a container: locations plus one or more rules . A rule holds conditions, actions, user notifications, optional user overrides, incident reports, and Additional options . Microsoft states that rules run sequentially, starting with the highest-priority rule in each policy . Priority is an evaluation order, not a promise that lower-priority rules are ignored.
Hosted service locations: first most-restrictive rule wins
For Exchange, SharePoint, and OneDrive , each rule is assigned priority in the order it is created . The rule created first has first (highest) priority ; the next rule is second; and so on. Content is evaluated against rules in that order. If content matches multiple rules, the first rule evaluated that has the most restrictive action is enforced .
Microsoft’s canonical four-rule example is the one to memorize:
Rule What it does Applied?
- Rule 1 Only notifies users Evaluated, not applied
- Rule 2 Notifies users, restricts access, allows user overrides Evaluated, not applied
Rule 3 Notifies users, restricts access, does not allow user overrides Enforced — highest-priority most restrictive rule
Rule 4 Restricts access Evaluated, not applied
Restrict without override beats restrict with override, which beats notify-only. A later restrict-only rule does not steal enforcement from an earlier restrict-without-override rule. Matches for all of the rules are still recorded in the audit log and DLP reports. Investigators can see Rule 1 and Rule 4 fired even though the user only felt Rule 3.
The same most-restrictive logic applies when several policies match, not only when several rules sit in one policy. The policy-tips article is explicit: content can match several rules in one DLP policy or several different DLP policies , but only the policy tip from the most restrictive rule that has the highest priority is shown . Evaluation is not “policy 0 matches, stop.” Other policies still match and still write audit events; the user still sees one tip from the winning rule.
That grouping is why Microsoft tells you to put related protection requirements in one policy with several rules (for example every HIPAA rule together) instead of scattering overlapping HIPAA clones across ten policies. Overlap is legal; it is just harder to predict which tip the user sees.
Policy tips and overrides follow the same winner
Users must not see a cascade of tips. Only the policy tip from the most restrictive rule that has the highest priority is shown , including policies that are in simulation mode . A tip from a rule that blocks access is shown instead of a tip from a rule that only sends a notification . Custom policy tips follow the most restrictive rule, not necessarily the rule that is performing the restriction — a wording trap if two rules share a match but only one blocks.
If that winning rule allows people to override , overriding it also overrides any other rules the content matched . Override is therefore a precedence feature, not a per-rule peephole. User overrides require Notify users in Office 365 services with a policy tip . If you set an override action but BlockAccess is not true (or BlockAccessScope is wrong), the tip appears without an override control. Overrides are not available for on-premises repositories.
On endpoints, if the user selects Allow for print, copy to USB, or copy to a network share, they have 30 seconds after the popup; miss that window and the activity stays blocked. Other device activities must be retried after Allow.
Endpoint DLP: aggregate the most restrictive actions
Devices do not collapse to a single rule. When an item matches multiple DLP rules, Endpoint DLP runs a documented calculation and applies the aggregate or sum of the most restrictive actions . Factors:
Factor What Microsoft documents
Policy priority If matching policies have identical actions, use the highest-priority policy (priority 0 is highest)
Rule priority If matching rules in a policy have identical actions, use the highest-priority rule
Policy mode Turn it on (enforce) is applied preferentially over Run the policy in simulation mode with policy tips and Run the policy in simulation mode
Differing actions Take the aggregate / sum of the most restrictive actions (block print from policy A plus block USB from policy B both apply)
- Authorization groups Same aggregate-most-restrictive rule when policies disagree
- Override options No override is applied rather than Allow override
Worked Microsoft scenarios use three policies, all matching credit cards or SSNs:
ABC (priority 0): block print , audit other egress.
MNO (priority 1): block copy to USB , audit other egress.
XYZ (priority 2): block copy to clipboard , audit other egress; also blocks print in the SSN example.
Credit cards only, both ABC and MNO Turn it on : runtime blocks print and USB , audits the rest. Credit cards and SSNs, all three on: runtime blocks clipboard, USB, and print . Credit cards, ABC on and MNO in simulation : MNO’s USB block does not enforce ; runtime blocks print (from ABC) and audits USB . Credit cards, ABC blocks USB with override and MNO blocks USB without override : runtime is block without override .
Simulation rewrites the configured action at runtime:
- Configured action Simulation, policy tips off Simulation, policy tips on
- Block Audit Block with override
- Block with override Audit Block with override
- Audit only Audit Audit
- Allow Allow Allow
Allow as a DLP action exists on Devices . A simulation-mode Adaptive Protection Device policy that “blocks” USB is therefore not blocking in production until you switch the policy to Turn it on — which is why quick setup’s Adaptive Protection DLP policies start in simulation.
Additional options, list order, and what precedence is not
Additional options on a rule can set evaluation priority and stop further rule and policy processing after a match. Microsoft documents that stop-processing control only for Exchange and Teams locations . Do not promise it on SharePoint, OneDrive, or Devices.
On endpoints, Microsoft’s worked examples number policies 0 , 1 , and 2 , with 0 as the highest-priority policy. When two Turn-it-on policies configure the same action, that highest-priority policy supplies the action. When they configure different actions, both the priority-0 print block and the priority-1 USB block can apply together. Raising a blocking policy’s priority therefore matters for identical actions; it does not hide another policy’s matches from audit logs or DLP reports.
What precedence is not :
It is not “priority 0 means ignore every other policy.” Other policies still evaluate . Hosted workloads still pick the most restrictive matching rule among those evaluated; endpoints still sum blocks.
It is not mail-flow order. Microsoft Q&A on overlapping DLP policies repeats the product behavior: priority does not make DLP first-match-wins.
It is not “the notify-only rule hides the block.” The block is more restrictive, so the block (and its tip) wins on hosted locations.
It is not Adaptive Protection replacing this model. Adaptive Protection is a condition . Once two Device policies match, you are back in most-restrictive aggregation.
Custom Learn more URLs on Exchange policy tips override the tenant Set-PolicyConfig -ComplainceURL value (Microsoft’s cmdlet spelling). That is URL precedence, not rule precedence.
Design implication you should be able to say out loud: if two policies fight, reduce overlap or combine the logic into one policy with ordered rules . Use simulation to see which rule is most restrictive before you Turn it on. When you can walk the four-rule hosted example, the ABC/MNO/XYZ endpoint grid, the simulation rewrite table, and the single-tip/override-all behavior, you can interpret DLP precedence on SC-401.