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.
In the Microsoft Defender portal, go toMicrosoft Sentinel>Automationand selectSelect + Create > Automation rule.- Under Trigger, select When an alert is created.
- Under Conditions, add:
- ProviderEqualsMicrosoft Defender for Endpoint
Add a stage-appropriate checklist the moment an analyst starts investigating.
FromMicrosoft Sentinel>Automation, createCreate a new automation rule.- Under Trigger, select When a case is updated.
- Under Conditions, add: StatusChanged toInvestigating.
- Under Actions, add Add Task with the tasks you want the analyst to follow during the investigation phase.
@@ -44,11 +44,11 @@ source_path: sentinel/automation/create-basic-automation-rules-simple-flows.md cmProducts: - https://authoring-docs-microsoft.poolparty.biz/devrel/43093068-2dda-408b-b3fe-dfd705c84f78 - https://authoring-docs-microsoft.poolparty.biz/devrel/1ae5c491-970a-4062-8301-6336e69f9026-- https://authoring-docs-microsoft.poolparty.biz/devrel/8a94907f-2511-4271-b5ca-ec7f2e75067c+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/c671beaa-a830-4c9f-aceb-97379ee031ca spProducts: - https://authoring-docs-microsoft.poolparty.biz/devrel/e453d60d-ba7e-43bc-8028-ec38e6b62512 - https://authoring-docs-microsoft.poolparty.biz/devrel/f2c3e52e-3667-4e8a-bf11-20b9eaccdc8c-- https://authoring-docs-microsoft.poolparty.biz/devrel/bffa8e88-f633-409d-a24d-083bdbc68872+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/8921374c-4dbe-4ed0-b011-a39e18bfbd98 platformId: 55391a93-a9f4-dc8d-e064-63d06b505b86 --- @@ -149,11 +149,18 @@ Not every action works with every trigger. The matrix below shows the supported
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](https://security.microsoft.com/), 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 select **+ Create** > **Automation rule**.
+1. Select **+ Create** > **Automation rule**.
2. Under **Trigger**, select **When an alert is created**.
3. Under **Conditions**, add:
- **Provider***Equals***Microsoft Defender for Endpoint**
@@ -167,7 +174,7 @@ Automatically resolve informational alerts from a specific provider as benign po
Add a stage-appropriate checklist the moment an analyst starts investigating.
-1. From **Microsoft Sentinel** > **Automation**, create a new automation rule.
+1. Create a new automation rule.
2. Under **Trigger**, select **When a case is updated**.
3. Under **Conditions**, add: **Status***Changed to***Investigating**.
4. Under **Actions**, add **Add Task** with the tasks you want the analyst to follow during the investigation phase.
