Skip to content

Commit 2870142

Browse files
committed
Added screenshots
1 parent d58941f commit 2870142

File tree

7 files changed

+45
-24
lines changed

7 files changed

+45
-24
lines changed
23.4 KB
Loading
47.3 KB
Loading
76.9 KB
Loading
59.7 KB
Loading
19.7 KB
Loading
39.4 KB
Loading

articles/sentinel/tutorial-respond-threats-playbook.md

Lines changed: 45 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -70,16 +70,22 @@ Get a more complete and detailed introduction to automating threat response usin
7070

7171
Follow these steps to create a new playbook in Microsoft Sentinel:
7272

73-
# [Logic Apps Consumption](#tab/LAC)
74-
### Prepare the playbook and Logic App
73+
:::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.":::
7574

7675
1. From the **Microsoft Sentinel** navigation menu, select **Automation**.
7776

78-
1. From the top menu, select **Create** and then, depending on which you want to create, either **Playbook with incident trigger** or **Playbook with alert trigger**.
77+
1. From the top menu, select **Create**.
78+
79+
1. The drop-down menu that appears under **Create** gives you three choices for creating playbooks:
80+
81+
1. If you're creating a **Standard** playbook (the new kind - see [Two types of Logic Apps](automate-responses-with-playbooks.md#two-types-of-logic-apps)), select **Blank playbook** and then follow the steps in the **Logic Apps Standard** tab below.
82+
83+
1. If you're creating a **Consumption** playbook (the orignial, classic kind), then, depending on which trigger you want to use, select either **Playbook with incident trigger** or **Playbook with alert trigger**. Then, continue following the steps in the **Logic Apps Consumption** tab below.
7984

80-
:::image type="content" source="./media/tutorial-respond-threats-playbook/add-new-playbook.png" alt-text="Add a new Consumption playbook.":::
85+
# [Logic Apps Consumption](#tab/LAC)
86+
### Prepare the playbook and Logic App
8187

82-
Either way, the **Create playbook** wizard will appear.
88+
Regardless of which trigger you chose to create your playbook with in the previous step, the **Create playbook** wizard will appear.
8389

8490
:::image type="content" source="./media/tutorial-respond-threats-playbook/create-playbook-LAC.png" alt-text="Create a logic app":::
8591

@@ -105,21 +111,17 @@ Follow these steps to create a new playbook in Microsoft Sentinel:
105111

106112
Review the configuration choices you have made, and select **Create and continue to designer**.
107113

108-
1. Your playbook will take a few minutes to be created and deployed, after which you will see the message "Your deployment is complete" and you will be taken to your new playbook's [Logic App Designer](../logic-apps/logic-apps-overview.md), where you can start designing the workflow.
114+
1. Your playbook will take a few minutes to be created and deployed, after which you will see the message "Your deployment is complete" and you will be taken to your new playbook's [Logic App Designer](../logic-apps/logic-apps-overview.md). The trigger you chose at the beginning will have automatically been added as the first step, and you can continue designing the workflow from there.
109115

110116
:::image type="content" source="media/tutorial-respond-threats-playbook/logic-app-blank-LAC.png" alt-text="Screenshot of logic app designer screen with opening trigger.":::
111117

112118
# [Logic Apps Standard](#tab/LAS)
113119

114120
### Prepare the Logic App and workflow
115121

116-
1. From the **Microsoft Sentinel** navigation menu, select **Automation**.
117-
118-
1. From the top menu, select **Create** and then **Blank playbook**.
119-
120-
:::image type="content" source="./media/tutorial-respond-threats-playbook/add-new-playbook.png" alt-text="Add a new Standard playbook.":::
122+
#### Create a Logic App
121123

122-
A new browser tab will open and take you to the **Create Logic App** wizard.
124+
Since you selected **Blank playbook**, a new browser tab will open and take you to the **Create Logic App** wizard.
123125

124126
:::image type="content" source="./media/tutorial-respond-threats-playbook/create-logic-app-basics.png" alt-text="Create a Standard logic app.":::
125127

@@ -148,36 +150,55 @@ Follow these steps to create a new playbook in Microsoft Sentinel:
148150
> [!NOTE]
149151
> This monitoring is **not required for Microsoft Sentinel** and **will cost you extra**.
150152
151-
1. Select **Next : Review + create >**.
153+
1. If you want you can select **Next : Tags >** to apply tags to this Logic App for resource categorization and billing purposes. Otherwise, select **Review + create**.
152154

