Automate and Run Microsoft Sentinel Playbooks | Microsoft Learn
In brief
The article now covers Microsoft Defender SOC Logic Apps and generated playbooks, distinguishes them from Sentinel connector Logic Apps, and documents the required Defender unified RBAC, Azure RBAC, and investigation-page access.
What Defender admins need to know
Review permissions for administrators and operators: Logic App playbooks require appropriate Azure roles, while generated playbooks require Defender unified RBAC permissions and no Azure roles.
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.
Automate and runRun Microsoft Sentinel playbooksPlaybooks | Microsoft Learn
Playbooks are collections of procedures that can be run from Microsoft Sentinel in response to an entire incident, to an individual alert, or to a specific entity. A playbook can help automate and orchestrate your response and can be setUse automation rules to run playbooks automatically when specific alerts are generateda case, incident, or when incidents are created or updated, by being attached to an automation rule. Italert matches the rule's trigger and conditions. You can also be run manually on-demand on specific incidents, alerts, or entities.
This article describes how to attach playbooks to analytics rules or automation rules, or run playbooks manually on specificdemand in response to cases, incidents, alerts, or entities. Before you begin, make sure you meet the prerequisites, including required Azure roles and playbook permissions.
Note
Playbooks in Microsoft Sentinel are based on workflows built in Azure Logic Apps, which means that you get all the power, customizability, and built-in templates of Logic Apps. Additional charges might apply. Visit the Azure Logic Apps pricing page for more details.entities, without an automation rule.
Important
If you're still using Microsoft Sentinel in the Azure portal, we recommend that you start planning your transition to the Defender portal to ensure a smooth transition and take full advantage of the unified security operations experience offered by Microsoft Defender.
Note
Azure Logic App playbooks are built on Azure Logic Apps. These playbooks use either the Microsoft Sentinel connector or the Microsoft Defender SOC connector for their triggers and input data. You can customize these workflows and use built-in Logic Apps templates. Additional charges might apply. See the Azure Logic Apps pricing page for details.
The Defender portal also supports generated playbooks, which are code-based workflows, not Logic Apps. For details about the new Logic App connector, see the Microsoft Defender SOC connector reference. For manual execution instructions for all three families, see Run a playbook manually, on demand.
Prerequisites
BeforeThe permissions you start, make sureneed depend on the playbook family and your task. For manual runs, you also need access to the investigation page.
Microsoft Defender unified RBAC permissions
For generated playbooks and Microsoft Defender SOC Logic Apps, your Microsoft Defender unified role-based access control (RBAC) role needs the Automation permission that matches your task:
| Task | Permission |
|---|---|
| Create, manage, and run playbooks | Playbooks with Manage access |
| Run existing playbooks without authoring access | Execute hard actions |
| Create an automation rule | Automation rules with Manage access |
For execution, either playbook permission is sufficient; you have a playbook availabledon't need both.
Azure RBAC permissions
Azure role-based access control (RBAC) permissions are required for Microsoft Defender SOC Logic Apps and Microsoft Sentinel connector Logic Apps. Generated playbooks aren't Logic Apps and don't require these Azure roles.
For Microsoft Defender SOC Logic Apps, you need the appropriate Azure user roles for the Logic App in addition to automate or run, with a trigger, conditions, and actions defined. For more information, see Create and manage Microsoft Sentinel playbooksDefender unified RBAC execution permission. See Azure Logic Apps access permissions.
Required Azure roles to run playbooks
To run playbooks, you needFor Microsoft Sentinel connector Logic Apps, the following Azure roles:roles apply:
| Role | Description |
|---|---|
| Owner or User Access Administrator | |
| Microsoft Sentinel Contributor | Attach a playbook to an |
| Microsoft Sentinel Responder | Access an incident in order to run a playbook manually. To actually run the playbook, you also need the following roles: - Microsoft Sentinel Playbook Operator, to run a playbook manually - Microsoft Sentinel Automation Contributor role, to allow automation rules to run playbooks. |
For more information about required roles and permissions, see playbook prerequisites.
Extra permissions required to run Logic Apps
For Microsoft Sentinel connector Logic Apps, the following service permissions are required to run playbooks on incidentsa case or an incident:
Microsoft Sentinel uses a service account to run playbooks on incidents, to add security and enable the automation rules API to support CI/CD use cases. This service account is used for incident-triggered playbooks, or when you run a playbook manually on a specific incident.
To grant Microsoft Sentinel with the required permissions, you must have an Owner or User access administrator role. To run the playbooks, you'll also need the Logic App Contributor role on the resource group that contains the playbooks you want to run.
For Microsoft Defender SOC Logic Apps on cases or alerts, grant service permissions from the Run playbook panel or from Settings. See Grant permissions for Microsoft Defender SOC Logic Apps.
Configure playbook permissions for cases or incidents in a multitenant deployment
In a multitenant deployment, if the Microsoft Sentinel connector playbook you want to run on a case or incident is in a different tenant, you must grant the Microsoft Sentinel service account with permission to run the playbookit in the playbook's tenant.
Microsoft Defender portal
In the Defender portal, configure permissions in the playbook's tenant:
- From the navigation bar, select Settings > Sentinel.
- Select the workspace, and then select Playbook permissions.
- Select Configure permissions to open the Manage permissions panel.
- Select the resource groups containing the playbooks you want to run, and select Apply.
Azure portal
In the Azure portal, configure permissions in the playbook's tenant:
From the Microsoft Sentinel navigation menu in the playbooks' tenant, select Settings.
In the Settings page, select the Settings tab, then the Playbook permissions expander.

