Study guide

17.3 Select an Appropriate Policy Template

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.3 Select an Appropriate Policy Template

Key Takeaways Explain This Topic AI

Every IRM policy must be assigned a template; Microsoft supports up to 100 policies per template type.

Match the triggering event to the template: HR resignation/termination or Entra deletion for departing-user templates; High-severity DLP or custom exfiltration for Data leaks; Defender for Endpoint defense evasion for security-violation templates.

Data leaks by priority users and Security policy violations by priority users require priority user groups created in IRM settings.

Patient data misuse requires healthcare access indicators, an HR connector for address matching, and a Microsoft Healthcare or Epic connector—not a High-severity DLP trigger.

Departing-user data theft and departing-user security violations are different templates: files leaving versus Defender for Endpoint malware or disabled security controls.

Last updated: August 2026

Templates are scoring models, not finished policies

An Insider Risk Management policy template is a predefined package of which triggering events matter and which risk scoring model to use. Every policy must have an assigned template in the creation workflow before the policy is created. Microsoft supports up to 100 policies for each policy template . This section is selection : match the business event to the template. Wizard steps, forensic evidence settings, Adaptive Protection insider-risk levels, and case workflow are later chapters.

Triggering events are the prerequisites that determine whether a user is active for a policy. If you add a user but no triggering event occurs, the policy does not evaluate that user's activity unless you manually add the user on the Users dashboard. Policy prerequisites are the connectors, indicators, and integrations the template needs in order to receive signals.

Microsoft publishes in-scope user limits per template type . You may add any number of users to a policy; the limit applies to users brought in scope after a triggering event . If you near or exceed the limit, policy performance reduces . Check Policies and the Users in scope column. These maximums apply across all policies that use a given template type .

  • Template Published in-scope user limit
  • Data leaks by priority users 1,000
  • Security policy violations by priority users 1,000
  • Security policy violations 1,000
  • Patient data misuse (preview) 5,000
  • Risky browser usage (preview) 7,000
  • Data leaks by risky users 7,500
  • Security policy violations by risky users 7,500
  • Risky AI usage 10,000
  • Data leaks 15,000
  • Security policy violations by departing users 15,000
  • Data theft by departing users 20,000
  • Forensic evidence Unlimited

Microsoft's published in-scope table does not list a number for Risky Agents (preview) —do not invent one. Forensic evidence appears in that limits table; configuring forensic evidence is a later chapter, not a substitute for a data-theft template.

Microsoft also publishes other policy caps used when you later build a policy (not when you merely pick a template): 50 priority file extensions, 50 priority sensitive info types, 50 priority sensitivity labels, 50 priority sites, and 5 priority trainable classifiers.

Match the triggering event to the template

This is the SC-401 skill: Select an appropriate policy template. Start from the event that should bring a user into scope , then pick the template whose trigger matches.

Data theft by departing users. Trigger: resignation or termination date from the HR connector or Microsoft Entra account deletion . The HR connector is optional if you use Entra deletion. The template scores exfiltration near leave dates: SharePoint Online downloads, printing, and copies to personal cloud messaging and storage. Cloud indicators can include Box, Dropbox, Google Drive, Amazon S3, and Azure.

Data leaks. Trigger: DLP policy activity that creates a High severity alert or built-in exfiltration event triggers you customize. Prerequisites: a DLP policy configured for High severity alerts on Exchange Online, SharePoint Online, or OneDrive for Business or customized triggering indicators. Low or Medium DLP Incident reports severity will not trigger IRM. Each IRM Data leaks policy can assign up to 20 DLP policies . Scope trap: only users included in both the DLP rule and the IRM policy are processed. Over-assigning High to non-exfiltration DLP rules (for example access-denied events) floods IRM with noise. Prefer a dedicated DLP policy that combines the exfiltration events you actually want as triggers.

Data leaks by priority users. Same trigger options as Data leaks, plus you must assign priority user groups from Settings. Scoring is more sensitive; alerts are more likely and tend to be higher severity.

Data leaks by risky users. Trigger: HR performance improvement, poor performance, or job level change and/or Communication Compliance messages with potentially threatening, harassing, or discriminatory language. You must configure the HR connector, Communication Compliance integration, or both . Associated Communication Compliance alerts do not need to be triaged, remediated, or changed in status before they feed IRM.

Patient data misuse (preview). Trigger: defense evasion of security controls from EMR systems and user and patient address matching indicators from HR systems. Prerequisites: healthcare access indicators selected in the policy or insider risk settings; HR connector configured for address matching ; Microsoft Healthcare or Epic connector configured. Use this template for unauthorized access, viewing, modification, or export of patient data in EMR systems in support of HIPAA and HITECH safeguarding of protected health information.

