Study guide
19.2 Insider Risk Workflow and Notice Templates
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
19.2 Insider Risk Workflow and Notice Templates
Key Takeaways Explain This Topic AI
The published IRM workflow is Policies → Alerts → Triage → Investigate (cases) → Action (notice, resolve, share, or escalate).
Notice templates pre-fill reminder or training emails sent from a case. Sending a notice does not close the case; Resolve case is a separate action.
A template includes Template name, Send from, Subject, and Message body (text or HTML). HTML href attributes must use single quotes. You can send a notice only to the user email on that case; send-time values override the template and are copied into case notes.
Resolve a case as Benign or Confirmed policy violation, which sets status to Closed. Escalate for investigation creates a Microsoft Purview eDiscovery (Premium) user investigation for legal review—not a Defender incident.
Insider Risk Management, Analysts, and Investigators can configure notice templates. Admins configure policies and settings but cannot configure notice templates or investigate alerts and cases.
Last updated: August 2026
Creating the case is not the end of an Insider Risk Management program. Microsoft describes a five-stage workflow: Policies → Alerts → Triage → Investigate → Action . The previous section covered alerts, triage, and investigation tools. This section covers the Action stage and the reusable notice templates that keep user notification consistent, auditable, and role-correct. SC-401's wording is explicit: manage the IRM workflow, including notice templates .
The published IRM workflow
Policies (templates, indicators, in-scope users, and detection windows) produce alerts when indicators match. Triage decides whether to confirm into a case, dismiss as benign, or leave the item in Needs review. Investigate happens in the case: User activity, Activity explorer, Content explorer, forensic captures, and notes. Action is what you do when the picture is clear enough: send the user a notice, resolve the case, share it (email, ServiceNow, Teams, or Power Automate), or escalate it into eDiscovery (Premium).
The Users dashboard sits between policy assignment and cases. Investigators use it to see who is in scope, stop scoring activity, and (with the right flows) notify someone that they were added to a policy. Removing a user from in-scope status can take several minutes. If that user still has active alerts or cases, they remain on the dashboard and the user details show they are no longer in-scope for a policy.
Notice templates: purpose and limits
Most confirmed alerts are mistakes, not malice. Microsoft's published guidance is to treat notices as reminders , links to refresher training, or pointers to corporate policy—not as a substitute for HR or legal process. Notices also create a documented trail when the same user repeats the behavior.
You create templates under Insider Risk Management > Notification templates . The dashboard lists templates in reverse date order (newest first). Configure notice templates is allowed for Insider Risk Management , Insider Risk Management Analysts , and Insider Risk Management Investigators . Admins cannot configure notice templates ; they configure policies and settings instead. That pairing is an exam discriminator: the people who investigate are the people who own the wording of the email the user will see.
Each template has four fields:
- Template name — shown on the template list and in the picker when you send from a case
- Send from — mailbox that appears in From, unless you change it at send time
- Subject — text for the message subject line
- Message body — text or HTML
You may send a notice only to the user email address associated with that case . You cannot redirect a case notice to a manager, an HR mailbox, or a distribution list from the notice-template action. Manager or HR notification is a different path (recommended Power Automate flows).
HTML is supported, with one published catch: href attributes must use single quotes , not double quotes. A training link written as href="https://contoso.com" can fail in this template surface; href='https://contoso.com' is the documented pattern.
When you send from a case, choosing a template pre-fills the other fields. Anything you type in the send dialog overrides the template for that send only; it does not rewrite the stored template. All sent notices are added to the Case notes queue. Edit a stored template from the template details page ( Edit ), and delete unused templates with the toolbar delete icon after a Yes confirmation.
Sending a notice does not close the case
On the case action toolbar, Send email notice is independent of Resolve case . Microsoft states explicitly that sending a notice does not set the case to Closed. Leave the case Active if you want to keep watching the user without opening a second case. If the coaching email is the last step, send the notice, then Resolve case as a follow-on action.
Resolve as one of two published classifications:
Benign — policy-match alerts evaluated as low risk, not serious, or false positive
Confirmed policy violation — policy-match alerts evaluated as risky, serious, or the result of malicious intent
Resolving sets status to Closed , writes the classification and your Action taken text into case notes, and starts the 120-day resolved-case retention clock. Optionally you can delete the case and associated content immediately; that permanently removes related content, alerts, and insights. Use immediate delete only when policy requires destruction, not as a default click. If Microsoft Teams integration is enabled, resolving also archives the case team (hides it and makes it read-only).
Do not invent extra IRM case-resolution labels such as True positive or False positive. Those are Microsoft Defender alert classifications. Defender maps them into IRM Confirmed or Dismissed when alerts sync; they are not the Resolve case dropdown values.
Escalate, share, and automate
Escalate for investigation creates a Microsoft Purview eDiscovery (Premium) (shown as eDiscovery > Advanced ) user investigation so legal can preserve, collect, review, analyze, export, and run legal-hold notifications. You name the new investigation, add notes, and can adjust notice fields (those values override the template). After Confirm , open the new case in eDiscovery Advanced. Escalation is for extra legal review, not a synonym for "confirm the IRM alert" and not the same thing as opening a Defender XDR incident.
If Teams integration is on in IRM settings, confirming an alert and creating a case automatically creates a Microsoft Teams team . Use View Microsoft Teams team on the case toolbar. Cases opened before you enabled integration get Create Microsoft Teams team instead.
Recommended Power Automate templates (included with IRM licensing for those templates; premium or custom connectors may need extra Power Automate licenses) cover: notify users when they are added to a policy (Users dashboard); request information from HR or business (responses land as case notes); notify the manager of an alert (policy, date/time, severity, also logged to case notes); and create a ServiceNow record. Flows must be created in the default Power Automate environment. If you anonymize users in IRM privacy settings, the user- and manager-notification templates do not function as intended. Only the flow creator can run a flow until it is shared . Creating or sharing from IRM settings requires Insider Risk Management or Admins; from Manage Power Automate flows on a case, membership in at least one IRM role group is enough.
Contributors and who can resolve versus investigate
The Contributors tab grants temporary access to a specific case. You need the Role Management role to add contributors. By default, Insider Risk Management and Investigators appear as contributors on every active and closed case. Analysts and investigators can add contributors; you cannot add analysts as contributors ; contributors cannot add other contributors. Contributors get case-management controls except permission to confirm or dismiss alerts and permission to edit contributors .
Who investigates versus who configures remains the backbone of the workflow:
- Action IRM (umbrella) Admins Analysts Investigators Auditors Approvers
- Access and investigate alerts and cases Yes No Yes Yes No No
- Create a case from an alert Yes No No Yes No No
- Content explorer and forensic captures Yes No No Yes No No
- Configure policies and settings Yes Yes No No No No
- Configure notice templates Yes No Yes Yes No No
- View and export audit logs Yes No No No Yes No
- Approve forensic capturing requests Yes No No No No Yes
Analysts and Investigators (and the umbrella Insider Risk Management group) complete review and then Resolve case . Admins do not resolve cases because they cannot open them. Keep at least one user in Insider Risk Management or Admins so the tenant does not reach a zero-administrator state. Role assignment can take up to 30 minutes to apply across the organization.
A practical sequence for the exam
A typical inadvertent-exfiltration path: High-severity Needs review alert → Investigator confirms and creates a case → User activity shows a sequence (for example download, then USB) → Content explorer snapshot (often about an hour for new cases) → Send email notice from a training template (override the subject if needed; HTML links use single quotes) → leave the case Active overnight → if no further spikes, Resolve as Benign with Action taken notes. A typical theft path uses the same triage, then Escalate for investigation so eDiscovery can place holds, and resolve the IRM case as Confirmed policy violation only after that handoff is recorded in notes.
If the exam stem asks who can "manage the workflow including notice templates," pick Investigators or Analysts (or the umbrella group)—not Admins, not Auditors, and not Approvers. If it asks whether the coaching email closes the investigation, the answer is no: Resolve case is the close action, and resolved artifacts follow the published 120-day clock unless you chose immediate delete.