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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,10 +56,10 @@ Follow these steps to create a new playbook in Microsoft Sentinel:
56
56
- In the [Defender portal](https://security.microsoft.com/), go to your Microsoft Sentinel workspace. Select **Microsoft Sentinel** > **Configuration** > **Automation**.
57
57
58
58
#### [Azure portal](#tab/azure-portal)
59
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/add-new-playbook.png" alt-text="Screenshot of the menu selection for adding a new playbook in the Automation screen." lightbox="../media/tutorial-respond-threats-playbook/add-new-playbook.png":::
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
60
61
61
#### [Defender portal](#tab/defender-portal)
62
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/add-new-playbook-defender.png" alt-text="Screenshot of the menu selection for adding a new playbook in the Automation screen." lightbox="../media/tutorial-respond-threats-playbook/add-new-playbook-defender.png":::
62
+
:::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
63
64
64
---
65
65
@@ -130,7 +130,7 @@ Follow these steps to create your playbook:
130
130
131
131
Azure takes a few minutes to create and deploy your playbook. After deployment completes, your playbook opens in the Consumption workflow designer for [Azure Logic Apps](/azure/logic-apps/logic-apps-overview). The trigger that you selected earlier automatically appears as the first step in your workflow, so now you can continue building the workflow from here.
Copy file name to clipboardExpand all lines: articles/sentinel/automation/playbook-recommendations.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,41 +144,41 @@ This section provides sample screenshots of how you might use a playbook to upda
144
144
145
145
**Update an incident based on a new incident** (incident trigger):
146
146
147
-

147
+

148
148
149
149
**Update an incident based on a new alert** (alert trigger):
150
150
151
-

151
+

152
152
153
153
### Use incident details in your flow
154
154
155
155
This section provides sample screenshots of how you might use your playbook to use incident details elsewhere in your flow:
156
156
157
157
**Send incident details by mail, using a playbook triggered by a new incident**:
158
158
159
-

159
+

160
160
161
161
**Send incident details by mail, using a playbook triggered by a new alert**:
162
162
163
-

163
+

164
164
165
165
### Add a comment to an incident
166
166
167
167
This section provides sample screenshots of how you might use your playbook to add comments to an incident:
168
168
169
169
**Add a comment to an incident, using a playbook triggered by a new incident**:
170
170
171
-

171
+

172
172
173
173
**Add a comment to an incident, using a playbook triggered by a new alert**:
174
174
175
-

175
+

176
176
177
177
### Disable a user
178
178
179
179
The following screenshot shows an example of how you might use your playbook to disable a user account, based on a Microsoft Sentinel entity trigger:
180
180
181
-
:::image type="content" source="../media/playbook-triggers-actions/entity-trigger-actions.png" alt-text="Screenshot showing actions to take in an entity-trigger playbook to disable a user.":::
181
+
:::image type="content" source="../media/playbook-recommendations/entity-trigger-actions.png" alt-text="Screenshot showing actions to take in an entity-trigger playbook to disable a user.":::
Copy file name to clipboardExpand all lines: articles/sentinel/automation/run-playbooks.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ In a multitenant deployment, if the playbook you want to run is in a different t
54
54
1. Select the **Configure permissions** button to open the **Manage permissions** panel.
55
55
1. Mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**. For example:
56
56
57
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/manage-permissions.png" alt-text="Screenshot that shows the actions section with run playbook selected.":::
57
+
:::image type="content" source="../media/run-playbooks/manage-permissions.png" alt-text="Screenshot that shows the actions section with run playbook selected.":::
58
58
59
59
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.
60
60
@@ -88,17 +88,17 @@ To respond automatically to entire incidents or individual alerts with a playboo
88
88
89
89
1. From the **Automation** page in the Microsoft Sentinel navigation menu, select **Create** from the top menu and then **Automation rule**. For example:
90
90
91
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/add-new-rule.png" alt-text="Screenshot showing how to add a new automation rule.":::
91
+
:::image type="content" source="../media/run-playbooks/add-new-rule.png" alt-text="Screenshot showing how to add a new automation rule.":::
92
92
93
93
1. 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 unified security operations platform. For example:
94
94
95
95
### [Onboarded workspaces](#tab/after-onboarding)
96
96
97
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/create-automation-rule-onboarded.png" alt-text="Screenshot showing the automation rule creation wizard.":::
97
+
:::image type="content" source="../media/run-playbooks/create-automation-rule-onboarded.png" alt-text="Screenshot showing the automation rule creation wizard.":::
98
98
99
99
### [Workspaces that aren't onboarded](#tab/before-onboarding)
100
100
101
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/create-automation-rule.png" alt-text="Screenshot showing the automation rule creation wizard.":::
101
+
:::image type="content" source="../media/run-playbooks/create-automation-rule.png" alt-text="Screenshot showing the automation rule creation wizard.":::
102
102
103
103
---
104
104
@@ -127,7 +127,7 @@ To respond automatically to entire incidents or individual alerts with a playboo
127
127
128
128
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:
129
129
130
-
:::image type="content" source="../media/tutorial-respond-threats-playbook/manage-permissions.png" alt-text="Screenshot that shows the actions section with run playbook selected.":::
130
+
:::image type="content" source="../media/run-playbooks/manage-permissions.png" alt-text="Screenshot that shows the actions section with run playbook selected.":::
131
131
132
132
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.
Copy file name to clipboardExpand all lines: articles/sentinel/create-manage-use-automation-rules.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@ If you add a **Run playbook** action, you will be prompted to choose from the dr
261
261
- <aname="explicit-permissions"></a>Microsoft Sentinel must be granted explicit permissions in order to run playbooks. If a playbook appears "grayed out" in the drop-down list, it means Sentinel does not have permission to that playbook's resource group. Select the **Manage playbook permissions** link to assign permissions.
262
262
263
263
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**.
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 Automation Contributor** role on any resource group containing playbooks you want to run.
0 commit comments