Microsoft Sentinel
Incidents and response

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 playbook that'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 playbook that'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.

  1. For Microsoft Sentinel in the Azure portal, select the Configuration > Analytics page. For Microsoft Sentinel in the Defender portal, select Microsoft Sentinel > Configuration > Analytics.

  2. Under Active rules, find anselect the analytics rule already configured towhose alerts should run athe playbook, and select Edit.

    Screenshot of finding and selecting an analytics rule.

  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.

    Screenshot of automation rules and playbooks screen.

  4. In the upper half of the screen, selectSelect + 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.

    Screenshot of creating automation rule in analytics rule screen.

    Screenshot of selecting playbook as action in automation rule wizard.

  6. Select Apply. The new rule shows in the automation rules grid.

  7. Remove the playbook from the Alert automation (classic) section.

  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 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.

  1. For Microsoft Sentinel in the Azure portal, select the Configuration > Analytics page. For Microsoft Sentinel in the Defender portal, select Microsoft Sentinel > Configuration > Analytics.
  2. From the top menu bar, select Create -> Automation rule.
  3. Under Conditions, select the analytics rules you want to run a particular playbook or a set of playbooks on.
  4. Under Actions, for each playbook you want this rule to invoke, select + Add action. The Run playbook action is automatically selected and grayed out.
  5. 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
  6. Select Apply to save the automation rule.
  7. 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 \ No newline at end of file