You yourself must have Owner permissions on any resource groupFor setup and execution roles, see Required Azure roles to which you want to grant Microsoft Sentinel permissions, and you must have the Microsoft Sentinel Playbook Operator role on any resource group containing playbooks you want to run.run playbooks.
If, in an MSSPa managed security service provider (MSSP) scenario, you want to run a playbook in a customer tenant from an automation rule created while signed into the service provider tenant, you must grant Microsoft Sentinel permission to run the playbook in both tenants:
- In the customer tenant, follow the standard instructions for the multitenant deployment.
- In the service provider tenant, add the Azure Security Insights app in your Azure Lighthouse onboarding template as follows: }
## Automate responsesRun a playbook manually, on demand
Note
Manual execution of Microsoft Defender SOC Logic Apps and generated playbooks on alerts and cases is in public preview. Existing Microsoft Sentinel connector playbook support isn't part of this preview. The case procedures apply to incidentscases of type **Incident**.
Manually run playbooks on cases, incidents, alerts, or entities. In the Defender portal, use **Run playbook** to start a compatible playbook and alerts
To respond automaticallythe **Runs** tab to entire incidents or individual alerts with a playbook, create anreview execution results. No automation rule that runs whenis required.
The Defender portal supports three playbook families:
- **Microsoft Defender SOC Logic Apps:** Azure Logic Apps using the **Microsoft Defender SOC alert** or **Microsoft Defender SOC case** trigger.
- **Generated playbooks:** Code-based workflows created with Playbook Generator, using alert or case input. Generated playbooks aren't Logic Apps.
- **Microsoft Sentinel connector Logic Apps:** Existing playbooks remain supported on cases and incidents as the incident experience transitions to cases.
Microsoft Defender SOC Logic Apps and generated playbooks don't require a Microsoft Sentinel or Integrated Security Operations Center (ISOC) workspace for manual runs. Execution requires the appropriate entitlement and compatible input. Logic App hosting charges still apply, and third-party data ingested through Log Analytics still requires a workspace.
For generated playbooks, configure the integration profiles and API permissions required by their actions; see [Configure integration profiles](/en-us/defender-xdr/siem-defender-automation-integrations).
### Run a playbook manually on a case
Cases support all three types of playbooks. Run a compatible playbook from the case you're investigating in the Defender portal:
1. Go to **Cases**, select **Incident**, and open the case.
2. Open the three-dot menu. Under **Actions**, select **Run playbook**.

