Skip to content

Commit d5a426e

Browse files
committed
Adding screenshots
1 parent 5f1bcf0 commit d5a426e

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

articles/defender-for-iot/organizations/automate-sensor-disconnection-alerts.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,13 +31,20 @@ Before you start, make sure you have:
3131

3232
1. In Microsoft Sentinel, select **Automation**.
3333
1. In the **Automation** page, select **Create > Playbook with alert trigger**.
34+
35+
:::image type="content" source="media/automate-sensor-disconnection-alerts/sentinel-create-playbook.png" alt-text="Screenshot of creating a playbook for Defender for IoT sensor disconnection." lightbox="media/automate-sensor-disconnection-alerts/sentinel-create-playbook.png":::
36+
3437
1. In the **Create playbook** page **Basics** tab, select the subscription and resource group running Microsoft Sentinel, and give the playbook a name.
3538
1. Select **Next: Connections**.
3639
1. In the **Connections** tab, select **Microsoft Sentinel > Connect with managed identity**.
3740
1. Review the playbook information and select **Create playbook**.
41+
42+
:::image type="content" source="media/automate-sensor-disconnection-alerts/sentinel-save-playbook.png" alt-text="Screenshot of reviewing a playbook for Defender for IoT sensor disconnection.":::
3843

3944
When the playbook is ready, Microsoft Sentinel displays a **Deployment successful** message and navigates to the **Logic app designer** page.
4045

46+
:::image type="content" source="media/automate-sensor-disconnection-alerts/sentinel-playbook-successful-message.png" alt-text="Screenshot of a "Deployment successful" message for a playbook that sends Defender for IoT sensor disconnection alerts.":::
47+
4148
## Paste the playbook code and modify fields
4249

4350
1. Select **Logic app code view**, and paste the following code into the editor:
@@ -444,7 +451,9 @@ Before you start, make sure you have:
444451
```
445452

446453
1. Select **Save**.
447-
1. Go back to the **Logic app designer** to view the workflow that the playbook follows.
454+
1. Go back to the **Logic app designer** to view the logic that the playbook follows.
455+
456+
:::image type="content" source="media/automate-sensor-disconnection-alerts/playbook-logic.png" alt-text="Screenshot of a of the playbook logic for Defender for IoT sensor disconnection alerts." lightbox="media/automate-sensor-disconnection-alerts/playbook-logic.png":::
448457

449458
## Set up managed identity for your subscription
450459

@@ -460,8 +469,13 @@ To give the playbook permission to run Keyword Query Language (KQL) queries and
460469
1. Under **Subscription**, select the subscription running Microsoft Sentinel.
461470
1. Under **Managed identity**, select your playbook's name.
462471
1. Under **Select**, select the name of the automation rule you created and select **Select**.
472+
473+
:::image type="content" source="media/automate-sensor-disconnection-alerts/playbook-permissions-managed-identity-members.png" alt-text="Screenshot of a of setting up members for a managed identity while creating a Defender for IoT sensor disconnection alerts playbook." lightbox="media/automate-sensor-disconnection-alerts/playbook-permissions-managed-identity-members.png":::
474+
463475
1. In the editor, select **HTTP2** and verify that the **Authentication Type** is set to **Managed Identity**.
464476

477+
:::image type="content" source="media/automate-sensor-disconnection-alerts/playbook-permissions-managed-identity.png" alt-text="Screenshot of sending up a managed identity for the Defender for IoT sensor disconnection alerts playbook." lightbox="media/automate-sensor-disconnection-alerts/playbook-permissions-managed-identity.png":::
478+
465479
## Verify the sensor status
466480

467481
If you can't create the playbook successfully, run a KQL query in Azure Resource Graph to confirm that the sensor is offline.

0 commit comments

Comments
 (0)