Study guide
16.3 Integrate Insider Risk Management with Microsoft Defender for Endpoint
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
16.3 Integrate Insider Risk Management with Microsoft Defender for Endpoint
Key Takeaways Explain This Topic AI
Insider Risk Management security policy violation templates use Microsoft Defender for Endpoint alerts to score intentional or unintentional security-control violations such as installing unwanted software or disabling device security features.
You must have an active Microsoft Defender for Endpoint subscription and enable Defender for Endpoint for Insider Risk Management integration in the Defender portal under Settings > Endpoints > Advanced features.
The published advanced-feature toggle is Share endpoint alerts with Microsoft Compliance Center; forwarded alert data is stored in the same location as your Office 365 data.
In Insider Risk Management Intelligent detections, import Defender for Endpoint alerts by triage status: Unknown, New, In progress, and/or Resolved.
Defender for Endpoint alerts are imported daily; if you select multiple triage statuses, Insider Risk Management can import multiple user activities for the same alert as the triage status changes.
Last updated: August 2026
Users in a modern workplace often have permission to install software or temporarily disable device security features so they can do their jobs. Whether that behavior is accidental, convenient, or malicious, it can weaken the organization. Microsoft Purview Insider Risk Management does not replace Microsoft Defender for Endpoint as an EDR product. For security policy violation scenarios, IRM imports Defender for Endpoint alerts and then scores those security-related activities in the insider-risk model—next to exfiltration, HR stressors, and other signals.
The SC-401 skill is plan and implement integration with Microsoft Defender for Endpoint . That means you must know where the toggle lives , which IRM templates depend on it , how triage-status filtering works , and why a policy can look “empty” when sharing is off or the filter is too narrow . Detailed IRM indicator catalogs, template authoring, forensic evidence, Adaptive Protection levels , and case workflow belong to later chapters. This section stays on the integration contract .
Why the integration exists
Microsoft describes a family of IRM templates for intentional or unintentional security policy violations . Typical endpoint behaviors include installing malware or other potentially harmful applications and disabling security features. Defender for Endpoint is the enterprise platform that prevents, detects, investigates, and responds to advanced threats on devices. IRM’s job is to place those security-violation alerts in an insider-risk context : the same user who just turned off antivirus may also be a departing employee, a priority user, or someone on a performance improvement plan.
Four published templates require this integration:
Template What MDE contributes Extra planning dependency
Security policy violations Defense evasion of security controls or unwanted software detected by Defender for Endpoint Active MDE subscription plus IRM integration
Security policy violations by departing users Same MDE security alerts, scored against employment status HR connector or Microsoft Entra account deletion as the trigger
Security policy violations by risky users Same MDE security alerts, scored against employment stressors HR connector and/or Communication Compliance risky-user signals, and MDE integration
Security policy violations by priority users Same MDE security alerts for high-impact identities MDE integration and priority user groups assigned to the policy
Microsoft’s troubleshooting article is blunt: if Microsoft Defender for Endpoint alerts are not being shared with the Microsoft Purview portal , security-violation policies will not receive those alerts. If a security-violation policy is not assigning risk scores , one published check is that the alert triage status filter in Intelligent detections is not too narrow .
You also need to meet Defender for Endpoint’s own minimum requirements (supported operating systems, onboarding, licensing). Microsoft does not publish an SC-401-specific device count or alert-volume quota for this integration. Do not invent one. Confirm an active Microsoft Defender for Endpoint subscription and a supported onboarding state; then enable sharing.
Defender portal: turn on alert sharing
Enable the integration in the Microsoft Defender portal (IRM articles still say “Defender Security Center” in places; the current path is the Defender portal):
Sign in to the Microsoft Defender portal.
Go to Settings > Endpoints > Advanced features .
Locate Share endpoint alerts with Microsoft Compliance Center .
Toggle the setting On .
Select Save preferences .
Microsoft’s description of this advanced feature is the sentence you should be able to quote: the endpoint alert sharing setting sends endpoint security alerts and their triage status to the Microsoft Purview portal . You can use those alerts to improve insider risk management policies and address internal risks before they cause harm. Forwarded data is stored in the same location as your Office 365 data. That storage statement matters for residency conversations: this is not a separate “Defender-only” copy in an unpublished region; it follows the Office 365 data location.
Sharing does not start scoring by itself. Microsoft says that after you set up the Security policy violation indicators in Insider Risk Management settings, Defender for Endpoint shares alerts with insider risk management for applicable users . In other words, the Defender toggle is necessary but not sufficient. An IRM admin still has to opt in to the security-violation indicators (admin explicit opt-in from the previous section) and later create a policy from a security-violation template. You will configure those indicators and templates in the next IRM chapters; for this skill, remember the two-sided handshake : Defender sharing and IRM security-violation indicators.
Do not confuse this toggle with neighboring advanced features that are not the IRM integration:
Microsoft Defender for Cloud Apps integration forwards Defender for Endpoint signals to Defender for Cloud Apps for cloud-app visibility. That is not IRM.
Microsoft Intune connection shares device data for device-risk Conditional Access. That is not IRM.
Automatically resolve alerts changes how Defender itself closes alerts. It is not the IRM connector, but it does change triage status , which does affect what IRM imports.
Auto-resolve interaction. If Defender auto-resolves alerts where no threat was found or where threats were remediated, those alerts can move to Resolved without an analyst clicking anything. If your IRM import filter includes only New , you may never see alerts that auto-resolve quickly. If your filter includes Resolved , IRM will ingest those closed alerts as activities. If a SOC analyst manually sets status to In progress or Resolved, auto-resolve will not overwrite that manual status. Plan the IRM triage filter with your SOC’s auto-resolve setting in mind.
Purview portal: import by Defender triage status
The IRM side of the integration is Intelligent detections , documented as the setting that lets you import and filter Defender for Endpoint alerts for activities used in policies created from Insider Risk Management security violation policy templates .
Path: Microsoft Purview portal → Settings (upper-right) → Insider Risk Management → Intelligent detections → Microsoft Defender for Endpoint alert statuses .
You can define one or more of the following alert triage statuses to import:
- Unknown
- New
- In progress
- Resolved
Those four values are the published list. Exam distractors often invent severity names (Critical, High) or IRM alert statuses (Needs review, Confirmed). Severity is not the import filter. Triage status is the import filter.
Alerts from Defender for Endpoint are imported daily. This is not a documented real-time streaming pipe. Plan investigations with a daily latency. If a question asks when an IRM analyst should expect a newly raised Defender alert to appear as IRM activity, the published answer is daily import , not “immediately in the same minute.”
Multiple activities for one alert. Depending on the triage statuses you choose, you might see multiple user activities for the same alert as the triage status changes in Defender for Endpoint. Microsoft’s example: if you select New , In progress , and Resolved , then:
When the Defender alert is generated with status New , IRM imports an initial activity for the user.
When SOC changes the status to In progress , IRM imports a second activity for the same alert.
When the status becomes Resolved , IRM imports a third activity.
This is intentional. It lets investigators follow the progression of the Defender alert and choose the level of visibility their investigation requires. It is also how you accidentally inflate IRM activity volume: import every status and every SOC click becomes another scored activity.
Planning the triage filter
Import choice What IRM sees When to use it Risk
New only Opening of the alert You want only freshly raised endpoint detections You miss alerts that skip New or auto-resolve
New + In progress Open investigation lifecycle You want visibility while SOC works the alert, but not closures You miss the Resolved signal that the endpoint issue is done
Resolved only Closures, including auto-resolved items You want confirmed/completed endpoint events You miss in-flight attacks and may import noise from mass auto-resolve
Unknown + New + In progress + Resolved Full lifecycle, multiple activities per alert You want maximum visibility for insider investigations Highest duplicate-activity volume
There is no published “best” combination. Microsoft’s language is that you choose statuses based on the types of signals you are interested in . For SC-401, be ready to defend a choice (for example: import New and In progress to watch live defense-evasion without scoring every Resolved true-positive cleanup) rather than memorize a secret default Microsoft does not publish.
Intelligent detections also contains unrelated controls—boosting unusual download scores, alert-volume sliders, unallowed domains (up to 500 ), and third-party domains (up to 500 ). Those are IRM settings you will study in the next chapter. Do not configure them as a substitute for the Defender toggle. Unallowed domains do not import MDE alerts.
End-to-end planning sequence
Use this sequence when an exam scenario asks you to implement MDE integration for IRM:
Confirm licensing and onboarding : supported Microsoft 365 subscription for IRM, active Defender for Endpoint subscription, devices onboarded, minimum requirements met.
In the Defender portal, enable Share endpoint alerts with Microsoft Compliance Center and save preferences.
In Purview, assign Insider Risk Management or Insider Risk Management Admins so someone can change IRM settings (Analysts and Investigators cannot configure this integration).
In Intelligent detections , select the Defender for Endpoint alert triage statuses to import.
Later (next chapters): enable security policy violation indicators , then create a policy from the appropriate security policy violations template. Add HR or priority user groups if you chose a departing, risky, or priority variant.
Validate with Microsoft’s published failure modes: sharing not configured; devices not onboarded; triage filter too narrow; security-violation indicators not selected.
What this integration is not
It is not the preview that shares IRM user risk levels into Defender and DLP alerts . That is a different data-sharing setting (IRM → Defender), documented as analyzing activity over 90–120 days . This skill is Defender → IRM alert import for security-violation templates.
It is not investigating IRM alerts inside the Microsoft Defender XDR portal. That XDR experience has its own role requirements (Security Operator/Reader plus IRM Analysts or Investigators) and belongs with later alert-response content.
It is not Endpoint DLP. Endpoint DLP is a different Purview capability. Virtualized environments that Endpoint DLP supports can feed IRM device indicators, but that is not the MDE security-violation import path.
It is not forensic evidence. Investigators may later view forensic captures if that feature is configured, but MDE alert import does not turn on screen capture.
If Microsoft has not published a numeric limit (maximum MDE alerts imported per day, maximum devices, maximum security-violation policies that can consume MDE), do not invent one. Teach the toggle , the four triage statuses , the daily import , and the four security-violation templates that depend on the integration.