153155
1. In the **Review + create** tab:
154156

155157
Review the configuration choices you have made, and select **Create**.
156158

157-
1. Your playbook will take a few minutes to be created and deployed, after which you will see the message "Your deployment is complete" and you will be taken to your new playbook's [Logic App Designer](../logic-apps/logic-apps-overview.md), where you can start designing the workflow. You'll see a screen with a short introductory video and some commonly used Logic App triggers and templates. [Learn more](../logic-apps/logic-apps-create-logic-apps-from-templates.md) about creating a playbook with Logic Apps.
159+
1. Your playbook will take a few minutes to be created and deployed, during which you will see some deployment messages. At the end of the process you will be taken to the final deployment screen where you'll see the message "Your deployment is complete".
160+
161+
Select **Go to resource**. You will be taken to the main page of your new Logic App.
162+
163+
Unlike with classic Consumption playbooks, you're not done yet. Now you must create a workflow.
164+
165+
#### Create a workflow (playbook)
166+
167+
1. Select **Workflows** from the navigation menu of your Logic App page.
168+
169+
1. Select **+ Add** from the button bar at the top (it might take a few seconds for the button to be active).
170+
171+
1. The **New workflow** panel will appear. Enter a name for your workflow.
172+
173+
1. Under **State type**, select **Stateful**.
174+
175+
> [!NOTE]
176+
> Microsoft Sentinel does not currently support Stateless workflows to be used as playbooks.
177+
178+
1. Select **Create**. Your workflow will be saved and will appear in the list of workflows in your Logic App. Select the workflow to proceed.
158179

159-
1. Select the **Blank Logic App** template.
180+
1. You'll enter your workflow's page. Here you can see all the information about your workflow, including a record of all the times it will have run. From the navigation menu, select **Designer**.
160181

161-
:::image type="content" source="./media/tutorial-respond-threats-playbook/choose-playbook-template.png" alt-text="Logic Apps Designer template gallery":::
182+
1. The Designer screen will open and you will immediately be prompted to add a trigger and continue designing the workflow.
162183

163-
### Choose the trigger
184+
:::image type="content" source="media/tutorial-respond-threats-playbook/logic-app-standard-designer.png" alt-text="Screenshot of Logic App Standard designer." lightbox="media/tutorial-respond-threats-playbook/logic-app-standard-designer.png":::
164185

165-
Every playbook must start with a trigger. The trigger defines the action that will start the playbook and the schema that the playbook will expect to receive.
186+
#### Choose the trigger
166187

167-
1. In the search bar, look for Microsoft Sentinel. Select **Microsoft Sentinel** when it appears in the results.
188+
1. Select the **Azure** tab and enter "Sentinel" in the Search line.
168189

169-
1. In the resulting **Triggers** tab, you will see the two triggers offered by Microsoft Sentinel:
170-
- When a response to a Microsoft Sentinel Alert is triggered
171-
- When Microsoft Sentinel incident creation rule was triggered
190+
1. In the **Triggers** tab below, you will see the two triggers offered by Microsoft Sentinel:
191+
- Microsoft Sentinel alert (preview)
192+
- Microsoft Sentinel incident (preview)
172193

173-
Choose the trigger that matches the type of playbook you are creating.
194+
Select the trigger that matches the type of playbook you are creating.
174195

175196
> [!NOTE]
176197
> Remember that only playbooks based on the **incident trigger** can be called by automation rules. Playbooks based on the **alert trigger** must be defined to run directly in [analytics rules](detect-threats-custom.md#set-automated-responses-and-create-the-rule) and can also be run manually.
177198
>
178199
> For more about which trigger to use, see [**Use triggers and actions in Microsoft Sentinel playbooks**](playbook-triggers-actions.md)
179200
180-
:::image type="content" source="./media/tutorial-respond-threats-playbook/choose-trigger.png" alt-text="Choose a trigger for your playbook":::
201+
:::image type="content" source="./media/tutorial-respond-threats-playbook/sentinel-triggers.png" alt-text="Choose a trigger for your playbook":::
181202

182203
> [!NOTE]
183204
> When you choose a trigger, or any subsequent action, you will be asked to authenticate to whichever resource provider you are interacting with. In this case, the provider is Microsoft Sentinel. There are a few different approaches you can take to authentication. For details and instructions, see [**Authenticate playbooks to Microsoft Sentinel**](authenticate-playbooks-to-sentinel.md).

0 commit comments

Comments
 (0)