Study guide
24.3 Configure DSPM for AI Policies
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
24.3 Configure DSPM for AI Policies
Key Takeaways Explain This Topic AI
Create DSPM for AI policies from Recommendations or Get started one-click actions; edit each policy later in its owning Purview solution, not by reinventing it from scratch in DSPM.
DSPM for AI - Capture interactions for Copilot experiences is a collection policy for Copilot in Fabric and Security Copilot prompts and responses; Microsoft 365 Copilot interactions still come from the unified audit log.
DSPM for AI - Capture interactions for enterprise AI apps captures prompts and responses from ChatGPT Enterprise and Entra- or Foundry-connected enterprise AI apps for eDiscovery and Data Lifecycle Management.
The network collection policy requires a manual SASE or SSE integration in Data Loss Prevention settings; content capture is off until you edit the policy, enable capture, and set Content contains classifiers to All.
Deleted one-click policies show PendingDeletion and still appear as created on recommendation cards until deletion finishes; preview-era policies may keep a Microsoft AI Hub - name prefix.
Last updated: August 2026
Configure DSPM for AI Policies
Quick Answer: Open Recommendations (or Get started) in DSPM for AI (classic), activate the one-click policies that match your AI surfaces, then use the Policies page only as a status board. Edit collection policies, DLP, Insider Risk Management, Communication Compliance, and sensitivity labels in their own solutions. For Fabric and Security Copilot prompt capture, take Secure interactions in Microsoft Copilot experiences . For enterprise apps, take Secure interactions from enterprise apps .
Configuring DSPM for AI policies is not the same as authoring a blank DLP policy. Microsoft ships preconfigured one-click policies that you activate from personalized recommendations . After they exist, they are ordinary Purview policies with DSPM-style names. SC-401 expects you to know which recommendation creates which policy , which solution owns it , what mode it starts in , and what you still have to configure by hand (SASE/SSE, content capture, label selection, scoping during a pilot).
Allow at least 24 hours after creation or default-setting changes before Reports reflect the policy. If you use administrative units, only an unrestricted administrator can create the one-click policies that apply to all users .
How one-click policies fit the rest of Purview
DSPM for AI is the front door. The policies it creates land in:
Collection policies — ingest and optionally store AI prompts and responses, and detect sensitive information on network or Edge paths
- Data Loss Prevention — detect or block sensitive content going to AI sites or being processed by Copilot
- Insider Risk Management — AI site visits and risky AI usage scoring
- Communication Compliance — unethical behavior in AI apps
- Information Protection — default sensitivity labels and label policies, skipped if you already have labels
The Policies page lists those objects and their status. To change scope, classifiers, or actions, open the owning solution. Example: matches for DSPM for AI - Unethical behavior in Copilot (Microsoft also documents the name DSPM for AI - Unethical behavior in AI apps ) are reviewed in Communication Compliance , not inside a DSPM-only queue.
Older retention policies that still use the combined location Teams chats and Copilot interactions do not appear on this Policies page. Create separate retention policies for Microsoft Copilot Experiences if you want those retention policies included there.
If you delete a one-click policy, status becomes PendingDeletion . The recommendation card can continue to show the policy as created until deletion finishes. Policies created while the feature was in preview as Microsoft Purview AI Hub keep the Microsoft AI Hub - name prefix; Microsoft does not rename them automatically.
Recommendations that create policies
Work Recommendations (Overview or the Recommendations pane). Completed or dismissed recommendations leave Overview. View all recommendations is the full list. Typical cards include:
Protect your data from potential oversharing risks — review the default data risk assessment rather than creating a policy
Protect your data with sensitivity labels — creates default labels and policies only if you do not already have them
Protect items with sensitivity labels from Microsoft 365 Copilot and agent processing — you select one or more labels; the DLP policy then blocks Copilot and agents from summarizing those labeled items
- Detect risky interactions in AI apps — Insider Risk Management risky AI usage
- Discover and govern interactions with ChatGPT Enterprise AI — register ChatGPT Enterprise workspaces
Get guided assistance to AI regulations — Compliance Manager regulatory templates (control mapping, not a DLP policy)
- Secure interactions for Microsoft Copilot experiences — collection policy for Fabric and Security Copilot
- Detect sensitive info shared with AI via network — collection policy that needs SASE/SSE
Secure interactions from enterprise apps — collection policy for Entra-registered apps, ChatGPT Enterprise connector, and Microsoft Foundry apps
Secure data in Azure AI apps and agents — setup instructions to capture prompts and responses for apps that use Azure AI subscriptions
Fortify your data security — Adaptive Protection and Edge DLP block policies
Extend your insights for data discovery — the Get started discovery set (DLP audit-mode, IRM visit detection, Edge SIT detection)
Default policies for data discovery
Policy name Type Source What it does on day one
DSPM for AI: Detect sensitive info added to AI sites DLP Extend your insights for data discovery Discovers sensitive content pasted or uploaded in Edge, Chrome, and Firefox to AI sites. All users and groups, audit mode only
DSPM for AI - Detect when users visit AI sites Insider Risk Management Extend your insights Detects browser visits to AI sites
DSPM for AI - Detect risky AI usage Insider Risk Management Detect risky interactions in AI apps Helps calculate user risk from risky prompts and responses in Microsoft 365 Copilot, agents, and other generative AI apps
DSPM for AI - Unethical behavior in AI apps Communication Compliance Detect unethical behavior in AI apps Detects sensitive information in prompts and responses across those AI apps; all users and groups
DSPM for AI - Capture interactions for Copilot experiences Collection Secure interactions in Microsoft Copilot experiences Captures prompts and responses from Copilot in Fabric and Security Copilot so eDiscovery, Data Lifecycle Management, and related solutions can manage them
DSPM for AI - Detect sensitive info shared with AI via network Collection Extend insights into sensitive data in AI app interactions Detects sensitive information shared with AI apps in browsers, applications, APIs, add-ins, and more through a SASE or SSE integration
DSPM for AI - Capture interactions for enterprise AI apps Collection Secure interactions from enterprise apps Captures prompts and responses from enterprise AI such as ChatGPT Enterprise and apps connected through Microsoft Entra or Microsoft Foundry
DSPM for AI - Detect sensitive info shared in AI prompts in Edge Collection Extend your insights Detects prompts to generative AI apps in Edge and finds sensitive information in prompt contents. All users, audit mode, does not capture content
Collection policies and content capture
Collection policies are the SC-401 center of this skill. They filter which events Purview ingests . DSPM one-click actions create collection policies for you; you can later open them under Data Loss Prevention > Classifiers > Collection policies or Information Protection > Classifiers > Collection policies and edit them like any other collection policy.
Content capture for AI interactions stores detected prompts and responses from generative AI data sources added to the policy. It does not include content in files shared with generative AI. Microsoft documents that capture applies to Copilot experiences , Enterprise AI , unmanaged cloud apps categorized as generative AI , and the all unmanaged AI apps adaptive app scope. Without capture, detection is limited to sensitive information only .
To capture AI content you must set the Content contains classifiers condition to All . The one-click network policy does not select content capture when it is auto-created. If the exam says you see SITs but not full prompts from a network or Edge collection policy, edit the policy and enable capture (and set classifiers to All). The Edge discovery policy is explicitly audit mode and does not capture content until you change it.
DSPM for AI - Detect sensitive info shared with AI via network has a second manual step: add one or more SASE or SSE integrations in Data Loss Prevention settings . Detection depends on the network partner implementation. Creating the named policy without the integration produces an empty signal path.
Microsoft 365 Copilot prompt capture is not this Fabric/Security Copilot collection policy. Copilot in Microsoft 365 continues to flow through audit . Know both pipelines so you do not disable the wrong object when a privacy team asks you to stop storing prompts.
Default policies that protect data in generative AI
Policy name Type Source Day-one behavior
DSPM for AI - Block sensitive info from AI sites DLP Fortify your data security Adaptive Protection block-with-override for elevated risky users pasting or uploading sensitive information to other AI apps in Edge, Chrome, and Firefox. All users, test mode
DSPM for AI - Block elevated risk users from submitting prompts to AI apps in Microsoft Edge DLP Fortify your data security Adaptive Protection blocks elevated, moderate, and minor risk users from putting information in AI apps in Edge. Includes unmanaged apps , so included users are blocked from using unprotected browsers
DSPM for AI - Block sensitive info from AI apps in Edge DLP Fortify your data security Inline detection of a selection of common SITs; blocks prompts to AI apps in Edge; also includes unmanaged apps
DSPM for AI - Protect sensitive data from Copilot processing DLP Protect items with sensitivity labels from Microsoft 365 Copilot and agent processing Blocks Microsoft 365 Copilot and agents from processing items that have the sensitivity labels you selected
Sensitivity labels and policies Information Protection Protect your data with sensitivity labels Creates Microsoft’s default labels and policies; skipped if labels already exist
Default policies that use Adaptive Protection turn Adaptive Protection on if it is not already on, using default risk levels for all users and groups . That is a side effect you must expect: taking Fortify your data security is not “just a test DLP rule.”
After creation, scope the policies to a pilot group, add or remove classifiers, or move DLP from test/audit to enforce — in the DLP or collection-policy UI. DSPM will not magically keep a second copy of the settings.
Scenario: enterprise ChatGPT versus consumer ChatGPT
A bank allows ChatGPT Enterprise and wants prompts available to eDiscovery. Take Secure interactions from enterprise apps , which creates DSPM for AI - Capture interactions for enterprise AI apps , and complete ChatGPT Enterprise workspace registration if that recommendation is shown. Consumer ChatGPT in a browser is Other AI apps / third-party sites: you need devices, the browser extension, Extend your insights, and possibly endpoint or Edge DLP. Do not expect the enterprise collection policy to see unmanaged consumer sessions.
Exam traps
One-click is not “set and forget” for the network policy. SASE/SSE integration is manual.
Content capture is a collection-policy checkbox plus classifiers = All , not a separate DSPM product.
Protect sensitive data from Copilot processing is a DLP policy driven by labels you pick , not a magical block of all Copilot.
Audit mode and test mode are not the same as block. The discovery DLP policy starts in audit; the Adaptive Protection paste policy starts in test.
Do not edit from memory inside DSPM. Follow the Policies page into DLP, IRM, Communication Compliance, or collection policies.
Official references: One-click policies , Collection policies .