Study guide
10.3 Create File Policies in Defender for Cloud Apps Using DLP
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
10.3 Create File Policies in Defender for Cloud Apps Using DLP
Key Takeaways Explain This Topic AI
SC-401 still tests creating Microsoft Defender for Cloud Apps file policies that use DLP inspection even though Microsoft has published a retirement date of January 6, 2027
A Purview DLP policy scoped to the Instances location is automatically created as the same policy in Defender for Cloud Apps; you can also create a File policy in the Defender portal and set inspection to Data Classification Service
File policies are API-based at-rest controls with more than 20 metadata filters, a tenant limit of 50, and Data Classification Service using the same sensitive-information engine as Purview DLP
Purview locations SharePoint sites and OneDrive accounts cover those Microsoft 365 apps natively; use Instances / connected apps for non-Microsoft SaaS such as Box, Dropbox, Google Workspace, and Salesforce
Do not run equivalent MDCA file policies and Purview DLP policies at the same time; Microsoft documents enforcement conflicts, and after migration you disable then delete the file policies
Last updated: August 2026
The July 28, 2026 SC-401 outline still includes Create file policies in Microsoft Defender for Cloud Apps by using a DLP policy . Teach the skill. Also teach the current product news: Microsoft’s Defender for Cloud Apps Learn pages (file policies, commonly used information protection policies, DLP content inspection, What’s new, and Migrate file policies to Microsoft Purview, the last updated 2026-08-07 ) state that file policies retire on January 6, 2027 . Partner Center’s July 2026 announcement uses the same date: after January 6, 2027, file policies configured in Defender for Cloud Apps will no longer be supported or enforced . File-based data protection is moving to Microsoft Purview DLP and auto-labeling . Defender for Cloud Apps keeps SaaS discovery, posture management, app governance, and threat detection. Session policies are a different control; they are not the file-policy retirement.
Until that date, you still create and operate file policies. After it, you need the Purview equivalents. SC-401 can ask either side.
Two supported ways to “use a DLP policy”
Path A — Purview DLP creates the MDCA policy. Connect the non-Microsoft app in Defender for Cloud Apps first (documented connectors include Box , Dropbox , Google Workspace , Salesforce , and Cisco Webex ). In the Microsoft Purview portal , create a DLP policy (Custom is the usual template for Instances). On Locations , turn Instances on. Edit the location, choose Specific instances , and Include instances for the connected apps — or include none, which scopes the policy to all connected apps in the MDCA tenant. Build the rule (SITs, sharing, and so on). Under actions, use Restrict Third Party Apps and pick listed apps. Microsoft’s non-Microsoft cloud apps DLP article states: when you create a DLP policy scoped to Instances, the same policy is automatically created in Microsoft Defender for Cloud Apps. That sentence is the exam wording almost verbatim. Role groups that can create that DLP policy include Compliance administrator, Compliance data administrator, Information Protection, Information Protection Admin, and Security administrator. Instances do not support administrative units. Data state is at rest .
Path B — File policy in the Defender portal with DLP inspection. In the Microsoft Defender portal , go to Cloud Apps > Policies > Policy management , open the Information Protection tab, Create policy , and choose File policy . Default Category is DLP . Give it a name, severity, and filters. Set Inspection method to Data Classification Service (DCS) (Microsoft recommends DCS). DCS is the same classification engine Purview DLP uses for sensitive information types: pick the SIT (or GDPR-style EU identifier types), set a minimum number of content violations (for example 10 credit card numbers), and optionally exclude a regex for an internal classification keyword. You can inspect content, metadata, and/or file name; the default is content and metadata . Matches are masked with “X” and shown with 100 characters of context; numbers in context become “#” and are not stored. Unmask the last four characters of a match is optional. You can also inspect protected files . Third-party DLP or anti-malware engines can extend inspection; that is optional, not the exam default.
The first file policy in a tenant requires Microsoft Entra Service Principal permissions; those permissions are granted automatically only when no file policy exists yet. Later policies do not need that grant again. You are limited to 50 file policies per tenant. Purview’s published ceilings after migration are 10,000 information protection and governance policies and 600 DLP rules per tenant — do not invent other numbers. If file monitoring is enabled but no file policy exists or all are disabled for seven consecutive days , file monitoring is autodisabled ; create or re-enable at least one file policy to keep monitoring on.
File policy anatomy versus Purview locations
A file policy is API-based . It continuously scans connected cloud apps for files that already exist and for new content. It is not Exchange/Teams in-motion DLP and not Endpoint DLP. Microsoft documents content inspection across 100+ common file types (Office, Open Office, compressed files, rich text, XML, HTML, and more) and more than 20 metadata filters.
Piece What you configure
File filters App, access level (internal / external / shared / public / public with a link), collaborators, owner, extension, file name, file ID, MIME type, file type, sensitivity label, parent folder, created/last modified, in trash, quarantined, matched policy, owner OU (Google Drive)
Apply to All files, all files excluding selected folders, or selected folders for Box, SharePoint, Dropbox, or OneDrive
- User groups All file owners, owners in selected groups, or all owners excluding selected groups
- Content inspection DCS / preset expressions / custom regex; minimum match count; masking
Alerts Per-match alert at the policy severity, email, daily alert limit (governance actions are not capped by that limit), Power Automate
Governance actions Collaboration, security, and investigation actions that vary by cloud app — remove external users, remove public access, make private, user or admin quarantine, apply a sensitivity label, trash/delete, and others
Only the governance action of the first triggered policy is guaranteed. If file policy 1 applies a sensitivity label, file policy 2 cannot apply a different label to the same file. Narrow filters; use Edit and preview results . The Contains filter matches complete words separated by punctuation; spaces/hyphens behave like OR unless you quote strings.
Access-level and ownership traps: OneDrive treats files an external user dropped into your tenant as internally owned , so MDCA does scan them. Google Drive, Box, and Dropbox treat externally owned files as outside your legal ownership; MDCA does not have access. In trash does not apply to SharePoint and OneDrive. Sensitivity-label filters on file policies apply to Microsoft Office files only . Apply sensitivity label as a governance action is currently supported for Box, Google Workspace, SharePoint Online, and OneDrive for Business , and the label must already be published in Purview. Supported Office/PDF types for applying labels are listed in the Purview integration article; PDF needs unified labels .
Where Purview DLP already covers the app
- Connected app / location Prefer this after (and, for Microsoft 365, often before) retirement
- SharePoint Online Purview DLP location SharePoint sites
- OneDrive for Business Purview DLP location OneDrive accounts
Box, Dropbox, Google Workspace, Salesforce, other connected SaaS Purview DLP Instances (today also MDCA file policies)
Exchange / Teams / Devices Purview DLP locations — not MDCA file policies
Microsoft’s migration table maps MDCA Access level External or Public to Purview Content is shared from Microsoft 365 with people outside my organization , DCS inspection to Content contains SITs , custom regex to custom SITs , minimum violation count to SIT instance count, and file name/extension to document name / file extension conditions. Parent folder becomes site-level scoping only — Purview has no folder-level equivalent. File ID has no Purview equivalent. Sharing remediation in Purview blocks future access ; it does not always strip existing sharing the way MDCA Remove external users does — Microsoft points at Restrict access plus Power Automate when you need to unwind sharing. Trash or delete file , expire shared link , and transfer file ownership have no direct Purview DLP equivalent.
Important: Policies in Defender for Cloud Apps and Purview cannot coexist. Running equivalent policies in both products at the same time creates enforcement conflicts . Validate Purview in simulation mode , turn Purview on, then set the MDCA file policy to Disabled (do not delete yet), confirm protection, then delete the file policy.
Build the classic DLP file policy, then plan the 2027 move
Common exam/lab pattern from Microsoft’s information-protection policy article:
Connect at least one app with an app connector .
Create a File policy .
Set Access Level equals Public / Public (Internet) / External if the story is oversharing.
Set Inspection method to DCS and pick the SIT (or set Sensitivity label equals Confidential if the story is labeled data).
Set governance: for Google Workspace, Remove external users and Remove public access are the documented examples; for labeling at rest, Apply sensitivity label on supported apps.
Create the policy and review matches (Matching now versus History up to six months ).
Split migration work by purpose: DLP detection and response file policies become Purview DLP ; apply label file policies become Purview auto-labeling (auto-labeling does not backfill unchanged files — use on-demand classification for at-rest catch-up). Recreate each MDCA file policy as one or more Purview DLP rules because Purview policies contain multiple rules and MDCA file policies do not. Purview gains simulation mode , which file policies never had.
After migration, DLP matches live in Purview > Data loss prevention > Alerts and Activity explorer ; auto-labeling matches live under Information protection; incidents can still appear in the Defender portal. File-policy alerts remain a later SC-401 bullet; this section is create , not respond .
Do not invent unpublished file-policy limits beyond the 50 -policy cap, the seven-day monitoring autodisable, the query-size warning on huge collaborator filters, and the first-policy Service Principal requirement. When you can create the Instances DLP policy that auto-stamps MDCA, build a DCS file policy in the Defender portal, contrast those API file policies with Purview SharePoint/OneDrive locations, and cite January 6, 2027 without dropping the exam skill, you have this blueprint bullet.