You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/automation/create-playbooks.md
+45-19Lines changed: 45 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,19 +49,15 @@ This article describes how to create and manage Microsoft Sentinel playbooks. Yo
49
49
50
50
Follow these steps to create a new playbook in Microsoft Sentinel:
51
51
52
-
1.Choose your starting point:
52
+
1.In the [Azure portal](https://portal.azure.com) or in the [Defender portal](https://security.microsoft.com/), go to your Microsoft Sentinel workspace. On the workspace menu, under **Configuration**, select **Automation**.
53
53
54
-
- In the [Azure portal](https://portal.azure.com), go to your Microsoft Sentinel workspace. On the workspace menu, under **Configuration**, select **Automation**.
54
+
#### [Azure portal](#tab/azure-portal)
55
+
:::image type="content" source="../media/create-playbooks/add-new-playbook.png" alt-text="Screenshot shows Azure portal and Microsoft Sentinel Automation page with Create selected." lightbox="../media/create-playbooks/add-new-playbook.png":::
55
56
56
-
- In the [Defender portal](https://security.microsoft.com/), go to your Microsoft Sentinel workspace. Select **Microsoft Sentinel** > **Configuration** > **Automation**.
57
-
58
-
#### [Azure portal](#tab/azure-portal)
59
-
:::image type="content" source="../media/create-playbooks/add-new-playbook.png" alt-text="Screenshot shows Azure portal and Microsoft Sentinel Automation page with Create selected." lightbox="../media/create-playbooks/add-new-playbook.png":::
60
-
61
-
#### [Defender portal](#tab/defender-portal)
57
+
#### [Defender portal](#tab/defender-portal)
62
58
:::image type="content" source="../media/create-playbooks/add-new-playbook-defender.png" alt-text="Screenshot shows Defender portal and Microsoft Sentinel Automation page with Create selected." lightbox="../media/create-playbooks/add-new-playbook-defender.png":::
63
59
64
-
---
60
+
---
65
61
66
62
1. From the top menu, select **Create**, and then select one of the following options:
67
63
@@ -93,13 +89,6 @@ Select one of the following tabs for details about how to create a logic app for
93
89
> workflows also support virtual network integration for outbound traffic. For more information, see
94
90
> [Secure traffic between virtual networks and single-tenant Azure Logic Apps using private endpoints](/azure/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint).
95
91
96
-
### Authentication prompts
97
-
98
-
When you add a trigger or subsequent action that requires authentication, you might be prompted to choose from the available authentication types supported by the corresponding resource provider. In this example, a Microsoft Sentinel trigger is the first operation that you add to your workflow. So, the resource provider is Microsoft Sentinel, which supports several authentication options. For more information, see the following documentation:
99
-
100
-
-[**Authenticate playbooks to Microsoft Sentinel**](authenticate-playbooks-to-sentinel.md)
101
-
-[**Supported triggers and actions in Microsoft Sentinel playbooks**](playbook-triggers-actions.md)
102
-
103
92
### [Consumption](#tab/consumption)
104
93
105
94
After you select the trigger, which includes an incident, alert, or entity trigger, the **Create playbook** wizard appears, for example:
@@ -132,6 +121,28 @@ Follow these steps to create your playbook:
1. On the designer, select the Microsoft Sentinel trigger, if not already selected.
125
+
126
+
1. On the **Create connection** pane, follow these steps to provide the required information to connect to Microsoft Sentinel.
127
+
128
+
1. For **Authentication**, select from the following methods, which affect subsequent connection parameters:
129
+
130
+
| Method | Description |
131
+
|--------|-------------|
132
+
|**OAuth**| Open Authorization (OAuth) is a technology standard that lets you authorize an app or service to sign in to another without exposing private information, such as passwords. OAuth 2.0 is the industry protocol for authorization and grants limited access to protected resources. For more information, see the following resources: <br><br>- [What is OAuth](https://www.microsoft.com/security/business/security-101/what-is-oauth)? <br>- [OAuth 2.0 authorization with Microsoft Entra ID](/entra/architecture/auth-oauth2)|
133
+
|**Service principal**| A service principal represents an entity that requires access to resources that are secured by a Microsoft Entra tenant. For more information, see [Service principal object](/entra/identity-platform/app-objects-and-service-principals). |
134
+
|**Managed identity**| An identity that is automatically managed in Microsoft Entra ID. Apps can use this identity to access resources that support Microsoft Entra authentication and to obtain Microsoft Entra tokens without having to manage any credentials. <br><br>For optimal security, Microsoft recommends using a managed identity for authentication when possible. This option provides superior security and helps keep authentication information secure so that you don't have to manage this sensitive information. For more information, see the following resources: <br><br>- [What are managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/overview)? <br>- [Authenticate access and connections to Azure resources with managed identities in Azure Logic Apps](/azure/logic-apps/authenticate-with-managed-identity). |
135
+
136
+
For more information, see [Authentication prompts](#authentication-prompts).
137
+
138
+
1. Based on your selected authentication option, provide the necessary parameter values for the corresponding option.
139
+
140
+
For more information about these parameters, see [Microsoft Sentinel connector reference](/connectors/azuresentinel/).
141
+
142
+
1. For **Tenant ID**, select your [Microsoft Entra tenant ID](/entra/fundamentals/how-to-find-tenant).
143
+
144
+
1. When you finish, select **Sign in**.
145
+
135
146
1. If you previously chose **Playbook with entity trigger**, select the type of entity you want this playbook to receive as an input.
136
147
137
148
:::image type="content" source="../media/create-playbooks/entity-trigger-types.png" alt-text="Screenshot shows Consumption workflow playbook with entity trigger, and available entity types to select for setting the playbook schema." lightbox="../media/create-playbooks/entity-trigger-types.png":::
@@ -241,7 +252,9 @@ Follow these steps to create your Standard logic app:
241
252
242
253
1. Select the trigger that you want to use for your playbook.
243
254
244
-
This example continues with the **Microsoft Sentinel entity** trigger.
255
+
This example continues with the **Microsoft Sentinel entity** trigger.
256
+
257
+
1. On the designer, select the trigger, if not already selected.
245
258
246
259
1. On the **Create connection** pane, provide the required information to connect to Microsoft Sentinel.
247
260
@@ -251,13 +264,17 @@ Follow these steps to create your Standard logic app:
251
264
|--------|-------------|
252
265
|**OAuth**| Open Authorization (OAuth) is a technology standard that lets you authorize an app or service to sign in to another without exposing private information, such as passwords. OAuth 2.0 is the industry protocol for authorization and grants limited access to protected resources. For more information, see the following resources: <br><br>- [What is OAuth](https://www.microsoft.com/security/business/security-101/what-is-oauth)? <br>- [OAuth 2.0 authorization with Microsoft Entra ID](/entra/architecture/auth-oauth2)|
253
266
|**Service principal**| A service principal represents an entity that requires access to resources that are secured by a Microsoft Entra tenant. For more information, see [Service principal object](/entra/identity-platform/app-objects-and-service-principals). |
254
-
|**Managed identity**| An identity that is automatically managed in Microsoft Entra ID. Apps can use this identity to access resources that support Microsoft Entra authentication and to obtain Microsoft Entra tokens without having to manage any credentials. <br><br>For optimal security, Microsoft recommends using a managed identity for authentication when possible. This option provides superior security and helps keep authentication information secure so that you don't have to manage this sensitive information. For more information, see the following resources: <br><br>- [What are managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/overview)? <br>- [Authenticate access and connections to Azure resources with managed identities in Azure Logic Apps](/azure/logic-apps/authenticate-with-managed-identity). |
267
+
|**Managed identity**| An identity that is automatically managed in Microsoft Entra ID. Apps can use this identity to access resources that support Microsoft Entra authentication and to obtain Microsoft Entra tokens without having to manage any credentials. <br><br>For optimal security, Microsoft recommends using a managed identity for authentication when possible. This option provides superior security and helps keep authentication information secure so that you don't have to manage this sensitive information. For more information, see the following resources: <br><br>- [What are managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/overview)? <br>- [Authenticate access and connections to Azure resources with managed identities in Azure Logic Apps](/azure/logic-apps/authenticate-with-managed-identity). |
268
+
269
+
For more information, see [Authentication prompts](#authentication-prompts).
255
270
256
271
1. Based on your selected authentication option, provide the necessary parameter values for the corresponding option.
257
272
258
273
For more information about these parameters, see [Microsoft Sentinel connector reference](/connectors/azuresentinel/).
259
274
260
-
1. When you finish, select **Create new**.
275
+
1. For **Tenant ID**, select your [Microsoft Entra tenant ID](/entra/fundamentals/how-to-find-tenant).
276
+
277
+
1. When you finish, select **Sign in**.
261
278
262
279
1. If you chose **Playbook with entity trigger**, select the type of entity you want this playbook to receive as an input.
263
280
@@ -267,6 +284,15 @@ For more information, see [Supported triggers and actions in Microsoft Sentinel
267
284
268
285
---
269
286
287
+
<aname="authentication-prompts"></a>
288
+
289
+
### Authentication prompts
290
+
291
+
When you add a trigger or subsequent action that requires authentication, you might be prompted to choose from the available authentication types supported by the corresponding resource provider. In this example, a Microsoft Sentinel trigger is the first operation that you add to your workflow. So, the resource provider is Microsoft Sentinel, which supports several authentication options. For more information, see the following documentation:
292
+
293
+
-[**Authenticate playbooks to Microsoft Sentinel**](authenticate-playbooks-to-sentinel.md)
294
+
-[**Supported triggers and actions in Microsoft Sentinel playbooks**](playbook-triggers-actions.md)
295
+
270
296
### Add actions to your playbook
271
297
272
298
Now that you have a workflow for your playbook, define what happens when you call the playbook. Add actions, logical conditions, loops, or switch case conditions, all by selecting the plus sign (**+**) on the designer. For more information, see [Create a workflow with a trigger or action](../../logic-apps/create-workflow-with-trigger-or-action.md).
0 commit comments