Study guide
5.1 Roles and Permissions for Sensitivity Labels
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
5.1 Roles and Permissions for Sensitivity Labels
Key Takeaways Explain This Topic AI
Create and configure sensitivity labels in the Microsoft Purview portal under Solutions > Information Protection > Sensitivity labels; assign roles under Settings > Roles and scopes
Least privilege for label authors is a custom role group that contains the Sensitivity Label Administrator role, or the Information Protection Admins role group
Information Protection is full control of labels, DLP, and classifiers; Information Protection Analysts, Investigators, and Readers are view-oriented and do not create labels
Compliance Administrator, Compliance Data Administrator, and Security Administrator can also manage labels, but they are broader than a label-only assignment
Purview admin permissions are required to create labels and label policies, not to apply a published label in Word, Excel, PowerPoint, or Outlook
Last updated: August 2026
The first sensitivity-label bullet on the July 28, 2026 SC-401 outline is Implement roles and permissions for administering sensitivity labels . That skill is about who may open the label designer in the Microsoft Purview portal , not about who may click Confidential on a Word document. Microsoft's get-started article (updated 2026) states the permissions are required only to create and configure sensitivity labels and their label policies . They are not required to apply labels in apps or services.
Work in the current portal names. Sign in at the Microsoft Purview portal. Role groups live under Settings > Roles and scopes > Role groups . The labels themselves live under Solutions > Information Protection > Sensitivity labels . Microsoft recommends roles with the fewest permissions and specifically warns against using Global Administrator for day-to-day labeling work.
Role versus role group
A role is a named bundle of tasks. The role you will see on least-privilege exam items is Sensitivity Label Administrator : view, create, modify, and remove sensitivity labels. The read-only counterpart is Sensitivity Label Reader . Those names are roles , not the built-in groups you pick from a dropdown on day one.
A role group is a container of roles plus members. Microsoft ships Information Protection groups that already mix label work with DLP and classifiers. You can also Create role group , add only Sensitivity Label Administrator , and put the labeling operators in that custom group. To create or even view role groups, the operator needs Role Management , which ships in Organization Management , or must be a Global Administrator. Do not give every label designer Role Management.
Built-in Information Protection groups
Microsoft's get-started page lists these role groups as the Information Protection set you can use:
Role group What Microsoft documents it can do with labels Typical SC-401 use
Information Protection Full control over information protection features, including sensitivity labels and their policies, DLP, all classifier types, activity and content explorers, and related reports Too broad for a person who only designs labels
Information Protection Admins Create, edit, and delete DLP policies, sensitivity labels and their policies, and all classifier types; manage endpoint DLP settings and auto-labeling simulation Default least-privilege built-in group when the same people also own DLP/classifiers
Information Protection Analysts Manage DLP alerts and activity explorer; view-only access to DLP policies, sensitivity labels and their policies, and classifiers Operations and alert triage, not label authoring
Information Protection Investigators Analyst capabilities plus content explorer; still view-only on label definitions Investigation, not create/edit
Information Protection Readers View-only access to reports for DLP policies and sensitivity labels Reporting only
Exam trap: the get-started article lists Analysts, Investigators, and Readers next to Admins because they are the Information Protection family. Listing is not permission to create a label. Read the flyout description on the role group, or the Defender/Purview role-group table: Admins write labels; Analysts and Investigators read the configuration and work alerts; Readers see reports.
Broader compliance and security groups
Microsoft also documents that you can add users to Compliance Data Administrator , Compliance Administrator , or Security Administrator .
Compliance Administrator is a wide compliance role group. It includes Information Protection Admin among many other roles (DLP, retention, holds, communication compliance, and more). It will let someone manage labels, and it will also let them manage a large slice of Purview they may not need.
Compliance Data Administrator includes Sensitivity Label Administrator plus Information Protection Admin/Analyst/Reader and several preservation and DLP roles. Still broader than a custom label-only group.
Security Administrator inherits from the Microsoft Entra Security Administrator role. The Purview copy of this group includes Sensitivity Label Administrator . Editing the Purview copy of Security Administrator changes only security and compliance areas in these portals, not every Entra capability — but it is still the wrong answer when the stem asks for least privilege.
Organization Management can also administer labels (it includes Sensitivity Label Administrator). Global admins are automatically members of Organization Management. Microsoft's permission docs tell you not to treat that as a labeling job description.
If the item says "Contoso wants one admin to create sensitivity labels and nothing else," the best fit is a custom role group with Sensitivity Label Administrator . If the same person already owns DLP policies and classifiers, Information Protection Admins is the built-in match. If the person must also run Content explorer and DLP investigations, that is the wider Information Protection group — still not Global Administrator.
What these permissions do not cover
Label-admin rights do not replace every neighboring permission:
Applying a published label in Office, Teams, SharePoint, or Power BI is an end-user action. The user needs a work or school account, a license that includes labeling, and a label policy that publishes the label to them. They do not need Sensitivity Label Administrator.
Enabling sensitivity labels for Microsoft 365 groups is a Microsoft Entra configuration plus the Security & Compliance PowerShell cmdlet Execute-AzureAdLabelSync . That enablement is a tenant prerequisite for container labels, not a substitute for Purview label-admin roles.
Azure Rights Management super users can decrypt content for eDiscovery and recovery. That is an encryption-service role, not a Purview label designer role.
Specific features (SharePoint/OneDrive labeling, co-authoring on encrypted files, Defender for Cloud Apps labeling) document extra permissions in their own articles. Do not assume Information Protection Admins covers every connected admin center.
Admins who manage labels also need a license that includes Microsoft Purview Information Protection labeling. Microsoft publishes feature-level licensing in the Purview service description and the related PDF; the exam does not ask you to invent a dollar amount or a secret SKU code.
Administrative units
Sensitivity labels support administrative units configured in Microsoft Entra ID. Two layers matter:
Admin scoping. Edit an Information Protection role group, select a member, and use Assign admin units . That admin can then manage only users in those units.
Policy scoping. When you create a sensitivity label policy or an auto-labeling policy, you can select administrative units. For Exchange and OneDrive , only users in those units are eligible. For SharePoint , only sites in those units are eligible.
Protection policies (Fabric/data-map protection policies) do not support administrative units. Microsoft documents that AU membership accuracy is an Entra dependency. The point of AUs is least privilege; a side effect is that you can publish a France-only label policy without enumerating every French group by hand.
Worked example: your account is in Information Protection Admins and is assigned AUs for France, Germany, and Spain. You create a label policy and see only those three units. You select France and leave users and groups at the default of all. The policy targets users in the France AU as Entra membership changes. You did not need Global Administrator, and you did not publish the label to Germany by accident.
Exam traps
Global Administrator is required to create labels. It works. It is not least privilege. Microsoft's labeling article says to minimize Global Administrator.
Information Protection Analysts create labels because they are in the Information Protection family. They have view-only access to label definitions.
Help-desk staff need Sensitivity Label Administrator to apply Confidential in Outlook. Application in apps does not use that role.
Role Management belongs on every label admin. Role Management is for people who create role groups, not for people who create labels.
Confusing Compliance Administrator with Information Protection Admins. Both can administer labels. Compliance Administrator is the wide compliance hammer; Information Protection Admins is the information-protection hammer; Sensitivity Label Administrator is the scalpel.
When you can name the portal path, the difference between the Information Protection role groups , the Sensitivity Label Administrator role , and the fact that end users apply labels without those rights, you have this blueprint bullet.