Study guide
12.2 Monitor Endpoint Activities
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
12.2 Monitor Endpoint Activities
Key Takeaways Explain This Topic AI
Activity explorer is a 30-day transformed view of Microsoft 365 unified audit log data and is not real-time; confirm a missing event independently in Audit search.
The Devices list is the health surface: Last seen, Configuration status, and Policy sync status (Updated, Not updated, or Not available).
Purview DLP alerts remain on the DLP Alerts dashboard for 30 days and in the Microsoft Defender portal for six months; JIT block events do not generate alerts.
Always audit file activity for devices (on by default for Office, PDF, and CSV) records create, modify, rename, and create-on-USB or create-on-network-share even when no DLP rule matched.
Common restrictable activities include copy to USB, copy to network share, print, clipboard, cloud upload, Bluetooth, and RDP on Windows; create and rename are auditable only.
Last updated: August 2026
12.2 Monitor Endpoint Activities
Quick Answer: After devices are onboarded, Endpoint DLP telemetry shows up in three different places . Activity explorer is a 30-day , not real-time view built from the Microsoft 365 unified audit log . Audit search is the source of those records and is how you independently confirm an activity. The Devices list ( Settings > Device onboarding > Devices ) is the health surface: Last seen , Configuration status , and Policy sync status . Policy-match alerts go to the DLP Alerts dashboard ( 30 days in Purview, six months in Microsoft Defender). JIT holds are Activity explorer events , not alerts.
Why monitoring is a separate SC-401 skill
Configuring Endpoint DLP and JIT does not prove they are working. SC-401 expects you to pick the right console for the question:
A user copied a labeled file to USB an hour ago —start in Activity explorer , and if the row is missing, Audit search.
A policy never fires on a laptop—open the Devices list and check Last seen , Configuration status , and Policy sync status .
An investigator needs to triage a policy match —use the DLP Alerts dashboard (or Defender, where the same alert lasts longer).
Leadership asks whether laptops are ready for JIT —use Settings > Device onboarding > Device report , not Activity explorer.
Mixing those surfaces is a common exam distractor. Activity explorer does not show whether a device received the latest policy. The Devices list does not show DLPRuleMatch contextual text. Alerts do not list every audited copy.
Activity explorer: 30-day activity view
Activity explorer lives in the Microsoft Purview portal (Information Protection / data classification, and as a tab on the DLP page). Microsoft documents that:
Data comes from the Microsoft 365 unified audit logs , then is transformed for the Activity explorer UI.
The UI reports up to 30 days of data.
It is not a real-time view . For core services (Exchange, SharePoint, OneDrive, and Teams), allow 60 to 90 minutes . Other services can take longer; Microsoft does not guarantee a specific availability time.
Devices report endpoint activities only while they are online. An offline device backfills after it reconnects.
Once a device is onboarded, audited activities flow into Activity explorer even before you deploy any DLP policy that includes Devices .
Preconfigured filter sets that matter for Endpoint DLP include Endpoint DLP activities , Egress activities , Files containing sensitive info types , DLP policies that detected activities , and DLP policy rules that detected activities . You can also filter on activity type, location, user, device name, client IP, sensitivity label, and whether the item is protected. Filter dropdown values are generated from the first 500 records for performance; some values may be missing from the dropdown even if they exist in the data. For endpoint events, Activity explorer surfaces the most restrictive DLP rule, and filters operate on that rule.
Example device activities Microsoft lists include deletion, creation, copy to clipboard, modify, read, print, rename, copy to network share, and access by an unallowed app.
When a DLP rule matches, look at two adjacent rows :
The user activity (for example CopyToClipboard or CloudEgress) carries policy context.
The DLPRuleMatch event carries the contextual summary —the text surrounding the matched content, such as digits around a credit card number.
For that contextual summary on Windows endpoints, Microsoft requires KB5016688 (Windows 10) or KB5016691 (Windows 11) or later, and advanced classification must be enabled. JIT events are different: they show JIT triggered = true and do not raise DLPRuleMatch or an alert.
Activity explorer is not where you prove a device is healthy. If a recent copy is missing, first confirm it is inside the 30-day window, wait for audit-log latency, confirm the device is online (or has reconnected), then search Audit . An empty view right after you publish a policy usually means the pipeline has not caught up, not that the policy failed.
Purview Audit versus Activity explorer
All DLP monitored activities are recorded to the Microsoft 365 audit log by default and routed to Activity explorer. That sentence is the relationship you should memorize:
Surface What it is for Retention Microsoft publishes here
Activity explorer Filtered, analyst-friendly view of labeling and DLP activities, including endpoint egress Up to 30 days in the Activity explorer UI
Audit search Source of record; independent confirmation; longer investigations Tenant audit retention (Standard versus Premium licensing is a later blueprint topic—do not invent a number on this skill)
Devices list Onboarding health, Last seen , configuration, policy sync Point-in-time device attributes, not a 30-day activity feed
DLP Alerts dashboard Triage of policy-match alerts 30 days in Purview; six months in Microsoft Defender
Use Audit when Activity explorer is empty, when you need a time range Activity explorer will not show, or when you must prove an event exists in the unified log. Use Activity explorer when you need DLP-oriented filters (Endpoint DLP activities, egress, policy/rule matches) and the rich file metadata Endpoint DLP attaches to those events.
Devices list, Last seen, and policy sync
Open Settings (gear) > Device onboarding > Devices . Select a device to open the details pane.
Configuration status and Policy sync status each use three values:
- Value Configuration status Policy sync status
- Updated Device health parameters are enabled and correctly set Device has the current policy versions
Not updated Settings need attention (on Windows this includes Microsoft Defender Antivirus always-on protection and behavior monitoring) Latest policies have not synced; Microsoft notes it can take up to 2 hours for the Devices list status to update
Not available Properties are missing (minimum OS not met, device just onboarded, or similar) Properties missing, or there is no Endpoint DLP policy
Last seen is the most recent time the device was determined to be online . Microsoft's troubleshooting note is blunt: devices must be online for the policy update to happen . If status is stuck, check Last seen before you recreate policies.
Other attributes on the device details pane include Last policy sync time , OS , Defender engine version , Defender Mocamp (client) version , MDATP device ID , Valid user (the signed-in user has a corresponding Microsoft Entra ID account and is in scope of a Devices-targeted DLP policy), Sensitive Data Activity for the last 30 days , whether advanced classification bandwidth was exceeded in the past 24 hours , and Endpoint DLP status (enabled or disabled).
The same DLP device fields are available in Microsoft Defender Advanced hunting on the DeviceInfo table in the DlpInfo JSON column ( IsDlpConfigurationValid , IsDlpEnabled , HasDlpValidUpn , and related properties). Use hunting when you need fleet-wide queries instead of clicking one device at a time.
For Windows servers, onboarded servers do not show Endpoint DLP events in Activity explorer until you Enable Endpoint DLP for Windows Servers in Endpoint settings.
Device health report and Last seen buckets
Settings > Device onboarding > Device report is the fleet dashboard. It uses devices that reported in the past 30 days and updates hourly . Visualizations include:
Device onboarding — coverage and configuration issues.
Device readiness to receive policy updates — offline during the past day, outdated Microsoft Defender Antivirus, or configuration issues (these are risk indicators, not proof a specific update failed).
Last time devices were seen online — non-cumulative buckets for the last 24 hours , 3 days , 7 days , and 30 days . Each device is counted once in the most recent applicable bucket.
Device readiness for feature — currently Just-in-time protection and Paste to supported browsers .
Use this report to answer are we ready to turn on JIT, not to investigate a single USB copy.
DLP Alerts dashboard
The DLP Alerts page in Purview is for policy matches that generate alerts , not for every audited activity. You view alerts, events, and metadata; set investigation status; and track resolution. Alerts are also routed to the Microsoft Defender portal, where you can do the same work plus additional Defender XDR investigation. Microsoft publishes two retention numbers:
- Purview DLP alerts dashboard: 30 days
- Microsoft Defender portal: six months
Administrative-unit-restricted admins see only their unit's alerts. JIT in-progress and JIT block events are not alerts —do not expect them on this dashboard. When an endpoint policy match does alert, the event details can include rich device metadata (file hashes, device name, application, removable-media manufacturer/model/serial for USB copies).
Always audit and when events appear without a policy
Always audit file activity for devices is an Endpoint DLP setting. By default, after onboarding, the service audits activity for Office, PDF, and CSV files. You can review that activity in Activity explorer even if the device is not targeted by any policy . The setting also audits, when no DLP rule matched: File Created , File Modified , File Renamed , File created on removable media , and File created on network share .
Turn Always audit off if you want those Office/PDF/CSV activities audited only when onboarded devices are included in an active policy. Leave it on during early rollout so you can see baseline file movement before you publish blocking rules.
Microsoft also documents a second layer: some Office, PDF, CSV, and archive extensions can be audited regardless of a policy match on Windows and (with a shorter extension list) on macOS. Image formats such as .jpg and .png can be audited when OCR is enabled. Unsupported types such as .exe , .dll , and .sys are not monitored—do not invent coverage for them.
Common activities you can monitor or restrict
Endpoint DLP can audit and, for most egress channels, restrict these activities on sensitive items stored on Windows 10/11 and current macOS devices:
Activity What it detects Restrictable? Platform notes
Upload to a restricted cloud service domain or access from an unallowed browser Upload or browser access against allow/unallowed domain lists; unallowed browsers can be redirected to Microsoft Edge Yes Windows and macOS
Paste to supported browsers Paste of content to a restricted service domain (evaluated on the pasted content) Yes macOS is preview
Copy to clipboard Copy from a protected file; intra-Office copy of the same file can still be allowed Yes Includes redirected clipboards on Azure Virtual Desktop with Windows 365
Copy to USB removable device Copy or move to USB Yes Redirected USB on AVD/Windows 365 can appear as a network share
Copy to a network share Copy or move to a network share Yes Same AVD redirected-USB caveat
Print Printing, including redirected printers on AVD with Windows 365 Yes Some printer-group parameters are Windows-only
Copy or move using unallowed Bluetooth app Copy through apps on the unallowed Bluetooth list Yes Windows and macOS
- Copy or move using RDP Copy into a remote desktop session Yes Not supported on macOS
- Create an item / Rename an item New file or rename Auditable only Not restrictable
Access by restricted apps An app on the restricted-apps list opens a protected file Configured via restricted apps / app groups Windows and macOS
Create Windows Recall snapshots Sensitive content that would be in a Recall snapshot Yes (preview) Not ARM64 Windows 11; not macOS
If data is never saved to a local file (for example Word saves directly to USB), Endpoint DLP cannot scan or block that path. That is a monitoring gap, not a misconfigured Activity explorer filter.
While policies already on an offline device still enforce on already-classified files, enforcement events do not appear in Activity explorer until the device is back online . The Devices list shows that an offline device is out of sync with server-side policies.
Exam scenarios
Copied to USB, no alert: Check Always audit and Activity explorer first. Alerts require a rule configured to alert; audit events do not always become alerts.
Policy never fires: Devices list Last seen and Policy sync status , then confirm both user and device are in the policy scope.
JIT toast, no alert: Expected. Look for JIT triggered = true in Activity explorer.
Need 90 days of alerts: Use Microsoft Defender , not the Purview DLP Alerts dashboard's 30-day window.
Need last week's copies but Activity explorer is empty: Confirm 30-day window and latency, then Audit search; if the laptop was offline, wait for backfill.
- Official resources
- Learn about Endpoint data loss prevention
- Get started with Activity explorer
- Troubleshooting endpoint DLP configuration and policy sync
- Monitor Endpoint DLP device health
- Get started with the DLP Alerts dashboard