Study guide

9.2 Roles and Permissions for Data Loss Prevention

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.2 Roles and Permissions for Data Loss Prevention

Key Takeaways Explain This Topic AI

Create and edit unrestricted DLP policies from the Compliance administrator, Compliance data administrator, Information Protection, Information Protection Admin, or Security administrator role groups

The DLP Compliance Management role views and edits DLP policy settings and reports; View-Only DLP Compliance Management views those settings and reports without making changes

Information Protection Admins write DLP policies; Information Protection Analysts and Investigators triage alerts with view-only policy access; Information Protection Readers are report-oriented

Administrative-unit restricted DLP admins can create and edit policies only for their units and see only those units' alerts; unrestricted admins see the whole tenant

A Microsoft Entra role such as Compliance Administrator overrides a scoped Purview assignment and makes overlapping access unscoped

Last updated: August 2026

The second DLP bullet on the July 28, 2026 outline is Implement roles and permissions for data loss prevention . This is a Microsoft Purview portal problem under Settings > Roles and scopes > Role groups , not an Exchange mail-flow permission and not a reason to hand out Global Administrator . Microsoft's permissions article (updated 2026-07-30) repeats the least-privilege warning: minimize Global Administrator; grant only the tasks the person must perform.

A role is a named bundle of tasks. DLP Compliance Management is the role that views and edits settings and reports for DLP policies . View-Only DLP Compliance Management views those settings and reports. A role group is a container of roles plus members. You usually add people to a built-in group. You can also Create role group , add only DLP Compliance Management , and that is the scalpel when the stem says "DLP policies and nothing else." To view or edit role groups at all, the operator needs Role Management (shipped with Organization Management ) or Global Administrator. Do not put Role Management on every DLP operator.

Who can create unrestricted DLP policies

Microsoft's Create and deploy DLP policies article (updated 2026-06-26) lists the role groups whose members can create and deploy policies:

  • Compliance administrator
  • Compliance data administrator
  • Information Protection
  • Information Protection Admin
  • Security administrator

Those names are the Purview role groups (Information Protection Admin is the admin-shaped Information Protection group). They are also the groups Microsoft's Q&A guidance cites when a Global Administrator still cannot open DLP > Policies: Entra directory roles alone are not a substitute for a Purview DLP-capable group. Put the account in one of the groups above, then retry.

Granular roles Microsoft lists next to that create list: DLP Compliance Management , Information Protection Admin , Information Protection Analyst , Information Protection Investigator , and Information Protection Reader . Granular role groups: Information Protection , Information Protection Admins , Information Protection Analysts , Information Protection Investigators , and Information Protection Readers . Read the flyout. Being in the Information Protection family is not permission to write a policy.

DLP Compliance Management versus Compliance Administrator versus view-only

Memorize the Defender / Purview role table wording:

Assignment Microsoft-documented DLP capability When it is the exam answer

DLP Compliance Management (role) View and edit settings and reports for DLP policies Least-privilege write for DLP configuration; default member of Compliance Administrator, Compliance Data Administrator, Organization Management, and Security Administrator

View-Only DLP Compliance Management (role) View the settings and reports for DLP policies Auditors, SOC readers, and anyone who must see policy JSON-equivalent settings without changing them; also appears in Global Reader, Security Operator, and Security Reader

Compliance Administrator (role group) Broad compliance hammer: device management, DLP, reports, preservation, eDiscovery-adjacent roles, Information Protection Admin, and DLP Compliance Management Works, and is too wide if the person should only touch DLP

Compliance Data Administrator (role group) Data protection, DLP, reports, preservation; includes DLP Compliance Management and View-Only DLP Compliance Management Still broader than a custom DLP-only group

Information Protection Admins Create, edit, and delete DLP policies, sensitivity labels and their policies, and classifier types; manage endpoint DLP settings Built-in fit when the same people own labels and DLP

Information Protection (full group) Full control of information protection features, including DLP, labels, classifiers, activity explorer, and content explorer Too broad for a DLP-only operator

Information Protection Analysts Manage DLP alerts and activity explorer ; view-only DLP policies, labels, and classifiers Alert triage, not Create policy

Information Protection Investigators Analyst capabilities plus content explorer ; still view-only on policy definitions Investigation, not authoring

Information Protection Readers View-only reports for DLP and labels Reporting only

Global Reader Read-only configuration and settings, including View-Only DLP Compliance Management Tenant-wide reader, not a DLP editor

Exam trap: Compliance Administrator includes DLP Compliance Management , so it can create policies. The stem that asks for least privilege wants DLP Compliance Management on a custom role group , or Information Protection Admins when labels travel with DLP. The stem that asks who can see policies but not change them wants View-Only DLP Compliance Management , Information Protection Analysts/Investigators/Readers (view-only on definitions), or Global Reader — not Compliance Administrator.

