Skip to content

Commit 0668c02

Browse files
author
ecfan
committed
Move screenshots into correct folders and fix all art links
1 parent d63d8ad commit 0668c02

35 files changed

+17
-17
lines changed

articles/sentinel/automation/create-playbooks.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,10 +56,10 @@ Follow these steps to create a new playbook in Microsoft Sentinel:
5656
- In the [Defender portal](https://security.microsoft.com/), go to your Microsoft Sentinel workspace. Select **Microsoft Sentinel** > **Configuration** > **Automation**.
5757

5858
#### [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":::
6060

6161
#### [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":::
6363

6464
---
6565

@@ -130,7 +130,7 @@ Follow these steps to create your playbook:
130130

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

133-
:::image type="content" source="../media/create-playbooks/logic-app-blank.png" alt-text="Screenshot shows Consumption workflow designer with selected trigger." lightbox="../media/tutorial-respond-threats-playbook/logic-app-blank.png":::
133+
:::image type="content" source="../media/create-playbooks/logic-app-blank.png" alt-text="Screenshot shows Consumption workflow designer with selected trigger." lightbox="../media/create-playbooks/designer-consumption.png":::
134134

135135
1. If you previously chose **Playbook with entity trigger**, select the type of entity you want this playbook to receive as an input.
136136

articles/sentinel/automation/playbook-recommendations.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -144,41 +144,41 @@ This section provides sample screenshots of how you might use a playbook to upda
144144

145145
**Update an incident based on a new incident** (incident trigger):
146146

147-
![Screenshot of an incident trigger simple update flow example.](../media/playbook-triggers-actions/incident-simple-flow.png)
147+
![Screenshot of an incident trigger simple update flow example.](../media/playbook-recommendations/incident-simple-flow.png)
148148

149149
**Update an incident based on a new alert** (alert trigger):
150150

151-
![Screenshot of an alert trigger simple update incident flow example.](../media/playbook-triggers-actions/alert-update-flow.png)
151+
![Screenshot of an alert trigger simple update incident flow example.](../media/playbook-recommendations/alert-update-flow.png)
152152

153153
### Use incident details in your flow
154154

155155
This section provides sample screenshots of how you might use your playbook to use incident details elsewhere in your flow:
156156

157157
**Send incident details by mail, using a playbook triggered by a new incident**:
158158

159-
![Screenshot of an incident trigger simple get flow example.](../media/playbook-triggers-actions/incident-simple-mail-flow.png)
159+
![Screenshot of an incident trigger simple get flow example.](../media/playbook-recommendations/incident-simple-mail-flow.png)
160160

161161
**Send incident details by mail, using a playbook triggered by a new alert**:
162162

163-
![Screenshot of an alert trigger simple get incident flow example.](../media/playbook-triggers-actions/alert-simple-mail-flow.png)
163+
![Screenshot of an alert trigger simple get incident flow example.](../media/playbook-recommendations/alert-simple-mail-flow.png)
164164

165165
### Add a comment to an incident
166166

167167
This section provides sample screenshots of how you might use your playbook to add comments to an incident:
168168

169169
**Add a comment to an incident, using a playbook triggered by a new incident**:
170170

171-
![Screenshot of an incident trigger simple add comment example.](../media/playbook-triggers-actions/incident-comment.png)
171+
![Screenshot of an incident trigger simple add comment example.](../media/playbook-recommendations/incident-comment.png)
172172

173173
**Add a comment to an incident, using a playbook triggered by a new alert**:
174174

175-
![Screenshot of an alert trigger simple add comment example.](../media/playbook-triggers-actions/alert-comment.png)
175+
![Screenshot of an alert trigger simple add comment example.](../media/playbook-recommendations/alert-comment.png)
176176

177177
### Disable a user
178178

179179
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:
180180

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.":::
182182

183183
## Related content
184184

articles/sentinel/automation/run-playbooks.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ In a multitenant deployment, if the playbook you want to run is in a different t
5454
1. Select the **Configure permissions** button to open the **Manage permissions** panel.
5555
1. Mark the check boxes of the resource groups containing the playbooks you want to run, and select **Apply**. For example:
5656

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.":::
5858

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

@@ -88,17 +88,17 @@ To respond automatically to entire incidents or individual alerts with a playboo
8888

8989
1. From the **Automation** page in the Microsoft Sentinel navigation menu, select **Create** from the top menu and then **Automation rule**. For example:
9090

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.":::
9292

9393
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:
9494

9595
### [Onboarded workspaces](#tab/after-onboarding)
9696

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.":::
9898

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

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.":::
102102

103103
---
104104

@@ -127,7 +127,7 @@ To respond automatically to entire incidents or individual alerts with a playboo
127127

128128
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:
129129

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.":::
131131

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

articles/sentinel/create-manage-use-automation-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,7 @@ If you add a **Run playbook** action, you will be prompted to choose from the dr
261261
- <a name="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.
262262

263263
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**.
264-
:::image type="content" source="./media/tutorial-respond-threats-playbook/manage-permissions.png" alt-text="Manage permissions":::
264+
:::image type="content" source="./media/create-manage-automation-rules/manage-permissions.png" alt-text="Manage permissions":::
265265

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

articles/sentinel/includes/playbooks-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.topic: include
1414
| **Microsoft Sentinel Playbook Operator** | Lets you run a playbook manually. |
1515
| **Microsoft Sentinel Automation Contributor** | Allows automation rules to run playbooks. This role isn't used for any other purpose. |
1616

17-
The following table describes required roles based on whether you select a *Consumption* or *Standard* logic app to create your playbook:
17+
The following table describes required roles based on whether you select a Consumption or Standard logic app to create your playbook:
1818

1919
| Logic app | Azure roles | Description |
2020
|-----------|-------------|-------------|

0 commit comments

Comments
 (0)