Security policy violations. Trigger: defense evasion of security controls or unwanted software detected by Microsoft Defender for Endpoint. Requires an active Defender for Endpoint subscription and integration with the Microsoft Purview portal.

Security policy violations by departing users. Trigger: HR resignation/termination or Entra account deletion (HR optional if using Entra). Still requires Defender for Endpoint. Use this when the concern is malware or disabled security features , not file theft. File theft on the way out is Data theft by departing users .

Security policy violations by priority users. Trigger: Defender for Endpoint defense evasion or unwanted software. Requires Defender for Endpoint and priority user groups.

Security policy violations by risky users. Trigger: the same HR/Communication Compliance stressors as Data leaks by risky users. Requires those connectors and Defender for Endpoint.

Loading diagram... Choose an IRM template from the triggering event

AI, browser, and agent templates

Risky AI usage. Microsoft's trigger-and-prerequisite table leaves the triggering-events cell blank for this template—do not invent a fake trigger name. Prerequisites Microsoft does publish: the Microsoft Insider risk extension (Microsoft Edge) or Microsoft Purview extension (Chrome) must be installed; at least one browsing indicator selected in the policy; optionally an HR connector for termination and resignation dates; optionally a Communication Compliance policy that detects inappropriate content in messages. Detection focuses on browsing to generative AI websites and on user prompts and AI responses that contain sensitive information in Microsoft 365 Copilot, Microsoft Copilot, and agents. This policy's detections also contribute to user risk scoring in Adaptive Protection (configured in a later chapter). You can also create it as a one-click policy from Microsoft Purview Data Security Posture Management (DSPM) for AI when you act on Detect risky interactions in AI apps .

Risky browser usage (preview). Trigger: user browsing activity related to security that matches at least one selected Browsing indicator . Microsoft points you to the browser signal detection article for the full prerequisite list (device onboarding plus the Edge or Chrome extension). Use this template for acceptable-use violations such as phishing sites or adult content—not for SharePoint exfiltration (that is Data leaks / data theft) and not for EMR snooping (that is Patient data misuse).

Risky Agents (preview). Triggers Microsoft lists: exposing an agent to risky prompts, an agent generating sensitive responses, accessing sensitive or priority SharePoint files, accessing risky websites, sharing SharePoint files with people outside the organization, and activity above the agent's usual activity for the day. Prerequisites: Copilot Studio agents and Microsoft Foundry agents. Microsoft states this policy template is applied by default for all organizations .

Exam decision table

If the scenario emphasizes... Select

Employee resigns, is terminated, or the Entra account is deleted and files leave via USB, print, or cloud Data theft by departing users

Same employment end and Defender for Endpoint shows disabled antivirus or unwanted software Security policy violations by departing users

High-severity DLP alert or selected exfiltration on the general population Data leaks

Same leak pattern but the population is executives, privileged admins, or a watch list Data leaks by priority users

Performance improvement plan, poor review, demotion, or toxic messages then data leaving Data leaks by risky users

Same stressors then Defender for Endpoint security violations Security policy violations by risky users

Defender for Endpoint defense evasion for ordinary users, including a history of violations Security policy violations

  • EMR snooping, neighbor or family record access, or PHI export Patient data misuse
  • Copilot or AI prompts and responses that contain secrets Risky AI usage
  • Users browsing malware, adult, or violence categories Risky browser usage
  • Copilot Studio or Foundry agents leaking via tools or SharePoint Risky Agents

Sequence detection (two or more risky activities in a defined order) is supported on Data leaks, Data leaks by priority users, Data leaks by risky users, Data theft by departing users, and Risky AI usage. Priority content selection is supported on those same templates plus the same data-leak family. You choose sequences and priority content when you create the policy , not when you merely pick the template—but knowing which templates support them prevents you from picking Patient data misuse or a security-violation template when the scenario is a sequenced SharePoint exfiltration.

A collection policy can still starve device indicators after you pick the right template: if collection filters out the device activity, IRM never sees it.

Exam traps for templates

Departing plus files is not departing plus Defender. Two different templates.

Priority templates fail without a priority user group (policy health: "No priority user groups are included in this policy").

Risky-user templates fail without the HR connector and/or Communication Compliance integration.

Patient data misuse needs both HR address matching and a Healthcare or Epic connector—not High-severity DLP.

Data leaks needs High DLP severity, supported workloads, and overlapping user scope. Each Data leaks policy can bind at most 20 DLP policies.

Customizable triggers exist only on Data leaks and Data leaks by priority users.

Do not pick Forensic evidence or Adaptive Protection as the answer to "which template detects departing-user theft."

If a triggering event is not configured, Microsoft's policy health warning is that risk scores will not be assigned until you select a triggering event.