3. In the **Playbooks** tab, select a playbook. The list is created or updated, or whenfiltered to playbooks compatible with the case.
Microsoft Defender SOC Logic Apps in this list use the **Microsoft Defender SOC case** trigger, not the alert is generated. This automation rule includes a step that callstrigger.
[](../media/run-playbooks/defender-case-playbooks.png#lightbox)
4. If the playbook you want to use.
**To create an automation rule**:
1. Fromis inactive, activate it on the **Automation** page inunder the **Playbooks** tab. For a Microsoft Defender SOC Logic App with **Missing permissions**, follow Grant permissions for SOC Logic Apps.
For existing Microsoft Sentinel navigation menu, select **Create** from the top menu and then **Automation rule**. For example:

2. The **Create new automation rule** panel opens. Enter a name for your rule. Your options differ depending on whether your workspace is onboarded to the Microsoft Defender portal. For example:
# [Onboarded workspaces](#tab/after-onboarding)

# [Workspaces that aren't onboarded](#tab/before-onboarding)

---
3. **Trigger:** Select the appropriate trigger according to the circumstance for which you're creating the automation rule — **When incident is created**, **When incident is updated**, or **When alert is created**.
4. **Conditions:**
1. If your workspace isn't yet onboarded to the Defender portal, incidents can have two possible sources:
- Incidents can be created inside Microsoft Sentinel
- Incidents can be [imported from — and synchronized with — Microsoft Defender XDR](../microsoft-365-defender-sentinel-integration).
If you selected one of the incident triggers and you want the automation rule to take effect only on incidents sourced in Microsoft Sentinel, or alternatively in Microsoft Defender XDR, specify the source in the **If Incident provider equals** condition.
This condition is displayed only if an incident trigger is selected and your workspace isn't onboarded to the Defender portal.
2. For all trigger types, if you want the automation rule to take effect only on certain analytics rules, specify which ones by modifying the **If Analytics rule name contains** condition.
3. Add any other conditions you want to determine whether this automation rule runs. Select **+ Add** and select [conditions or condition groups](../add-advanced-conditions-to-automation-rules) from the drop-down list. The list of conditions is populated by alert detail and entity identifier fields.
5. **Actions:**
1. Since you're using this automation rule to run a playbook, select the **Run playbook** action from the drop-down list. You'll then be prompted to select from a second drop-down list that shows the available playbooks. An automation rule can run only those playbooks that start with the same trigger (incident or alert) as the trigger defined in the rule, so only those playbooks appear in the list.
If a playbook appears grayed out in the drop-down list, it means that Microsoft Sentinel doesn't have permission to that playbook's resource group. Select the **Manage playbook permissions** link to assign permissions.
In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**. For example:

You yourself must have **Owner** permissions on any resource group to which you want to grant Microsoft Sentinel permissions, and you must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run.
For more information,connector playbooks, see Extra permissions required to run playbooks on incidents.
2. Add any other actions you wantLogic Apps.
5. Select **Run playbook** for this rule. You can change the order ofplaybook.
6. Review the execution of actions by selecting the up or down arrows to the right of any action.
6. Set an expiration date for your automation rule if you want it to have one.
7. Enter a number under **Order** to determine where in the sequence of automation rules this rule runs.
8. Select **Apply** to complete your automation.
For more information, see [Create and manage Microsoft Sentinel playbooks](create-playbooks).
### Respond to alerts—legacy method
Another way to run playbooksresult.
An alert-input playbook isn't automatically in response to **alerts** is to call them from an **analytics rule**. When the rule generates an alert, the playbook runs.
**Calling playbooks from analytics rules will be deprecated as of March 2026.**
Beginning **June 2023**, you can no longer add playbooks directly from an analytics rule. However, you can still see the existing playbooks called from analytics rules, and these playbooks will still run until March 2026. We strongly encourage you to [create automation rules to call these playbooks instead](migrate-playbooks-to-automation-rules) before then.
## Run a playbook manually, on demand
You can also manually runcompatible with case input. Running a playbook on demand, whether in response to alerts, incidents, or entities. This can be useful in situations where you want more human input into and controla case doesn't imply iteration over orchestration and response processes.the case's child alerts.
### Run a playbook manually on an alert
Running a playbook manually on an alert isn't supported inincident
The incident experience is being upgraded to the Defender portal.
Infull case experience, retaining all incident features and adding new capabilities. Use the Azure portal, select one ofcase experience to continue running the following tabs as needed for your environment:
# [Run a playbook from the incident details page](#tab/incidents)
To run a playbook on an alert from the incident details page, perform the following steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **same Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
# [Run a playbook from the investigation graph](#tab/cases)
To run a playbook on an alert from the investigation graph, follow these steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
---
You can see the run history for playbooks on an alert by selecting the **Runs** tab on the **Alert playbooks** pane. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
### Run a playbook manually on an incidentconnector playbooks.
The procedure for manually running a playbook on an incident differs, depending on whether you're working in the Azure portal or in the Defender portal. Select the relevant tab for your environment:
# [Run a playbook on an incident in the Azure portal](#tab/azure)
In the Azure portal, use the following steps to run a playbook on an incident:
1. In the **Incidents** page, select an incident.
2. From the incident details pane that appears on the side, select **Actions > Run playbook**.
Selecting the three dots at the end of the incident's line on the grid or right-clicking the incident displays the same list as the **Action** button.
3. The **Run playbook on incident** panel opens on the side. You see a list of all playbooks configured with the **Microsoft Sentinel Incident** Logic Apps trigger that you have access to.
If you don't see the playbook you want to run in the list, it means Microsoft Sentinel doesn't have permissions to run playbooks in that resource group.
To grant those permissions, select **Settings** > **Settings** > **Playbook permissions** > **Configure permissions**. In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**.
For information, see Extra permissions required to run playbooks on incidents.
4. Select **Run** on the line of a specific playbook to run it immediately.
You must have the **Microsoft Sentinel playbook operator** role on any resource group containing playbooks you want to run. If you're unable to run the playbook due to missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites).
# [Run a playbook on an incident in the Microsoft Defender portal](#tab/microsoft-defender)
In the Microsoft Defender portal, follow these steps to run a playbook on an incident:
1. In the **Incidents** page, select an incident.
2. From the incident details pane that appears on the side, select **Run Playbook**.
3. The **Run playbook on incident** panel opens on the side, with all related playbooks for the selected incident. In the **Action** column, select **Run playbook** for the playbook you want to run immediately.
The **Actions** column might also show one of the following statuses:
| Status | Description and action required |
| --- | --- |
| **Missing permissions** | You must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run. If you're missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites). |
| **Grant permission** | Microsoft Sentinel is missing the **Microsoft Sentinel Automation Contributor** role, which is required to run playbooks on incidents. In such cases, select **Grant permission** to open the **Manage permissions** pane. The **Manage permissions** pane is filtered by default to the selected playbook's resource group. Select the resource group and then select **Apply** to grant the required permissions. You must be an **Owner** or a **User access administrator*Access Administrator** on the resource group to which you want to grant Microsoft Sentinel permissions. If you're missing permissions, the resource group is greyed out and you can't select it. In such cases, we recommend you contact an admin to grant you with the relevant permissions. For more information, see Extra permissions required to run Logic Apps. |
# [Run a playbook on an incident in the Azure portal](#tab/azure)
In the Azure portal, use the following steps to run a playbook on an incident:
1. In the **Incidents** page, select an incident.
2. From the incident details pane that appears on the side, select **Actions > Run playbook**.
Selecting the three dots at the end of the incident's line on the grid or right-clicking the incident displays the same list as the **Action** button.
3. The **Run playbook on incident** panel opens on the side. You see a list of all playbooks configured with the **Microsoft Sentinel Incident** Logic Apps trigger that you have access to.
If you don't see the playbook you want to run in the list, it means Microsoft Sentinel doesn't have permissions to run playbooks in that resource group.
To grant those permissions, select **Settings** > **Settings** > **Playbook permissions** > **Configure permissions**. In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**.
For information, see Extra permissions required to run Logic Apps.
4. Select **Run** on incidents. |the line of a specific playbook to run it immediately.
You must have the **Microsoft Sentinel playbook operator** role on any resource group containing playbooks you want to run. If you're unable to run the playbook due to missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites).
---
View the run history for playbooks on an incident by selecting the **Runs** tab on the **Run playbook on incident** panel. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
### Run a playbook manually on an alert
Select the portal where you want to run the playbook:
# [Microsoft Defender portal](#tab/alert-defender)
Run Microsoft Defender SOC Logic Apps or generated playbooks on alerts in the Defender portal. The **Microsoft Defender SOC alert** trigger supports both Microsoft Defender and Microsoft Sentinel alerts.
In the Defender portal, perform the following steps:
1. On the alert page, in the right side panel, select **Run playbook**.
2. In the **Playbooks** tab, select a playbook. The list shows only alert-trigger Microsoft Defender SOC Logic Apps and generated playbooks with **Alert** input.

3. If the playbook is inactive, activate it on the **Automation** page under the **Playbooks** tab. For a Microsoft Defender SOC Logic App with **Missing permissions**, follow Grant permissions for SOC Logic Apps.
4. Select **Run playbook** on the line of a specific playbook to run it.
5. Review the execution result. A request-accepted acknowledgment doesn't establish that execution completed successfully.
# [Azure portal](#tab/alert-azure)
The following legacy procedures apply only to the Azure portal and run Microsoft Sentinel connector playbooks on alerts. For the Defender portal, select the **Microsoft Defender portal** tab.
##### Run a playbook from the incident details page (legacy, Azure portal)
To run a playbook on an alert from the incident details page, perform the following steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
##### Run a playbook from the investigation graph (legacy, Azure portal)
To run a playbook on an alert from the investigation graph, follow these steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
You can see the run history for playbooks on an alert by selecting the **Runs** tab on the **Alert playbooks** pane. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
---
### Review Defender playbook execution results
Use the **Runs** tab in the **Run playbook** panel to review execution results in one place. A request-accepted acknowledgment doesn't establish that execution completed successfully.
To review a run:
1. In the alert or case's **Run playbook** panel, select **Runs** and find the execution. Check whether it is running, completed, or failed.
2. For a Logic App execution, select **View run** to open the Azure Logic App execution details. Review individual actions and errors to determine the downstream outcome.
3. Review execution results in the related case or incident:
- For a case, open **Artifacts** > **Activities**.
- For an incident, select **Activity**.
For an alert run, use the parent case or incident, not an Alert-local Activity tab. Generated playbooks aren't Logic Apps; review their results in the related case or incident activity, not Azure Logic App execution details.
### Grant permissions for Microsoft Defender SOC Logic Apps
Use this flow when a Microsoft Defender SOC Logic App shows **Missing permissions** in an alert or case's **Run playbook** panel. A user who can run a playbook might need an authorized administrator or author to resolve missing permissions.
If the **Missing permissions** status is shown, select it, browse resource groups, select the relevant resource group, and grant Microsoft Sentinel permissions to run playbooks in that resource group. You can also update permissions from **Settings** > **Sentinel** (select the workspace) > **Playbook permissions** (select **Configure permissions**).

This Logic App permission flow doesn't configure generated-playbook integrations. For generated playbooks, see [Configure integration profiles](/en-us/defender-xdr/siem-defender-automation-integrations).
### Run a playbook manually on an entity
Select**Legacy Azure portal procedures.** The following procedures describe Microsoft Sentinel entity-trigger playbooks in the Azure portal, not entry points on the Defender case page. "New" and "legacy" incident details pages in these tabs refer to versions of the Azure portal experience.
In the Azure portal, select an entity in one of the following ways, depending on your originating context:
# [Run a playbook on an entity from the new incident details page](#tab/incident-details-new)
**If you're in an incident's details page (new version):**
Regardless of the context you came from, the last step in this procedure is from the **Run playbook on *<entity type>*** panel. This panel shows list of all playbooks that you have access to that were configured with the **Microsoft Sentinel Entity** Logic Apps trigger for the selected entity type.
\ No newline at end of file
On the **Run playbook on \*<entity type>** pane, select the **Runs** tab to see the playbook run history for a given entity. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
\ No newline at end### Optional: Create a playbook from an alert or case
If you need a new playbook while investigating an alert or case, you can start creating one from the **Run playbook** panel. This is an optional authoring shortcut, separate from running playbooks and reviewing results.
To start creating a playbook:
1. Open **Run playbook** from the alert or case.
2. Select **Create**, and choose the playbook family:
| Option | Authoring guidance |
| --- | --- |
| **Create generated playbook** | Create a code-based workflow with the required alert or case input. See [Generate a playbook](/en-us/defender-xdr/siem-defender-generate-playbooks#generate-a-playbook). |
| **Create Logic App** | Create a workflow using the [Microsoft Defender SOC connector](/en-us/connectors/defendersoc/). |
The available Logic App options depend on the investigation:
| Investigation | Logic App options |
| --- | --- |
| Alert | **Playbook with alert trigger**, **Blank playbook**. |
| Case | **Playbook with case trigger**, **Blank playbook**. |
3. Follow the authoring guidance for the chosen family. Review and test the workflow before use. Saving a generated playbook leaves it disabled; [activate the generated playbook](/en-us/defender-xdr/siem-defender-generate-playbooks#activate-a-generated-playbook) before running it.
The contextual menu doesn't offer creation of fileexisting Microsoft Sentinel connector playbooks. For authoring permissions, see Prerequisites.
## Automate responses to cases, incidents, and alerts
Use an automation rule to run a playbook automatically when a case, incident, or alert matches the rule's trigger and conditions. For setup instructions, see:
- [Create Microsoft Sentinel automation rules](../create-manage-use-automation-rules#create-your-automation-rule), including the [Run playbook action](../create-manage-use-automation-rules#add-actions).
- [Run a generated playbook when a case is created or updated](/en-us/defender-xdr/siem-defender-generate-playbooks#run-a-generated-playbook-when-an-incident-case-is-created-or-updated).
\ No newline at end of file
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Automate and run Microsoft Sentinel playbooks | Microsoft Learn+title: Automate and Run Microsoft Sentinel Playbooks | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/azure/sentinel/automation/run-playbooks breadcrumb_path: ../breadcrumb/toc.json feedback_help_link_url: https://learn.microsoft.com/answers/tags/423/microsoft-sentinel/@@ -22,14 +22,14 @@ ms.service: microsoft-sentinel ms.subservice: sentinel-siem search.appverid: met150 ms.reviewer: sshuster-description: Learn how to automate incident response with Microsoft Sentinel playbooks, or run playbooks manually to remediate immediate security threats.-ms.author: monaberdugo-author: mberdugo+description: Learn how to run Microsoft Sentinel and Microsoft Defender playbooks, configure permissions, and review results for security investigations.+ms.author: guyshmeltzer+author: guyshmeltzer ms.topic: how-to-ms.date: 2026-07-01T00:00:00.0000000Z+ms.date: 2026-11-01T00:00:00.0000000Z ms.collection: usx-security ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1016+ms.custom: msecd-doc-authoring-1032 locale: en-us document_id: a37eabcb-35e3-d257-8b1a-9ed19319b488 document_version_independent_id: 3508a767-2ee2-16ba-e489-d2ccba7b64d6@@ -45,22 +45,18 @@ item_type: Content source_path: sentinel/automation/run-playbooks.md cmProducts: - https://authoring-docs-microsoft.poolparty.biz/devrel/8a94907f-2511-4271-b5ca-ec7f2e75067c-- https://authoring-docs-microsoft.poolparty.biz/devrel/43093068-2dda-408b-b3fe-dfd705c84f78+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/c671beaa-a830-4c9f-aceb-97379ee031ca+- https://authoring-docs-microsoft.poolparty.biz/devrel/e60d1924-c4ad-4104-bd1b-973758bbac7a spProducts: - https://authoring-docs-microsoft.poolparty.biz/devrel/bffa8e88-f633-409d-a24d-083bdbc68872-- https://authoring-docs-microsoft.poolparty.biz/devrel/e453d60d-ba7e-43bc-8028-ec38e6b62512+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/8921374c-4dbe-4ed0-b011-a39e18bfbd98+- https://authoring-docs-microsoft.poolparty.biz/devrel/91d5f984-ee3d-43c4-9daf-bb09a6bc4e1a platformId: 5b1e0c92-618f-a617-919a-2dea7d0396cc --- -# Automate and run Microsoft Sentinel playbooks | Microsoft Learn+# Automate and Run Microsoft Sentinel Playbooks | Microsoft Learn -Playbooks are collections of procedures that can be run from Microsoft Sentinel in response to an entire incident, to an individual alert, or to a specific entity. A playbook can help automate and orchestrate your response and can be set to run automatically when specific alerts are generated or when incidents are created or updated, by being attached to an automation rule. It can also be run manually on-demand on specific incidents, alerts, or entities.
-
-This article describes how to attach playbooks to analytics rules or automation rules, or run playbooks manually on specific incidents, alerts, or entities. Before you begin, make sure you meet the prerequisites, including required Azure roles and playbook permissions.
-
-Note
-
-Playbooks in Microsoft Sentinel are based on workflows built in [Azure Logic Apps](/en-us/azure/logic-apps/logic-apps-overview), which means that you get all the power, customizability, and built-in templates of Logic Apps. Additional charges might apply. Visit the [Azure Logic Apps](https://azure.microsoft.com/pricing/details/logic-apps/) pricing page for more details.
+Use automation rules to run playbooks automatically when a case, incident, or alert matches the rule's trigger and conditions. You can also run playbooks manually on demand in response to cases, incidents, alerts, or entities, without an automation rule.
Important
@@ -68,23 +64,49 @@ After **March 31, 2027**, Microsoft Sentinel will no longer be supported in the
If you're still using Microsoft Sentinel in the Azure portal, we recommend that you start planning your [transition to the Defender portal](../move-to-defender) to ensure a smooth transition and take full advantage of the [unified security operations experience offered by Microsoft Defender](/en-us/defender-xdr/isoc-overview).
+Note
+
+Azure Logic App playbooks are built on [Azure Logic Apps](/en-us/azure/logic-apps/logic-apps-overview). These playbooks use either the Microsoft Sentinel connector or the Microsoft Defender SOC connector for their triggers and input data. You can customize these workflows and use built-in Logic Apps templates. Additional charges might apply. See the [Azure Logic Apps pricing page](https://azure.microsoft.com/pricing/details/logic-apps/) for details.
+
+The Defender portal also supports [generated playbooks](/en-us/defender-xdr/siem-defender-generate-playbooks), which are code-based workflows, not Logic Apps. For details about the new Logic App connector, see the [Microsoft Defender SOC connector reference](/en-us/connectors/defendersoc/). For manual execution instructions for all three families, see Run a playbook manually, on demand.
+
## Prerequisites
-Before you start, make sure that you have a playbook available to automate or run, with a trigger, conditions, and actions defined. For more information, see [Create and manage Microsoft Sentinel playbooks](create-playbooks).
+The permissions you need depend on the playbook family and your task. For manual runs, you also need access to the investigation page.
+
+### Microsoft Defender unified RBAC permissions
+
+For generated playbooks and Microsoft Defender SOC Logic Apps, your Microsoft Defender unified role-based access control (RBAC) role needs the [Automation permission](/en-us/defender-xdr/custom-permissions-details#security-operations--security-data) that matches your task:
+
+| Task | Permission |
+| --- | --- |
+| Create, manage, and run playbooks | **Playbooks** with **Manage** access |
+| Run existing playbooks without authoring access | **Execute hard actions** |
+| Create an automation rule | **Automation rules** with **Manage** access |
+
+For execution, either playbook permission is sufficient; you don't need both.
-### Required Azure roles to run playbooks
+### Azure RBAC permissions
-To run playbooks, you need the following Azure roles:
+Azure role-based access control (RBAC) permissions are required for Microsoft Defender SOC Logic Apps and Microsoft Sentinel connector Logic Apps. Generated playbooks aren't Logic Apps and don't require these Azure roles.
+
+For Microsoft Defender SOC Logic Apps, you need the appropriate Azure user roles for the Logic App in addition to Defender unified RBAC execution permission. See [Azure Logic Apps access permissions](/en-us/azure/logic-apps/set-up-security-permissions#secure-access-to-logic-app-operations-with-azure-rbac).
+
+#### Required Azure roles to run playbooks
+
+For Microsoft Sentinel connector Logic Apps, the following Azure roles apply:
| Role | Description |
| --- | --- |
-| **Owner** | Lets you grant access to playbooks in the resource group. |
-| **Microsoft Sentinel Contributor** | Attach a playbook to an analytics rule or automation rule |
+| **Owner** or **User Access Administrator** | Grant Microsoft Sentinel access to playbooks in the resource group. Elevate only while assigning these service permissions. |
+| **Microsoft Sentinel Contributor** | Attach a playbook to an automation rule |
| **Microsoft Sentinel Responder** | Access an incident in order to run a playbook manually. To actually run the playbook, you also need the following roles: - **Microsoft Sentinel Playbook Operator**, to run a playbook manually - **Microsoft Sentinel Automation Contributor** role, to allow automation rules to run playbooks. |
For more information about required roles and permissions, see [playbook prerequisites](automate-responses-with-playbooks#prerequisites).
-### Extra permissions required to run playbooks on incidents
+#### Extra permissions required to run Logic Apps
+
+For Microsoft Sentinel connector Logic Apps, the following service permissions are required to run playbooks on a case or an incident:
Microsoft Sentinel uses a service account to run playbooks on incidents, to add security and enable the automation rules API to support CI/CD use cases. This service account is used for incident-triggered playbooks, or when you run a playbook manually on a specific incident.
@@ -92,9 +114,24 @@ In addition to your own roles and permissions, this Microsoft Sentinel service a
To grant Microsoft Sentinel with the required permissions, you must have an **Owner** or **User access administrator** role. To run the playbooks, you'll also need the **Logic App Contributor** role on the resource group that contains the playbooks you want to run.
-### Configure playbook permissions for incidents in a multitenant deployment
+For Microsoft Defender SOC Logic Apps on cases or alerts, grant service permissions from the **Run playbook** panel or from **Settings**. See Grant permissions for Microsoft Defender SOC Logic Apps.
+
+#### Configure playbook permissions for cases or incidents in a multitenant deployment
+
+In a multitenant deployment, if the Microsoft Sentinel connector playbook you want to run on a case or incident is in a different tenant, grant the Microsoft Sentinel service account permission to run it in the playbook's tenant.
+
+##### Microsoft Defender portal
-In a multitenant deployment, if the playbook you want to run is in a different tenant, you must grant the Microsoft Sentinel service account with permission to run the playbook in the playbook's tenant.
+In the Defender portal, configure permissions in the playbook's tenant:
+
+1. From the navigation bar, select **Settings** > **Sentinel**.
+2. Select the workspace, and then select **Playbook permissions**.
+3. Select **Configure permissions** to open the **Manage permissions** panel.
+4. Select the resource groups containing the playbooks you want to run, and select **Apply**.
+
+##### Azure portal
+
+In the Azure portal, configure permissions in the playbook's tenant:
1. From the Microsoft Sentinel navigation menu in the playbooks' tenant, select **Settings**.
2. In the **Settings** page, select the **Settings** tab, then the **Playbook permissions** expander.
@@ -103,9 +140,9 @@ In a multitenant deployment, if the playbook you want to run is in a different t

-You yourself must have **Owner** permissions on any resource group to which you want to grant Microsoft Sentinel permissions, and you must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run.
+For setup and execution roles, see Required Azure roles to run playbooks.
-If, in an MSSP scenario, you want to [run a playbook in a customer tenant](../automate-incident-handling-with-automation-rules#permissions-in-a-multitenant-architecture) from an automation rule created while signed into the service provider tenant, you must grant Microsoft Sentinel permission to run the playbook in both tenants:
+If, in a managed security service provider (MSSP) scenario, you want to [run a playbook in a customer tenant](../automate-incident-handling-with-automation-rules#permissions-in-a-multitenant-architecture) from an automation rule created while signed into the service provider tenant, you must grant Microsoft Sentinel permission to run the playbook in both tenants:
- **In the customer tenant**, follow the standard instructions for the multitenant deployment.
- **In the service provider tenant**, add the Azure Security Insights app in your Azure Lighthouse onboarding template as follows:
@@ -125,76 +162,109 @@ The **Microsoft Sentinel Automation Contributor** role has a fixed GUID of `f4c8 }
```
-## Automate responses to incidents and alerts
+## Run a playbook manually, on demand
-To respond automatically to entire incidents or individual alerts with a playbook, create an automation rule that runs when the incident is created or updated, or when the alert is generated. This automation rule includes a step that calls the playbook you want to use.
+Note
-**To create an automation rule**:
+Manual execution of Microsoft Defender SOC Logic Apps and generated playbooks on alerts and cases is in public preview. Existing Microsoft Sentinel connector playbook support isn't part of this preview. The case procedures apply to cases of type **Incident**.
-1. From the **Automation** page in the Microsoft Sentinel navigation menu, select **Create** from the top menu and then **Automation rule**. For example:
+Manually run playbooks on cases, incidents, alerts, or entities. In the Defender portal, use **Run playbook** to start a compatible playbook and the **Runs** tab to review execution results. No automation rule is required.
- 
-2. The **Create new automation rule** panel opens. Enter a name for your rule. Your options differ depending on whether your workspace is onboarded to the Microsoft Defender portal. For example:
+The Defender portal supports three playbook families:
-# [Onboarded workspaces](#tab/after-onboarding)
-
+- **Microsoft Defender SOC Logic Apps:** Azure Logic Apps using the **Microsoft Defender SOC alert** or **Microsoft Defender SOC case** trigger.
+- **Generated playbooks:** Code-based workflows created with Playbook Generator, using alert or case input. Generated playbooks aren't Logic Apps.
+- **Microsoft Sentinel connector Logic Apps:** Existing playbooks remain supported on cases and incidents as the incident experience transitions to cases.
-# [Workspaces that aren't onboarded](#tab/before-onboarding)
-
+Microsoft Defender SOC Logic Apps and generated playbooks don't require a Microsoft Sentinel or Integrated Security Operations Center (ISOC) workspace for manual runs. Execution requires the appropriate entitlement and compatible input. Logic App hosting charges still apply, and third-party data ingested through Log Analytics still requires a workspace.
----
-3. **Trigger:** Select the appropriate trigger according to the circumstance for which you're creating the automation rule — **When incident is created**, **When incident is updated**, or **When alert is created**.
-4. **Conditions:**
+For generated playbooks, configure the integration profiles and API permissions required by their actions; see [Configure integration profiles](/en-us/defender-xdr/siem-defender-automation-integrations).
- 1. If your workspace isn't yet onboarded to the Defender portal, incidents can have two possible sources:
+### Run a playbook manually on a case
- - Incidents can be created inside Microsoft Sentinel
- - Incidents can be [imported from — and synchronized with — Microsoft Defender XDR](../microsoft-365-defender-sentinel-integration).
+Cases support all three types of playbooks. Run a compatible playbook from the case you're investigating in the Defender portal:
- If you selected one of the incident triggers and you want the automation rule to take effect only on incidents sourced in Microsoft Sentinel, or alternatively in Microsoft Defender XDR, specify the source in the **If Incident provider equals** condition.
+1. Go to **Cases**, select **Incident**, and open the case.
+2. Open the three-dot menu. Under **Actions**, select **Run playbook**.
- This condition is displayed only if an incident trigger is selected and your workspace isn't onboarded to the Defender portal.
- 2. For all trigger types, if you want the automation rule to take effect only on certain analytics rules, specify which ones by modifying the **If Analytics rule name contains** condition.
- 3. Add any other conditions you want to determine whether this automation rule runs. Select **+ Add** and select [conditions or condition groups](../add-advanced-conditions-to-automation-rules) from the drop-down list. The list of conditions is populated by alert detail and entity identifier fields.
-5. **Actions:**
+ 
+3. In the **Playbooks** tab, select a playbook. The list is filtered to playbooks compatible with the case.
- 1. Since you're using this automation rule to run a playbook, select the **Run playbook** action from the drop-down list. You'll then be prompted to select from a second drop-down list that shows the available playbooks. An automation rule can run only those playbooks that start with the same trigger (incident or alert) as the trigger defined in the rule, so only those playbooks appear in the list.
+ Microsoft Defender SOC Logic Apps in this list use the **Microsoft Defender SOC case** trigger, not the alert trigger.
- If a playbook appears grayed out in the drop-down list, it means that Microsoft Sentinel doesn't have permission to that playbook's resource group. Select the **Manage playbook permissions** link to assign permissions.
+ [](../media/run-playbooks/defender-case-playbooks.png#lightbox)
+4. If the playbook is inactive, activate it on the **Automation** page under the **Playbooks** tab. For a Microsoft Defender SOC Logic App with **Missing permissions**, follow Grant permissions for SOC Logic Apps.
- In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**. For example:
+ For existing Microsoft Sentinel connector playbooks, see Extra permissions required to run Logic Apps.
+5. Select **Run playbook** for the playbook.
+6. Review the execution result.
- 
+An alert-input playbook isn't automatically compatible with case input. Running a playbook on a case doesn't imply iteration over the case's child alerts.
- You yourself must have **Owner** permissions on any resource group to which you want to grant Microsoft Sentinel permissions, and you must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run.
+### Run a playbook manually on an incident
- For more information, see Extra permissions required to run playbooks on incidents.
- 2. Add any other actions you want for this rule. You can change the order of execution of actions by selecting the up or down arrows to the right of any action.
-6. Set an expiration date for your automation rule if you want it to have one.
-7. Enter a number under **Order** to determine where in the sequence of automation rules this rule runs.
-8. Select **Apply** to complete your automation.
+The incident experience is being upgraded to the full case experience, retaining all incident features and adding new capabilities. Use the case experience to continue running the same Microsoft Sentinel connector playbooks.
-For more information, see [Create and manage Microsoft Sentinel playbooks](create-playbooks).
+The procedure for manually running a playbook on an incident differs, depending on whether you're working in the Azure portal or in the Defender portal. Select the relevant tab for your environment:
-### Respond to alerts—legacy method
+# [Run a playbook on an incident in the Microsoft Defender portal](#tab/microsoft-defender)
+In the Microsoft Defender portal, follow these steps to run a playbook on an incident:
-Another way to run playbooks automatically in response to **alerts** is to call them from an **analytics rule**. When the rule generates an alert, the playbook runs.
+1. In the **Incidents** page, select an incident.
+2. From the incident details pane that appears on the side, select **Run Playbook**.
+3. The **Run playbook on incident** panel opens on the side, with all related playbooks for the selected incident. In the **Action** column, select **Run playbook** for the playbook you want to run immediately.
-**Calling playbooks from analytics rules will be deprecated as of March 2026.**
+The **Actions** column might also show one of the following statuses:
-Beginning **June 2023**, you can no longer add playbooks directly from an analytics rule. However, you can still see the existing playbooks called from analytics rules, and these playbooks will still run until March 2026. We strongly encourage you to [create automation rules to call these playbooks instead](migrate-playbooks-to-automation-rules) before then.
+| Status | Description and action required |
+| --- | --- |
+| **Missing permissions** | You must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run. If you're missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites). |
+| **Grant permission** | Microsoft Sentinel is missing the **Microsoft Sentinel Automation Contributor** role, which is required to run playbooks on incidents. In such cases, select **Grant permission** to open the **Manage permissions** pane. The **Manage permissions** pane is filtered by default to the selected playbook's resource group. Select the resource group and then select **Apply** to grant the required permissions. You must be an **Owner** or a **User Access Administrator** on the resource group to which you want to grant Microsoft Sentinel permissions. If you're missing permissions, the resource group is greyed out and you can't select it. In such cases, we recommend you contact an admin to grant you with the relevant permissions. For more information, see Extra permissions required to run Logic Apps. |
-## Run a playbook manually, on demand
+# [Run a playbook on an incident in the Azure portal](#tab/azure)
+In the Azure portal, use the following steps to run a playbook on an incident:
+
+1. In the **Incidents** page, select an incident.
+2. From the incident details pane that appears on the side, select **Actions > Run playbook**.
+
+ Selecting the three dots at the end of the incident's line on the grid or right-clicking the incident displays the same list as the **Action** button.
+3. The **Run playbook on incident** panel opens on the side. You see a list of all playbooks configured with the **Microsoft Sentinel Incident** Logic Apps trigger that you have access to.
+
+ If you don't see the playbook you want to run in the list, it means Microsoft Sentinel doesn't have permissions to run playbooks in that resource group.
+
+ To grant those permissions, select **Settings** > **Settings** > **Playbook permissions** > **Configure permissions**. In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**.
+
+ For information, see Extra permissions required to run Logic Apps.
+4. Select **Run** on the line of a specific playbook to run it immediately.
-You can also manually run a playbook on demand, whether in response to alerts, incidents, or entities. This can be useful in situations where you want more human input into and control over orchestration and response processes.
+ You must have the **Microsoft Sentinel playbook operator** role on any resource group containing playbooks you want to run. If you're unable to run the playbook due to missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites).
+
+---
+
+View the run history for playbooks on an incident by selecting the **Runs** tab on the **Run playbook on incident** panel. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
### Run a playbook manually on an alert
-Running a playbook manually on an alert isn't supported in the Defender portal.
+Select the portal where you want to run the playbook:
+
+# [Microsoft Defender portal](#tab/alert-defender)
+Run Microsoft Defender SOC Logic Apps or generated playbooks on alerts in the Defender portal. The **Microsoft Defender SOC alert** trigger supports both Microsoft Defender and Microsoft Sentinel alerts.
+
+In the Defender portal, perform the following steps:
-In the Azure portal, select one of the following tabs as needed for your environment:
+1. On the alert page, in the right side panel, select **Run playbook**.
+2. In the **Playbooks** tab, select a playbook. The list shows only alert-trigger Microsoft Defender SOC Logic Apps and generated playbooks with **Alert** input.
+
+ 
+3. If the playbook is inactive, activate it on the **Automation** page under the **Playbooks** tab. For a Microsoft Defender SOC Logic App with **Missing permissions**, follow Grant permissions for SOC Logic Apps.
+4. Select **Run playbook** on the line of a specific playbook to run it.
+5. Review the execution result. A request-accepted acknowledgment doesn't establish that execution completed successfully.
+
+# [Azure portal](#tab/alert-azure)
+The following legacy procedures apply only to the Azure portal and run Microsoft Sentinel connector playbooks on alerts. For the Defender portal, select the **Microsoft Defender portal** tab.
+
+##### Run a playbook from the incident details page (legacy, Azure portal)
-# [Run a playbook from the incident details page](#tab/incidents)
To run a playbook on an alert from the incident details page, perform the following steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
@@ -204,7 +274,8 @@ To run a playbook on an alert from the incident details page, perform the follow 3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
-# [Run a playbook from the investigation graph](#tab/cases)
+##### Run a playbook from the investigation graph (legacy, Azure portal)
+
To run a playbook on an alert from the investigation graph, follow these steps:
1. In the **Incidents** page, select an incident, and then select **View full details** to open the incident details page.
@@ -212,53 +283,40 @@ To run a playbook on an alert from the investigation graph, follow these steps: 3. The **Alert playbooks** pane opens. You see a list of all playbooks configured with the **Microsoft Sentinel Alert** Logic Apps trigger that you have access to.
4. Select **Run** on the line of a specific playbook to run it immediately.
----
-
You can see the run history for playbooks on an alert by selecting the **Runs** tab on the **Alert playbooks** pane. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
-### Run a playbook manually on an incident
-
-The procedure for manually running a playbook on an incident differs, depending on whether you're working in the Azure portal or in the Defender portal. Select the relevant tab for your environment:
-
-# [Run a playbook on an incident in the Azure portal](#tab/azure)
-In the Azure portal, use the following steps to run a playbook on an incident:
-
-1. In the **Incidents** page, select an incident.
-2. From the incident details pane that appears on the side, select **Actions > Run playbook**.
+---
- Selecting the three dots at the end of the incident's line on the grid or right-clicking the incident displays the same list as the **Action** button.
-3. The **Run playbook on incident** panel opens on the side. You see a list of all playbooks configured with the **Microsoft Sentinel Incident** Logic Apps trigger that you have access to.
+### Review Defender playbook execution results
- If you don't see the playbook you want to run in the list, it means Microsoft Sentinel doesn't have permissions to run playbooks in that resource group.
+Use the **Runs** tab in the **Run playbook** panel to review execution results in one place. A request-accepted acknowledgment doesn't establish that execution completed successfully.
- To grant those permissions, select **Settings** > **Settings** > **Playbook permissions** > **Configure permissions**. In the **Manage permissions** panel that opens up, mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**.
+To review a run:
- For information, see Extra permissions required to run playbooks on incidents.
-4. Select **Run** on the line of a specific playbook to run it immediately.
+1. In the alert or case's **Run playbook** panel, select **Runs** and find the execution. Check whether it is running, completed, or failed.
+2. For a Logic App execution, select **View run** to open the Azure Logic App execution details. Review individual actions and errors to determine the downstream outcome.
+3. Review execution results in the related case or incident:
- You must have the **Microsoft Sentinel playbook operator** role on any resource group containing playbooks you want to run. If you're unable to run the playbook due to missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites).
+ - For a case, open **Artifacts** > **Activities**.
+ - For an incident, select **Activity**.
-# [Run a playbook on an incident in the Microsoft Defender portal](#tab/microsoft-defender)
-In the Microsoft Defender portal, follow these steps to run a playbook on an incident:
+ For an alert run, use the parent case or incident, not an Alert-local Activity tab. Generated playbooks aren't Logic Apps; review their results in the related case or incident activity, not Azure Logic App execution details.
-1. In the **Incidents** page, select an incident.
-2. From the incident details pane that appears on the side, select **Run Playbook**.
-3. The **Run playbook on incident** panel opens on the side, with all related playbooks for the selected incident. In the **Action** column, select **Run playbook** for the playbook you want to run immediately.
+### Grant permissions for Microsoft Defender SOC Logic Apps
-The **Actions** column might also show one of the following statuses:
+Use this flow when a Microsoft Defender SOC Logic App shows **Missing permissions** in an alert or case's **Run playbook** panel. A user who can run a playbook might need an authorized administrator or author to resolve missing permissions.
-| Status | Description and action required |
-| --- | --- |
-| **Missing permissions** | You must have the **Microsoft Sentinel Playbook Operator** role on any resource group containing playbooks you want to run. If you're missing permissions, we recommend you contact an admin to grant you with the relevant permissions. For more information, see [Microsoft Sentinel playbook prerequisites](automate-responses-with-playbooks#prerequisites). |
-| **Grant permission** | Microsoft Sentinel is missing the **Microsoft Sentinel Automation Contributor** role, which is required to run playbooks on incidents. In such cases, select **Grant permission** to open the **Manage permissions** pane. The **Manage permissions** pane is filtered by default to the selected playbook's resource group. Select the resource group and then select **Apply** to grant the required permissions. You must be an **Owner** or a **User access administrator** on the resource group to which you want to grant Microsoft Sentinel permissions. If you're missing permissions, the resource group is greyed out and you can't select it. In such cases, we recommend you contact an admin to grant you with the relevant permissions. For more information, see Extra permissions required to run playbooks on incidents. |
+If the **Missing permissions** status is shown, select it, browse resource groups, select the relevant resource group, and grant Microsoft Sentinel permissions to run playbooks in that resource group. You can also update permissions from **Settings** > **Sentinel** (select the workspace) > **Playbook permissions** (select **Configure permissions**).
----
+
-View the run history for playbooks on an incident by selecting the **Runs** tab on the **Run playbook on incident** panel. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
+This Logic App permission flow doesn't configure generated-playbook integrations. For generated playbooks, see [Configure integration profiles](/en-us/defender-xdr/siem-defender-automation-integrations).
### Run a playbook manually on an entity
-Select an entity in one of the following ways, depending on your originating context:
+**Legacy Azure portal procedures.** The following procedures describe Microsoft Sentinel entity-trigger playbooks in the Azure portal, not entry points on the Defender case page. "New" and "legacy" incident details pages in these tabs refer to versions of the Azure portal experience.
+
+In the Azure portal, select an entity in one of the following ways, depending on your originating context:
# [Run a playbook on an entity from the new incident details page](#tab/incident-details-new)
**If you're in an incident's details page (new version):**
@@ -298,4 +356,35 @@ In the **Entities** widget in the **Overview** tab, locate your entity, and do o
Regardless of the context you came from, the last step in this procedure is from the **Run playbook on *<entity type>*** panel. This panel shows list of all playbooks that you have access to that were configured with the **Microsoft Sentinel Entity** Logic Apps trigger for the selected entity type.
-On the **Run playbook on \*<entity type>** pane, select the **Runs** tab to see the playbook run history for a given entity. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.\ No newline at end of file+On the **Run playbook on \*<entity type>** pane, select the **Runs** tab to see the playbook run history for a given entity. It might take a few seconds for any just-completed run to appear in the list. Selecting a specific run opens the full run log in Logic Apps.
+
+### Optional: Create a playbook from an alert or case
+
+If you need a new playbook while investigating an alert or case, you can start creating one from the **Run playbook** panel. This is an optional authoring shortcut, separate from running playbooks and reviewing results.
+
+To start creating a playbook:
+
+1. Open **Run playbook** from the alert or case.
+2. Select **Create**, and choose the playbook family:
+
+ | Option | Authoring guidance |
+ | --- | --- |
+ | **Create generated playbook** | Create a code-based workflow with the required alert or case input. See [Generate a playbook](/en-us/defender-xdr/siem-defender-generate-playbooks#generate-a-playbook). |
+ | **Create Logic App** | Create a workflow using the [Microsoft Defender SOC connector](/en-us/connectors/defendersoc/). |
+
+ The available Logic App options depend on the investigation:
+
+ | Investigation | Logic App options |
+ | --- | --- |
+ | Alert | **Playbook with alert trigger**, **Blank playbook**. |
+ | Case | **Playbook with case trigger**, **Blank playbook**. |
+3. Follow the authoring guidance for the chosen family. Review and test the workflow before use. Saving a generated playbook leaves it disabled; [activate the generated playbook](/en-us/defender-xdr/siem-defender-generate-playbooks#activate-a-generated-playbook) before running it.
+
+The contextual menu doesn't offer creation of existing Microsoft Sentinel connector playbooks. For authoring permissions, see Prerequisites.
+
+## Automate responses to cases, incidents, and alerts
+
+Use an automation rule to run a playbook automatically when a case, incident, or alert matches the rule's trigger and conditions. For setup instructions, see:
+
+- [Create Microsoft Sentinel automation rules](../create-manage-use-automation-rules#create-your-automation-rule), including the [Run playbook action](../create-manage-use-automation-rules#add-actions).
+- [Run a generated playbook when a case is created or updated](/en-us/defender-xdr/siem-defender-generate-playbooks#run-a-generated-playbook-when-an-incident-case-is-created-or-updated).\ No newline at end of file 