Migrate Microsoft Sentinel alert-trigger playbooks to automation rules | Microsoft Learn
In brief
The article now states that alert-trigger playbooks and their Microsoft Sentinel Alert triggers remain supported, but direct invocation from analytics rules is deprecated. It updates the guidance to configure automation rules for alerts from one or multiple analytics rules.
What Defender admins need to know
Administrators relying on direct invocation should configure automation rules to keep these playbooks running automatically when alerts are created.
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.
Migrate Microsoft Sentinel alert-trigger playbooks to automation rules | Microsoft Learn
We recommendConfigure automation rules to run existing alert-trigger playbooks that you migrate existing playbooks built on alert triggers and migrate them from beingwere previously invoked directly by analytics rules to being invoked by automation rules. This article explains why we recommend migratingThe playbooks and their Microsoft Sentinel Alert triggers remain supported; only direct invocation from analytics rules to automation rules, and how to do it.was deprecated. Before you begin, review the Prerequisites.
If you're migratingTo run a playbookthat's used by onlyfor alerts from one analytics rule, follow the instructions under Create an automation rule from an analytics rule.If you're migratingTo run a playbookthat's used byfor alerts from multiple analytics rules, follow the instructions under Create a new automation rule from the Automation page.
Important
Why migrate
Playbooks that are invoked by automationAutomation rules instead of analytics rules haveprovide the following advantages:capabilities for alert-trigger playbooks:
- Automation management from a single display, regardless of type (“single pane of glass”).
- Use a single automation rule triggering playbooks for multiple analytics rules, instead of configuring each analytics rule separately.
- Define the order in which alert playbooks are to be executed.
- Support for scenarios that set an expiration date for running a playbook.
Migrating your playbook triggerConfiguring an automation rule doesn't change the playbook at all, andor its Logic Apps trigger. It changes only changes the mechanism that invokes the playbook to run changes.playbook.
The ability to invokeDirect invocation of playbooks from analytics rules will be deprecated effective March 2026. Until then,was deprecated. To run these playbooks already defined as from analytics rules will continue to run, but as of June 2023 you can no longer add playbooks to the list of those invoked from analytics rules. The only remaining optionautomatically when an alert is to invoke them fromcreated, use an automation rules.rule.
Prerequisites
Create an automation rule from an analytics rule
Follow these steps to migraterun a playbook that's used by onlyfor alerts from one analytics rule. If the playbook is used byFor alerts from multiple analytics rules, use Create a new automation rule from the Automation page.
For Microsoft Sentinel in the Azure portal, select the Configuration > Analytics page. For Microsoft Sentinel in the Defender portal, select Microsoft Sentinel > Configuration > Analytics.
Under Active rules,
find anselect the analytics rulealready configured towhose alerts should runathe playbook, and select Edit.
Select the Automated response tab.
Playbooks directly configured to run from this analytics rule can be found underAlert automation (classic). Notice the warning about deprecation.
In the upper half of the screen, selectSelect + Add new under Automation rules to create a new automation rule.In the Create new automation rule panel, under Trigger, select When alert is created.


