Study guide
17.1 Configure Insider Risk Management Settings
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
17.1 Configure Insider Risk Management Settings
Key Takeaways Explain This Topic AI
Insider Risk Management settings are tenant-wide: they apply to every IRM policy regardless of which template you choose later.
Privacy is on by design (pseudonyms such as AnonIS8-988), but Content explorer metadata, API/eDiscovery exports, the Triage Agent dashboard, and DLP/Conditional Access still show real names.
Analytics evaluates aggregated, anonymized activity for up to 10 days without creating a policy; first scan insights can take up to 48 hours.
Intelligent detections control unusual-download boosts, Fewer/Default/More alert volume, Defender for Endpoint import statuses, and up to 500 unallowed plus 500 third-party domains.
Policy timeframes use an activation window of 1–30 days after a trigger and past activity detection of 0–90 days before a trigger (email past detection is 10 days).
Last updated: August 2026
Why tenant settings come before policies
SC-401 treats Microsoft Purview Insider Risk Management (IRM) as a sequence: roles and connectors first, then tenant settings , then the indicator catalog, then a policy template , then the policy itself. This section is the settings layer. Microsoft states that Insider Risk Management settings apply to all Insider Risk Management policies, regardless of the template you choose when creating a policy . If privacy, analytics, intelligent detections, priority user groups, or timeframes are wrong, every later policy inherits the mistake.
Open settings from Settings at the top of any Insider Risk Management page in the Microsoft Purview portal ( purview.microsoft.com ), then select Insider Risk Management . There is no per-policy Privacy or Analytics blade. Creating the actual policy, forensic evidence capture, Adaptive Protection insider-risk levels, and the alert-to-case workflow belong to later chapters—use this catalog to configure the tenant , not to investigate a case.
- Setting What it does for every IRM policy
- Privacy Show real usernames or anonymized pseudonyms on alerts and cases
- Analytics Scan the tenant for insider-risk patterns without creating a policy
Intelligent detections Unusual-download boost, alert-volume slider, Defender for Endpoint import, unallowed and third-party domains
- Policy indicators Global catalog of signals (all disabled until you turn them on)
- Policy timeframes How far before and after a triggering event IRM reviews activity
- Priority user groups Named groups that get closer inspection and more sensitive scoring
- Global exclusions Domains, file types, and other items that are not scored
- Inline alert customization Tune thresholds from the Alerts dashboard while reviewing an alert
Admin notifications Email on the first alert for a new policy, daily high-severity alerts, and a weekly summary of policies with unresolved warnings
Data sharing Export alerts to SIEM via the Office 365 Management Activity API; share user risk details with Microsoft Defender and DLP
Detection groups, Microsoft Teams case channels, Power Automate flows, and priority physical assets also live under Settings. Know they exist; do not confuse them with the policy-creation wizard.
Privacy: pseudonyms by design
Microsoft documents IRM as privacy by design : users are pseudonymized by default , with role-based access control and audit logs. The Privacy setting still matters because an administrator can switch the tenant to show real names.
Two options:
Show anonymized versions of usernames. A user such as Grace Taylor appears as a randomized pseudonym such as AnonIS8-988 in the IRM experience. The choice anonymizes all users with current and past policy matches and applies to all policies. User profile fields (name, title, alias, organization or department) are hidden on alert and case details.
Do not show anonymized versions of usernames. Real names and profile fields appear for current and past matches.
Exam traps sit in the exceptions , not the happy path:
Activity metadata and Content explorer are not anonymized. Names in the metadata of an activity, in file metadata in Content explorer, and inside file content remain visible even when the Privacy toggle is on.
Provisioning still shows names. Usernames appear when you add users to existing policies or assign users to new policies.
Exports split. Anonymization is not preserved when you export alerts through the exporting API or into Microsoft Purview eDiscovery. Anonymization is preserved when you export to CSV from alerts or cases.
Data risk graph. With anonymized usernames enabled, you cannot use the data risk graph.
Triage Agent. User names in prioritized alerts are not anonymized on the Triage Agent dashboard even when Privacy is on.
Downstream enforcement. Adaptive Protection documentation notes that user names are not anonymized in Conditional Access or data loss prevention. IRM privacy does not rewrite DLP incident names.
Turning the setting off later reveals usernames for everyone who already had matches. Treat that as an HR and legal decision, not a casual demo toggle.
Analytics: scan before you commit to a template
Analytics lets you evaluate potential insider risk without configuring any insider risk policies . Results are aggregated and anonymized ; reviewers cannot identify individual usernames. Microsoft states the scan accounts for all UPNs and identities that might move data outside the organization—user, system, guest, and non-person accounts.
Enable it from the Overview Insider risk analytics card ( Run scan ) or from Settings > Analytics . First insights can take up to 48 hours . When you first enable analytics you see one day of results; if you leave it on, each daily scan adds to the report up to a maximum of the previous 10 days . Analytics risk scoring uses up to 10 days of activity; insider risk policies use daily activity for insights. Microsoft does not publish a longer analytics window—do not invent one.
Sources included in every scan:
- Microsoft 365 audit logs (the primary source)
- Exchange Online (attachments emailed to external contacts or services)
- Microsoft Entra ID (risky activity associated with deleted user accounts)
If you configured the Microsoft 365 HR data connector, analytics also uses resignation and upcoming termination dates.
Analytics also feeds real-time indicator threshold recommendations when you later build a policy. Turning analytics off stops insight reports from updating and removes those real-time threshold insights.
User-level analytics is a separate pair of toggles: Show insights at user level on the Analytics page, plus Share user risk details with other security solutions under Data sharing . That combination publishes user activity summaries and insider-risk severity into DLP alerts, Communication Compliance, and Microsoft Defender entity pages—including for users not in any IRM policy. Enabling analytics requires membership in Insider Risk Management , Insider Risk Management Admins , or Microsoft 365 Global admin . Prefer the IRM admin roles over Global Administrator.
Intelligent detections: volume, downloads, domains, and Defender alerts
Use Intelligent detections to:
- Boost the score for unusual file download activity by entering a minimum number of daily events
- Raise or lower the mix of high, medium, and low alerts
- Import and filter Microsoft Defender for Endpoint alerts used by security-violation templates
- Specify unallowed domains (higher risk score; optional trigger)
- Specify third-party domains (alerts for risky browser download activity)
Global exclusions used to live here; they now have their own Global exclusions (preview) setting. An exam option that still says "exclude domains under Intelligent detections" is stale.
File activity detection. You enter a daily-event floor. Microsoft's example: if the floor is 25 , and a user usually downloads about 10 files per day over the previous 30 days , a day with 20 downloads is unusual for that user but is not boosted because 20 is below 25.
Alert volume (tenant-wide):
- Setting What you see Trade-off Microsoft documents
- Fewer alerts All high-severity; fewer medium; no low You might miss some true positives
- Default volume All high; a balanced amount of medium and low Baseline
- More alerts All medium and high; most low More false positives
Defender for Endpoint alert statuses. After Defender for Endpoint is integrated (previous chapter), Intelligent detections lets you import alerts whose triage status is Unknown , New , In progress , and/or Resolved . Import is daily . If you select New, In progress, and Resolved, the same Defender for Endpoint alert can create three IRM activities as the status changes. That is by design so investigators can follow triage, not a duplicate-alert bug.
Unallowed vs third-party vs excluded domains
Unallowed domains (up to 500 ): activity involving the domain gets a higher risk score and can optionally participate in policy triggers . Example: email to gmail.com , or downloads from a domain you treat as hostile. Wildcards such as *.wingtiptoys.com match same-level subdomains; Include multi-level subdomains reaches deeper. CSV import is supported.
Third-party domains (up to 500 ): list business domains you want scored for the device indicator Use a browser to download content from a third-party site —for example a sanctioned vendor portal that is not a Microsoft 365 property.
Global exclusions : domains (and other items) that should not be scored at all.
Microsoft publishes 500 as the maximum for both unallowed and third-party domain lists. Do not invent a different cap.
Loading diagram... Tenant IRM settings that every policy inherits
Priority user groups
Users are not equal risk. Executives, highly privileged IT administrators, and people with a history of risky activity need closer inspection and more sensitive risk scoring . You define them in Settings > Priority user groups , not inside the template picker.
Creating or editing a group requires Insider Risk Management or Insider Risk Management Admins . Workflow: name (required; cannot be renamed after you finish), optional description, then members (search mail-enabled accounts, Select all , or upload a CSV whose column is titled user principal name ). Microsoft publishes a maximum of 10,000 users per priority user group. Then you must assign at least one reviewer: the built-in Insider Risk Management , Insider Risk Management Analysts , or Insider Risk Management Investigators role groups, a mix of those groups, or a custom set of users. That restriction is how you keep a confidential-project group off the default analyst roster.
Two templates require a priority user group: Data leaks by priority users and Security policy violations by priority users . Deleting a group removes it from any active policy that used it; the policy then has no included users , sits idle , and does not create alerts . Priority user groups are not currently supported for admin units —unrestricted admins can still assign groups, but scoped admins cannot create those two policy types.
Enable the matching risk score booster under Policy indicators > Risk score boosters so membership actually raises scores. Selecting those templates is covered in section 17.3; creating the policy is a later chapter.
Policy timeframes (published ranges)
Policy timeframes set how far IRM looks after and before a triggering event. Microsoft publishes these ranges:
Timeframe Direction Published range Notes
Activation window After the triggering event 1 to 30 days Available for all templates. Example: set 30 days; months later a trigger fires; that user stays in-scope for 30 days after the event.
Past activity detection Before the triggering event 0 to 90 days for audit-log activities Available for all templates.
Email activities Past detection 10 days Microsoft documents a 10-day past window for email , not 90.
Configure them with sliders on Settings > Policy timeframes . A longer user-level activation window overrides a shorter global window. Microsoft's example: global activation 15 days, a temporarily added user set to 30 days—that user remains in-scope for 30 days.
Do not invent other numeric limits for timeframes. Microsoft does not publish a required exam value for the default slider position.
Exam traps for settings
Settings are tenant-wide . A "per-policy privacy toggle" is a distractor.
Analytics is not a policy. It is how you decide which template to pick later.
Unallowed raises score; third-party feeds a specific browser-download indicator; exclusions suppress scoring.
Email past detection is 10 days , not 90.
Anonymization has holes (Content explorer, APIs, eDiscovery, Triage Agent, DLP/Conditional Access).
Deleting a priority user group can silently idle the policies that depended on it.