Study guide
23.1 Implement Purview Controls for AI Services
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
23.1 Implement Purview Controls for AI Services
Key Takeaways Explain This Topic AI
Copilot is permission-trimmed first; sensitivity labels add an extra layer, and encryption requires both VIEW and EXTRACT before Copilot can return item text
Enable sensitivity labels for SharePoint and OneDrive or encrypted files Copilot can use are limited to data in use from Office apps on Windows
The Microsoft 365 Copilot and Copilot Chat DLP location exists only on a Custom policy, cannot be combined with other locations, and cannot mix SITs and sensitivity labels in the same rule
Labeled items excluded by Copilot DLP can still appear in citations; files uploaded into a prompt are not inspected—only typed prompt text is
DSPM for AI is the operational front door for AI discovery and one-click policies; its prerequisites, roles, policy setup, and monitoring are the next chapter
Last updated: August 2026
23.1 Implement Purview Controls for AI Services
Quick Answer: Microsoft 365 Copilot and Copilot Chat honor existing Microsoft 365 permissions. Sensitivity labels add markings plus Azure Rights Management checks: the user needs VIEW and EXTRACT (Copy and extract content) before Copilot can return item text. Use a Custom Data Loss Prevention (DLP) policy with the Microsoft 365 Copilot and Copilot Chat location to stop Copilot from processing labeled files and emails, from answering prompts that contain sensitive information types (SITs), or from sending those prompts to external web search. Endpoint DLP still covers paste into third-party AI sites in a browser. Data Security Posture Management (DSPM) for AI is the next chapter—do not treat this skill as DSPM policy authoring.
Microsoft 365 Copilot, Microsoft 365 Copilot Chat, Security Copilot, Copilot Studio, Copilot in Fabric, and other generative AI apps do not invent a new information-protection product. They consume mailboxes, SharePoint and OneDrive files, Teams content, and data in use (a file already open in Word, Excel, PowerPoint, or Outlook), including files stored outside the tenant on a local disk, network share, USB drive, or another cloud. The SC-401 bullet is to implement Microsoft Purview controls so that AI grounding and summarization cannot extract what the user should not copy—even when Graph already granted read access.
That last point is the exam's mental model. Copilot is fast oversharing, not a backdoor. A user who can open a loosely permissioned HR library can now ask Copilot to summarize every resume in seconds. Labels, encryption usage rights, DLP, and classification are how you stop extract , after access is already true.
Access first, then protection
AI apps that Microsoft Purview supports use existing controls so tenant data is never returned to the user or used by a large language model if the user does not have access to that data. When your organization's sensitivity labels are on the content, Microsoft documents an extra layer:
With a file open in Word, Excel, or PowerPoint—or an email or calendar event open in Outlook—the app shows the label name and any header, footer, or watermark markings. Loop components and pages use the same sensitivity labels.
When the label applies encryption, the user must have EXTRACT as well as VIEW for Copilot or agents to return the data.
The same encryption check applies to data in use outside Microsoft 365 when the file is open in an Office app.
Enable sensitivity labels for Office files in SharePoint and OneDrive before a Copilot rollout. If you skip that, encrypted files that Copilot and agents can access are limited to data in use from Office apps on Windows . At-rest labeled files in SharePoint and OneDrive will not participate the same way.
Copilot and agents recognize your tenant's labels, not another organization's labels on incoming files. Container labels on Teams, Microsoft 365 Groups, SharePoint sites, Loop workspaces, and Viva Engage are not inherited by items in those containers. A Teams channel summary therefore will not display the team's Confidential container label unless the messages or files themselves are labeled as items.
EXTRACT, encryption without labels, and hard stops
The usage right that maps to copying text is EXTRACT , shown in the Purview portal as Copy and extract content (EXTRACT) . If content grants VIEW but not EXTRACT, Copilot will not summarize it; it may still emit a link so the user can open the item outside Copilot. Full control (OWNER) includes EXTRACT. The person who applied encryption is the Rights Management owner and always has EXTRACT for their own files, so Copilot can still return content that user encrypted themselves.
When you configure a label to assign permissions now, preset levels such as Editor include EXTRACT; custom Reviewer -style bundles often omit Copy. If you let users assign permissions, Outlook Encrypt-Only includes EXTRACT; Do Not Forward does not include FORWARD and typically blocks copy. In Word, Excel, and PowerPoint, user-defined Read without copy omits EXTRACT. User-defined permissions can block Copilot from extracting unopened SharePoint or OneDrive documents unless the label is used as a default that extends SharePoint permissions to downloaded documents, or the user directly references the file with / and still has EXTRACT. Copilot can always use those documents when they are already open in the app. Microsoft also documents that Copilot agents cannot read files that have user-defined sensitivity label permissions in the typical at-rest path.
Encryption from the Azure Rights Management service can exist without a sensitivity label (Microsoft Purview Message Encryption, Office Information Rights Management, the Rights Management connector, or the RMS SDK). Copilot still checks VIEW and EXTRACT, but new items do not inherit a label . Microsoft's guidance is to protect with labels that apply encryption so inheritance works.
Other encryption methods:
- Protection Copilot behavior (as Microsoft documents it)
- Label encryption with VIEW + EXTRACT Content can be returned and used for grounding
- Label encryption with VIEW only No summarization; possible link/citation path
Double Key Encryption (DKE) Copilot cannot access the data; Copilot is unavailable in the app if a DKE item is open
S/MIME-protected email Not returned; Copilot is not available in Outlook while an S/MIME message is open
Password-protected Office file Inaccessible unless already open in the same app; the password is not inherited by generated content
Customer Key or BYOK Supported; items remain eligible to be returned, as with eDiscovery and search
SharePoint library IRM that blocks copy Usage rights apply at download , not at create/upload; use a label without EXTRACT if you must block at-rest summarization
An advanced PowerShell setting on sensitivity labels can prevent Office apps from sending content to connected experiences , which includes Microsoft 365 Copilot and agents. Treat that as a blunt per-label brake, not a substitute for EXTRACT design.
When Copilot generates new content from labeled sources, the highest-priority sensitivity label is displayed in Copilot Chat and is inherited when supported. Unlike some auto-labeling paths, an inherited Copilot label can replace a lower-priority label that was applied manually . Inheritance does not apply when encryption used user-defined permissions or was applied independently from the label. Inheritance also fails if the destination is read-only, the user lacks EXPORT or FULL CONTROL on an already-encrypted destination, or the inherited label is not published to the user. Sensitivity labels on Teams meetings and chat are not currently recognized by Copilot (meeting invites, responses, and calendar events that are labeled still apply to the invite body, not to metadata such as time and attendees). Plugins and Microsoft Graph connectors generally do not honor sensitivity labels on external sources.
DLP for Microsoft 365 Copilot and Copilot Chat
Create the policy from the Custom template. On Locations, turn on Microsoft 365 Copilot and Copilot Chat . Selecting that location disables every other location in the same policy. Admin units are not supported . Updates can take up to four hours . DLP alerts, notifications, and simulation mode are supported.
You cannot combine Content contains > Sensitive information types and Content contains > Sensitivity labels in the same rule. Put each condition in its own rule in the same policy.
Condition Action What Copilot does
Content contains > Sensitivity labels Prevent Copilot from processing content File or Exchange email content is not used in the response; the item can still appear in citations
Content contains > SITs Prevent Copilot from processing content > Processing prompts No response; prompt is not used for internal or web search (preview; rolling out; check your tenant)
Content contains > SITs Prevent Copilot from processing content > Performing Web Searches External web search is blocked; Copilot may still answer from internal Microsoft 365 sources the user can access
Email is received from > External users Prevent Copilot from processing content External mail is excluded from grounding, summarization, and citation; sender domain vs accepted domains only —the body is not inspected (preview)
Labeled-item coverage includes stored files and files that are actively open (file types supported by sensitivity labels) and emails sent on or after January 1, 2025 . Calendar invites are not supported . In Word, Excel, and PowerPoint the policy is evaluated at file open ; a label applied mid-session is enforced the next time the file is opened. Skills that would reference file content are disabled; some experiences that do not use a large language model or file content may still appear.
Files uploaded into a prompt are not scanned. DLP evaluates only the text the user types. If the exam scenario is “user attaches a spreadsheet to the prompt,” this location does not inspect that file.
Accounts that can create or edit these policies include Microsoft Entra AI Admin , Purview Data Security AI Admin (edits Copilot-related DLP and can view AI content in DSPM but cannot read prompts and responses ), the Purview Data Security AI Admins group, Purview Compliance Administrator, Compliance Data Administrator, Information Protection / Information Protection Admin, Security Administrator, and Global Admin. Use least privilege. Global Admin is listed because it works, not because it is the design pattern.
Windows devices onboarded to Purview can use Endpoint DLP to warn or block paste of sensitive information into third-party generative AI sites in a browser (for example ChatGPT). Microsoft 365 Copilot Chat ( web version) also documents Endpoint DLP actions to block paste of sensitive content and to block files based on a specified sensitivity label. That is a device/browser control plane. The Copilot policy location is a Microsoft 365 Copilot processing control plane. You typically need both: one stops consumer AI exfiltration, the other stops Copilot from grinding Highly Confidential files into a Work chat answer.
Classification, audit, eDiscovery, and retention—without stealing DSPM
SITs and trainable classifiers can find sensitive data in prompts and responses. Those hits surface in Purview reports and in DSPM activity explorer on the AI activities tab. DSPM for AI (and DSPM) is the graphical front door with data risk assessments and one-click policies. Prerequisites, DSPM roles, configuring DSPM policies, and monitoring DSPM activities are the next chapter. This chapter's job is to know that Copilot protection still depends on the labels, DLP, audit, and retention you already operate.
Prompts and responses are stored in the user's mailbox and captured in the unified audit log , including the Microsoft 365 app (Copilot in Word, Copilot in Teams, Microsoft 365 Chat), referenced files, and labels on those files. Audit is built for security and compliance investigations, not as the official Copilot usage report—use the Microsoft 365 admin center Copilot usage report or Viva Insights for usage metrics. Auditing Copilot search is not the same as capturing the prompt and response text; use eDiscovery (mailbox source, condition Type contains Copilot activity ) or DSPM AI interaction views for content. Retention policies for Copilot and AI apps retain or delete those mailbox-stored interactions using the same principles of retention as other locations. Communication compliance can detect sensitive or inappropriate generative AI interactions. Insider Risk Management's Risky AI usage template (prompt injection and accessing protected materials) still applies; you configured IRM earlier—here it is one more Purview control that fires on AI usage.
Channel Agent in Teams honors EXTRACT for the requesting user but does not check every channel member, so a summary could include content some members cannot open. Microsoft also documents that you cannot use the Copilot DLP location to prevent Channel Agent from summarizing labeled files the same way. Do not assume every Copilot-family surface shares every DLP action.
Exam traps
Access is not extract. Everyone-except-external on a site is still summarizable until labels, DLP, or workload discovery controls intervene.
DKE and S/MIME are hard stops; Customer Key is not.
The Copilot DLP location cannot share a policy with Exchange or SharePoint locations.
Citations can still list a file whose content was excluded.
External-email DLP is metadata-only (preview).
Do not spend this skill configuring DSPM one-click policies—that is the following chapter.