Study guide

11.2 Configure Advanced DLP Rules for Devices

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

11.2 Configure Advanced DLP Rules for Devices

Key Takeaways Explain This Topic AI

Select the Devices location, then Create or customize advanced DLP rules; a rule is enforced on an endpoint only when both the user and the device are in scope

Device scoping does not support Microsoft Entra registered devices; macOS device-and-group scoping needs Defender build 101.25072 or newer

Device activities you restrict include copy to USB, copy to a network share, print, copy to clipboard, upload to a restricted cloud service or access from an unallowed browser, paste to supported browsers, Bluetooth, and RDP (Windows)

On Windows you can Allow, Audit only, Block with override, Block, or Off each activity; macOS uses Audit only, Block with override, or Block — Allow is a Devices-location action, not a SharePoint action

Policy updates generally take about an hour to sync; authorized-group changes take 24 hours; unsaved content that never hits the local disk cannot be classified

Last updated: August 2026

The July 28, 2026 bullet is Configure advanced DLP rules for devices in DLP policies . In the Purview wizard that is the Devices location plus Create or customize advanced DLP rules , then Audit or restrict activities on devices . Templates can pre-fill SITs. The device-specific work is still an advanced rule: conditions, per-activity actions, user notifications, overrides, and incident reports.

A DLP policy is the container. A rule is the business logic. Devices can use sensitive information types and sensitivity labels to define content. Retention labels are not a Devices content-definition method. Trainable classifiers are supported as a Devices condition, but Endpoint DLP needs advanced classification scanning and protection (next section) before EDM, named entities, trainable classifiers, credential classifiers, and document fingerprinting work on the laptop. Adaptive Protection's device policy also documents that you must enable advanced classification or use a File type is condition — that Adaptive Protection design was the previous chapter; here you still must not build an endpoint rule that assumes cloud classifiers with advanced classification off.

Devices location: both the user and the device

When the policy includes Devices , you scope users/groups and devices/device groups . Microsoft's policy reference (updated 2026-06-26) is blunt: the policy is enforced on an endpoint only when both the user and the device are in scope . User in, device out: no. Device in, user out: no. Default is all users and all devices. Typical exam patterns:

  • Target User scope Device scope
  • Everyone on every onboarded PC All users and groups All devices and device groups
  • Kiosk hardware used by many people All users and groups Specific devices, or all devices minus an exclude list
  • Named people on every PC Specific users/groups (or all minus excludes) All devices and device groups
  • Payroll printers used by two accounts Specific users and groups Specific devices and device groups

Device scoping does not support Microsoft Entra registered. Joined and hybrid-joined devices can be targeted by device or device group. Registered devices can still be onboarded (previous section), but Microsoft does not document putting an Entra-registered machine in a specific devices include list. On macOS, device and device-group scoping needs Defender build 101.25072 or newer .

If a policy is scoped to devices whose signed-in users do not meet the user criteria, Microsoft says to explicitly exclude those users or devices. Leaving the mismatch in place produces unintended enforcement. All onboarded devices still receive endpoint policies so a multi-user device can evaluate the right user's rules; scanning is not limited to "this device's primary user."

The Devices and device groups control applies to Audit or restrict activities on devices . It does not apply to Audit or restrict activities when users access sensitive sites in Microsoft Edge . Apply restrictions to only unsupported file extensions also does not support device-and-group scoping.

Activities you set on the rule

Under Audit or restrict activities on devices you configure service-domain/browser activities and file activities for all apps . Microsoft's Learn about Endpoint DLP activity table (updated 2026-08-05) is the list to memorize:

Activity What it catches Windows macOS Restrictable?

Upload to a restricted cloud service domain or access from an unallowed browser Cloud upload against the service-domain list; unallowed browsers are blocked from the file and sent to Edge Yes Yes Yes

  • Paste to supported browsers Classifies the pasted text , not the source file's label Yes Preview Yes
  • Copy to clipboard Copy from a protected file; also redirected clipboards on AVD with Windows 365 Yes Yes Yes
  • Copy to USB removable device Copy or move to USB media Yes Yes Yes

Copy to a network share Copy or move to a share, including redirected USB that appears as a share on AVD with Windows 365 Yes Yes Yes

  • Print Local, redirected, and (with printer groups) authorized printers Yes Yes Yes
  • Copy or move using unallowed Bluetooth app Bluetooth apps you listed in Endpoint DLP settings Yes Yes Yes
  • Copy or move using RDP Copy into a remote desktop session Yes Not supported Yes
  • Create an item / Rename an item File create or rename Yes Yes Auditable only
  • Access by restricted apps Apps on the restricted-apps list open a protected file Yes Yes Yes

Create Windows Recall snapshots (preview) Sensitive item or Teams message that would land in Recall Windows x64 No (and not ARM64) Yes

Access by apps not included in the restricted apps list is Windows-only in the settings support matrix. Create/rename do not take Block.

Enforcement modes on Windows: Allow , Audit only , Block with override , Block , and Off . Microsoft documents Allow as a Devices-location action (audit, no user notifications or alerts). On macOS , the policy-reference wording is Audit only , Block with override , or Block — do not promise Allow on a Mac stem. Off means no block and no audit. Block with override : the toast Allow / Edge OK lets the user proceed. After override, Endpoint DLP automatically resumes for copy to network share , copy to USB , and print . Other activities require the user to override again.

Microsoft's rollout advice is still start least-restrictive: Allow (devices) / Audit only (other locations), read the data, then tighten. Simulation mode is the policy state ; it is not a substitute for picking the activity actions.

Clipboard, unsaved files, and virtual USB

Clipboard Block / Block with override is not "any paste anywhere." Intra-file copy inside the same Word/Excel/PowerPoint file that already matched is allowed . Copy from a matching Office file into a different Office file is blocked . Copy from a matching Office file into Notepad is blocked . Copy from Notepad (or any non-Office app) that contains matching content is blocked to any destination. Copy from a non-matching Notepad file is allowed. Extra trap: while a DLP-blocked file is open , copying from other files in the same application — even files with no DLP rule — is restricted.

If data is never saved to a file on the local device , Endpoint DLP cannot scan it. Saving a Word document directly to USB without a local copy is the textbook miss.

In virtualized environments, USB storage is treated as a network share . Include Copy to a network share , not only Copy to USB , or you will miss the copies. Activity explorer and alerts label those events as copy to a network share. AVD browser clipboard enforcement is a known gap; RDP-path clipboard is monitored.

Restricted app groups (configured in Endpoint DLP settings, consumed on the rule) override the restricted-apps list in the same rule. You can Allow a sanctioned CAD group and Block everyone else. Maximum 50 apps per group and 10 groups . If Restricted app activities is Block , the user never gets to the file, so File activities for all apps never run. If it is Audit only or Block with override, the user gets in and then USB/print/clipboard actions apply.

Sync time, evaluation, and what you leave for later

DLP evaluation of sensitive items is central . Microsoft says it generally takes about an hour for policy updates in the Purview portal to synchronize; items re-evaluate the next time they are accessed or modified. Authorized Groups changes need 24 hours . Offline Windows devices keep enforcing already pushed policies on already classified files; new or edited policies wait until the device reconnects. That offline behavior is not supported the same way on macOS. Enforcement events from an offline device do not show in Activity explorer until the device is online — investigation is the next chapter.

Just-in-time protection can block egress on items that have never been evaluated or whose evaluation is stale. Do not configure JIT here. Do not build the Activity explorer attribute list here. This section stops when the advanced rule's Devices activities and actions are correct.

Loading diagram... Advanced DLP rule path for the Devices location