Select Apply. The new rule shows in the automation rules grid.
Remove the playbook from theAlert automation (classic)section.Review and update the analytics rule to save your changes.
Create a new automation rule from the Automation page
Use this procedure if you're migratingto run a playbook that's used byfor alerts from multiple analytics rules. Otherwise,For alerts from one analytics rule, use Create an automation rule from an analytics rulerule.
- For Microsoft Sentinel in the Azure portal, select the Configuration > Analytics page. For Microsoft Sentinel in the Defender portal, select Microsoft Sentinel > Configuration > Analytics.
- From the top menu bar, select Create -> Automation rule.
- Under Conditions, select the analytics rules you want to run a particular playbook or a set of playbooks on.
- Under Actions, for each playbook you want this rule to invoke, select + Add action. The Run playbook action is automatically selected and grayed out.
- Select from the list of available playbooks in the drop-down list in the line below. Order the actions according to the order in which you want the playbooks to run by selecting the up/down arrows next to each action. \ No newline at end of file
- Select Apply to save the automation rule.
Edit the analytics rule or rules that invoked these playbooks (the rules you specified underConditions), removing the playbook from theAlert automation (classic)section of theAutomated responsetab. \ No newline at end of file\ No newline at end of file
@@ -22,11 +22,11 @@ ms.service: microsoft-sentinel ms.subservice: sentinel-siem search.appverid: met150 ms.reviewer: sshuster-description: This article explains how (and why) to take your existing playbooks built on the alert trigger and migrate them from being invoked by analytics rules to being invoked by automation rules.+description: Configure automation rules to run existing Microsoft Sentinel alert-trigger playbooks that were previously invoked directly by analytics rules. ms.topic: how-to-ms.author: monaberdugo-author: mberdugo-ms.date: 2026-07-01T00:00:00.0000000Z+ms.author: sshuster+author: sshuster+ms.date: 2026-11-08T00:00:00.0000000Z ms.collection: usx-security ai-usage: ai-assisted ms.custom: msecd-doc-authoring-1016@@ -54,10 +54,10 @@ platformId: 98885ae6-4469-561e-8c18-be67565005ed # Migrate Microsoft Sentinel alert-trigger playbooks to automation rules | Microsoft Learn -We recommend that you migrate existing playbooks built on alert triggers and migrate them from being invoked by **analytics rules** to being invoked by **automation rules**. This article explains why we recommend migrating playbooks from analytics rules to automation rules, and how to do it. Before you begin, review the Prerequisites.
+Configure **automation rules** to run existing alert-trigger playbooks that were previously invoked directly by **analytics rules**. The playbooks and their Microsoft Sentinel Alert triggers remain supported; only direct invocation from analytics rules was deprecated. Before you begin, review the Prerequisites.
-- If you're migrating a playbook that's used by only one analytics rule, follow the instructions under Create an automation rule from an analytics rule.
-- If you're migrating a playbook that's used by multiple analytics rules, follow the instructions under Create a new automation rule from the Automation page.
+- To run a playbook for alerts from one analytics rule, follow the instructions under Create an automation rule from an analytics rule.
+- To run a playbook for alerts from multiple analytics rules, follow the instructions under Create a new automation rule from the Automation page.
Important
@@ -67,16 +67,16 @@ If you're still using Microsoft Sentinel in the Azure portal, we recommend that
## Why migrate
-Playbooks that are invoked by automation rules instead of analytics rules have the following advantages:
+Automation rules provide the following capabilities for alert-trigger playbooks:
- Automation management from a single display, regardless of type (“single pane of glass”).
- Use a single automation rule triggering playbooks for multiple analytics rules, instead of configuring each analytics rule separately.
- Define the order in which alert playbooks are to be executed.
- Support for scenarios that set an expiration date for running a playbook.
-Migrating your playbook trigger doesn't change the playbook at all, and only changes the mechanism that invokes the playbook to run changes.
+Configuring an automation rule doesn't change the playbook or its Logic Apps trigger. It changes only the mechanism that invokes the playbook.
-The ability to invoke playbooks from analytics rules will be **deprecated effective March 2026**. Until then, playbooks already defined as from analytics rules will continue to run, but as of **June 2023** you can no longer add playbooks to the list of those invoked from analytics rules. The only remaining option is to invoke them from automation rules.
+Direct invocation of playbooks from analytics rules was deprecated. To run these playbooks automatically when an alert is created, use an automation rule.
## Prerequisites
@@ -89,16 +89,14 @@ To learn more, see [Microsoft Sentinel playbook prerequisites](automate-response
## Create an automation rule from an analytics rule
-Follow these steps to migrate a playbook that's used by only one analytics rule. If the playbook is used by multiple analytics rules, use Create a new automation rule from the Automation page.
+Follow these steps to run a playbook for alerts from one analytics rule. For alerts from multiple analytics rules, use Create a new automation rule from the Automation page.
1. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), select the **Configuration** > **Analytics** page. For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Configuration** > **Analytics**.
-2. Under **Active rules**, find an analytics rule already configured to run a playbook, and select **Edit**.
+2. Under **Active rules**, select the analytics rule whose alerts should run the playbook, and select **Edit**.

-3. Select the **Automated response** tab. Playbooks directly configured to run from this analytics rule can be found under **Alert automation (classic)**. Notice the warning about deprecation.
-
- 
-4. In the upper half of the screen, select **+ Add new** under **Automation rules** to create a new automation rule.
+3. Select the **Automated response** tab.
+4. Select **+ Add new** under **Automation rules** to create a new automation rule.
5. In the **Create new automation rule** panel, under **Trigger**, select **When alert is created**.

@@ -106,12 +104,11 @@ Follow these steps to migrate a playbook that's used by only one analytics rule.

7. Select **Apply**. The new rule shows in the automation rules grid.
-8. Remove the playbook from the **Alert automation (classic)** section.
-9. **Review and update** the analytics rule to save your changes.
+8. **Review and update** the analytics rule to save your changes.
## Create a new automation rule from the Automation page
-Use this procedure if you're migrating a playbook that's used by multiple analytics rules. Otherwise, use Create an automation rule from an analytics rule
+Use this procedure to run a playbook for alerts from multiple analytics rules. For alerts from one analytics rule, use Create an automation rule from an analytics rule.
1. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), select the **Configuration** > **Analytics** page. For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Configuration** > **Analytics**.
2. From the top menu bar, select **Create -> Automation rule**.
@@ -119,5 +116,4 @@ Use this procedure if you're migrating a playbook that's used by multiple analyt 4. Under **Conditions**, select the analytics rules you want to run a particular playbook or a set of playbooks on.
5. Under **Actions**, for each playbook you want this rule to invoke, select **+ Add action**. The **Run playbook** action is automatically selected and grayed out.
6. Select from the list of available playbooks in the drop-down list in the line below. Order the actions according to the order in which you want the playbooks to run by selecting the up/down arrows next to each action.
-7. Select **Apply** to save the automation rule.
-8. Edit the analytics rule or rules that invoked these playbooks (the rules you specified under **Conditions**), removing the playbook from the **Alert automation (classic)** section of the **Automated response** tab.\ No newline at end of file+7. Select **Apply** to save the automation rule.\ No newline at end of file 