Information Protection Analysts can work the DLP alerts dashboard and activity explorer. That is operations. It is not Create policy. If the item mixes "investigate DLP alerts" with "do not let them edit the HIPAA policy," Analysts or Investigators are the group; DLP Compliance Management is the wrong gift.

Microsoft Entra roles in the Purview portal

Roles and scopes also lists Microsoft Entra roles. Compliance Administrator and Compliance Data Administrator in Entra map to the Purview groups of the same name. Security Administrator maps to Security Administrator. Global Reader maps to Global Reader. Global Administrator maps into Organization Management and more. Use Entra when the person's job is already that directory role. Do not stack Entra Compliance Administrator on top of a carefully scoped Purview group and assume the scope survives.

Microsoft documents role precedence in the Purview permissions article:

Assign Compliance Administrator in Entra and a scoped Compliance Administrator in Purview, and the Entra role wins . Effective access is unscoped . Administrative units do not apply.

Assign Global Reader in Entra and a scoped DLP Compliance Management assignment in Purview, and overlapping features or APIs grant unscoped access to that data.

When both scoped Purview assignments and Entra roles exist, Entra always takes precedence for overlapping capabilities.

That is the multinational exam item: you built France-only DLP admins, then someone added Entra Compliance Administrator "just in case," and those admins can suddenly see Germany's policies.

Privileged Identity Management (PIM) for Groups can make an Entra security group eligible for just-in-time membership, and you can assign that group to a Purview role group. Direct user assignments to Purview role groups are not activated the same way as PIM for Entra roles. Temporary permissions on Purview role groups can expire automatically: administrators set an expiration between one day and two years . Built-in and custom groups support this except eDiscovery Administrator and eDiscovery Manager. There is no expiry reminder; My Permissions shows the latest expiration across assignments.

Copilot DLP policies add two more names you may see: Microsoft Entra AI Administrator and Purview Data Security AI Admin / Data Security AI Admins , alongside the usual Compliance / Information Protection / Security Administrator groups. Least privilege for Copilot DLP is still not Global Administrator.

Administrative units

Administrative units are created in Microsoft Entra ID (P1 or P2). Purview then lets you Assign admin units on supported role-group members. DLP is a supported solution: role groups and DLP policies. Restricted administrators pick one or more of their units as the initial policy scope. Unrestricted administrators can target the entire directory or optionally pick units.

Microsoft's DLP policy reference splits administrators like this:

Unrestricted administrator : create and scope policies to the whole organization, edit all DLP policies, create AU-scoped policies, view all DLP alerts and events.

Administrative unit restricted administrator : must still belong to a DLP-capable role or role group; can create and scope policies only to assigned units, edit only those policies, and view alerts and events only from those policies.

After you assign units to a member, that restricted admin cannot see or edit existing unscoped policies . Those policies keep working; unrestricted admins still see them. Historical activity explorer and alert data for the whole tenant also stays with unrestricted admins. Going forward, the restricted admin sees data for their units only. If you are an AU-restricted admin, the DLP alerts dashboard shows only your unit's alerts.

Assign admin units requires the Role management role. Supported built-in groups for AU assignment include Compliance Administrator, Compliance Data Administrators, Global Reader, the Information Protection family, Organization Management, Security Administrator, Security Operator, and Security Reader. Custom role groups can always assign admin units.

Location support is not universal. Exchange, SharePoint, OneDrive, Teams, and Devices support administrative units. Fabric and Power BI, on-premises repositories, Instances, managed/unmanaged cloud apps, and Microsoft 365 Copilot and Copilot Chat do not . You cannot promise a France-only Copilot DLP policy via admin units. SharePoint sites can be associated to an AU in Purview; a DLP policy assigned to that AU then applies to all sites in the unit, with no extra site include/exclude. Site queries can take up to five days to populate — wait before you attach the policy. Microsoft Defender XDR supports administrative units for DLP (not for Insider Risk Management) and documents a ceiling of 100 administrative units.

Worked example: Adele is in Information Protection Admins with the France AU assigned. She can create a HIPAA DLP policy for France users and see France alerts. She cannot open the tenant-wide credit-card policy that an unrestricted Compliance Administrator created last year. If you also grant Adele Entra Compliance Administrator , Microsoft's precedence rule makes her unscoped: the France AU no longer hides Germany.

What these permissions do not replace

Purview DLP roles do not replace Exchange admin center permissions for mail-flow rules. They do not onboard devices (endpoint DLP has its own permission list in that chapter). They do not make Adaptive Protection, rule precedence, or MDCA file policies appear — those remain the next chapter's skills. They do not let an Information Protection Reader author a policy because the group name contains Information Protection.

When you can name DLP Compliance Management versus View-Only DLP Compliance Management versus the wide Compliance Administrator group, and you can explain how administrative units collapse under an Entra directory role, you have this blueprint bullet.

Loading diagram... DLP write, view-only, and administrative-unit scope