Microsoft Sentinel
Cloud and workloads

Create Basic Automation Rules Simple Flows

In brief

Updated DevRel links and clarified how to open Automation in the Microsoft Defender portal: Microsoft Sentinel > Configuration > Automation for Microsoft Sentinel, or Automation from the ISOC main navigation. The creation steps now omit redundant navigation.

What Defender admins need to know

Use the revised paths when locating Automation and creating automation rules.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

The following examples show how to combine Simple Flows triggers, conditions, and actions to deliver common SOC workflows.

Note

To open the automation page in the Microsoft Defender portal, use the path for your package:

  • In Microsoft Sentinel in the Defender portal: Microsoft Sentinel > Configuration > Automation.
  • In ISOC main navigation menu: Automation.

Example 1: Auto-triage low-fidelity alerts by classification

Automatically resolve informational alerts from a specific provider as benign positives so the queue stays focused on real threats.

  1. In the Microsoft Defender portal, go to Microsoft Sentinel > Automation and selectSelect + Create > Automation rule.
  2. Under Trigger, select When an alert is created.
  3. Under Conditions, add:
    • ProviderEqualsMicrosoft Defender for Endpoint

Add a stage-appropriate checklist the moment an analyst starts investigating.

  1. From Microsoft Sentinel > Automation, createCreate a new automation rule.
  2. Under Trigger, select When a case is updated.
  3. Under Conditions, add: StatusChanged toInvestigating.
  4. Under Actions, add Add Task with the tasks you want the analyst to follow during the investigation phase.