Study guide
11.1 Device Requirements for Endpoint DLP Including Extensions
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
11.1 Device Requirements for Endpoint DLP Including Extensions
Key Takeaways Explain This Topic AI
Endpoint DLP covers onboarded Windows 10/11 devices, macOS on the three latest released major versions, and Windows Server 2019 and later — not Domain Controllers and not Server Core
Microsoft Defender Antivirus real-time protection and behavior monitoring must be enabled; other Windows Security components do not have to be active, and the anti-malware client must be 4.18.2110 or newer (N-2)
Onboarding is shared with Microsoft Defender for Endpoint; devices must be Microsoft Entra joined, hybrid joined, or registered, and you turn on device monitoring in the Purview portal
The Microsoft Purview extensions for Chrome and Firefox are Windows-only; Microsoft Edge is native, and macOS does not need those extensions to enforce Endpoint DLP
Windows servers are onboarded but Endpoint DLP stays off until you enable Endpoint DLP support for onboarded servers; classification on servers is disabled after the supported server KBs
Last updated: August 2026
The July 28, 2026 SC-401 outline asks you to specify device requirements for Endpoint DLP, including extensions . That is a prerequisites bullet. A perfect Devices-scoped DLP policy still does nothing on a laptop that is not onboarded, that has Microsoft Defender Antivirus real-time protection off, or that uploads through Chrome without the Purview extension. Microsoft's Learn about Endpoint DLP article (updated 2026-08-05) and Onboard Windows devices overview (updated 2026-06-26) are the current facts to study.
Endpoint data loss prevention (Endpoint DLP) extends Microsoft Purview DLP to sensitive items that live on the device. After onboarding, the service can see what users do with those items and enforce DLP policy actions. Classification is not continuous OCR of the whole disk. Endpoint DLP fully scans a file for sensitive information types and labels when the file is created or modified . When an already classified file is read , it checks whether policies, rules, or SITs changed and re-evaluates, but it does not re-extract text. It cannot read a sensitivity label applied by another tenant . If the user never saves the data to a local file — for example Word content written straight to a USB stick — Endpoint DLP cannot classify or block that unsaved stream. That last trap belongs with the rule activities in the next section; the requirement here is that the device is even eligible.
Licensing is not a fake SKU on this exam. Microsoft's getting-started page points to Microsoft 365 Enterprise plans and the Purview service description. Say the tenant must be licensed for Endpoint DLP. Do not invent E5-only wording Microsoft does not publish on that page.
Operating systems Microsoft actually lists
Microsoft's current client list is Windows 10 , Windows 11 , and macOS (the three latest released major versions) . Do not pin a macOS marketing name such as Catalina unless the service description you are citing still uses it; the Endpoint DLP Learn articles now say three latest released major versions . macOS devices with x64 and Apple silicon (M1, M2, M3 / ARM64) are supported. On Windows ARM64, onboarding documents Windows 11 21H2 through 24H2; do not assume every Windows 10 ARM image is in that table.
Windows Server 2019 and later can be onboarded (the Windows overview also lists Windows Server 2022 from 21H2). Two hard exclusions: Endpoint DLP is not supported on Windows Servers configured as Domain Controllers , and not supported on Windows Servers installed with the Core Server option. Installing the supported Windows Server KBs disables the Classification feature on the server . Endpoint DLP will not classify files on that server after those KBs. It will still protect files that were already classified before the KBs, if you install Microsoft Defender version 4.18.23100 (October 2023) or later . By default, Endpoint DLP is not enabled for Windows servers when they first onboard. You must turn on Endpoint DLP support for onboarded servers in Endpoint DLP settings before Activity explorer shows server events. The same DLP policies can then apply to Windows PCs and those servers.
Defender Antivirus, identity, Office, and network
Microsoft's Prepare your Windows devices list is the exam checklist:
Requirement What Microsoft currently documents
Anti-malware client Version 4.18.2110 or newer . Check Windows Security > Settings > About. After a new client or engine ships, versions older than N-2 are unsupported. Update with KB4052623 if you are behind.
Real-time protection and behavior monitoring Must be enabled. None of the other Windows Security components need to be active. Endpoint DLP is not supported with Microsoft Defender Antivirus disabled. If a third-party antivirus puts Defender in passive mode, real-time protection and behavior monitoring still need to be on for DLP-specific functions — they do not replace that third-party product's malware blocking.
Device identity Microsoft Entra joined , Microsoft Entra hybrid joined , or Microsoft Entra registered .
Microsoft 365 Apps A supported, current build. For the most robust protection, 16.0.14701.0 or later . Office 365 needs KB 4577063. Monthly Enterprise Channel 2004–2008 must move to 2009 or later.
Proxy and allowlisting Devices must reach the cloud DLP service. Allow MpDlpService.exe through firewalls, third-party antivirus, and application control.
Chrome and Firefox extensions raise the anti-malware floor to 4.18.2202.x or later on Windows 10 x64 build 1809 or later . Feature-specific floors keep moving (for example hyperlinks in toast messages at 4.18.25010, Teams Endpoint DLP at 4.18.25050). If the stem names a roadmap feature, match the published client version; do not invent one.
Onboard the device, then turn monitoring on
Device management is the telemetry pipe for Endpoint DLP and Insider Risk Management. Open the Microsoft Purview portal > Settings > Device onboarding > Devices . Enable device onboarding / device monitoring, then download a package. Deployment methods Microsoft documents: Microsoft Intune , Microsoft Configuration Manager , Group Policy , a local script (up to 10 machines) , and VDI scripts for non-persistent machines. macOS uses Intune , Jamf Pro , or another MDM; if the Mac is already in Microsoft Defender for Endpoint, the extra steps shrink. After Windows device monitoring is on, macOS still needs Turn on macOS device monitoring .
Onboarding is shared with Microsoft Defender for Endpoint . Machines already in MDE appear in the Purview devices list — you still turn on device monitoring , but you do not onboard them twice. Onboarding in Purview also onboards into MDE. Microsoft says enablement often takes about 60 seconds ; wait up to 30 minutes before opening a support case. Offline onboarded devices remain on the list for 180 days .
Device management currently supports Microsoft Entra roles, not Purview roles. To enable device management, the account needs Security admin , Compliance admin , or Global admin . Viewing settings, opening onboarding/offboarding, and toggling monitoring have overlapping Entra-role lists (Compliance admin / Security admin / Global admin, plus Compliance data admin and Global reader for some view tasks). Do not answer this bullet with Information Protection Admin from the DLP-policy chapter.
Virtual desktops can onboard with the same packages. Microsoft publishes support for Azure Virtual Desktop, Windows 365, Citrix Virtual Apps and Desktops 7 (2209+), Amazon WorkSpaces, and Hyper-V on named Windows 10/11/Server combinations. Two published gotchas: you cannot monitor Copy to clipboard or enforce Endpoint DLP via browsers on AVD — the same egress is monitored over Remote Desktop Session ; Citrix XenApp does not support access-by-restricted-app monitoring. In those virtualized environments, USB storage is treated as a network share , which is a rule-activity fact for the next section.
Browser extensions are part of the device requirement
Microsoft Edge on Windows has the deepest Endpoint DLP integration (print the site, copy from the site, save-as, paste to supported browsers, upload to a restricted cloud service domain). Google Chrome and Mozilla Firefox on Windows need the Microsoft Purview extension . Microsoft's Chrome article is explicit: the extension only works on Windows devices ; you do not need it to enforce DLP on macOS . On macOS (three latest majors) Endpoint DLP documents Microsoft Edge , Safari , Chrome , and Firefox (latest versions) without that Windows extension package.
- Browser Windows macOS
- Microsoft Edge Native Endpoint DLP; no Purview extension Supported (latest)
Google Chrome Purview Chrome extension (Chrome Web Store / Intune / Group Policy force-install). Extension ID echcggldkblhodogklpincgchnpgcdco . Manifest V3 auto-upgrade to 3.0.0.239 or higher . User command access is a prerequisite. DLPEngine caches files for about 15 minutes by default. Latest version; Windows extension not required
Mozilla Firefox Purview Firefox extension; incognito mode is not supported and must be disabled Latest version; Windows extension not required
Safari Not the Windows extension story Latest version, macOS only
Unallowed browsers list Restrict by executable name (for example chrome.exe ) Restrict by full path from Activity Monitor > Open Files and Ports
If you force-install Chrome or Firefox org-wide, remove that browser from the unallowed browsers and unallowed apps lists . The extension bypasses those lists on machines where it is installed, but leaving Chrome on the unallowed list while you test a handful of machines is the supported mixed mode. If Chrome has a NativeMessageBlocklist, add the Purview extension to NativeMessageAllowlist.
Service-domain upload controls (next two sections) apply to files uploaded with Edge , or with Chrome or Firefox that have the Purview extension . An unallowed browser that tries to open a file matching a block or block-with-override cloud-upload rule is blocked and the user is told to open the file in Edge.
What this section does not configure
Just-in-time protection can hold egress until evaluation finishes; Activity explorer starts receiving audit events even before you deploy a Devices policy. Both are real. Both are the next chapter . Here, your job is: OS + Defender RTP/behavior monitoring + Entra device identity + onboarding/monitoring + the right browser extension story. If any of those are missing, advanced DLP rules and Endpoint DLP settings have nowhere to run.