Skip to content

Commit 0b84adf

Browse files
committed
feedback
1 parent 02caf66 commit 0b84adf

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

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

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,26 +6,28 @@ ms.date: 01/06/2025
66
ms.subservice: sentinel-integration
77
---
88

9-
# Tutorial: Set up automatic sensor disconnection notifications with Microsoft Defender for IoT
9+
# Tutorial: Set up automatic sensor disconnection notifications with Microsoft Defender for IoT and Microsoft Sentinel
1010

11-
This tutorial shows you how to create a [playbook](../../sentinel/tutorial-respond-threats-playbook.md) in Microsoft Sentinel that automatically sends an email notification when a sensor disconnects.
11+
This tutorial shows you how to create a [playbook](../../sentinel/tutorial-respond-threats-playbook.md) in Microsoft Sentinel that automatically sends an email notification when a sensor disconnects from the cloud.
1212

1313
In this tutorial, you:
1414

1515
> [!div class="checklist"]
1616
>
1717
> * Create a playbook to send automatic sensor disconnection notifications
18-
> * Paste the playbook code ino the editor and modify fields
18+
> * Paste the playbook code into the editor and modify fields
1919
> * Set up managed identity for your subscription
20-
> * Verify the sensor status
20+
> * Run a query to confirm that the sensor is offline
2121
2222
## Prerequisites
2323

2424
Before you start, make sure you have:
2525

2626
- Completed [Tutorial: Connect Microsoft Defender for IoT with Microsoft Sentinel](iot-solution.md).
2727

28-
- The subscription ID and the resource group for the relevant subscription. In the Azure portal **Subscriptions** page, copy the subscription ID and save it for a later stage.
28+
- The subscription ID for the relevant subscription. In the Azure portal **Subscriptions** page, copy the subscription ID and save it for a later stage.
29+
30+
- The resource group for the relevant subscription. Learn more about [resource groups](../../azure-resource-manager/management/manage-resource-groups-portal.md).
2931

3032
## Create the playbook
3133

@@ -69,7 +71,7 @@ Before you start, make sure you have:
6971

7072
:::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":::
7173

72-
## Set up managed identity for your subscription
74+
## Set up a managed identity for your subscription
7375

7476
To give the playbook permission to run Keyword Query Language (KQL) queries and get relevant sensor data:
7577

@@ -80,9 +82,9 @@ To give the playbook permission to run Keyword Query Language (KQL) queries and
8082
1. In the **Role** tab, select **Next**.
8183
1. In the **Members** tab, under **Assign access to**, select **Managed Identity**.
8284
1. In the **Select Managed identities** window:
83-
1. Under **Subscription**, select the subscription running Microsoft Sentinel.
84-
1. Under **Managed identity**, select your playbook's name.
85-
1. Under **Select**, select the name of the automation rule you created and select **Select**.
85+
- Under **Subscription**, select the subscription running Microsoft Sentinel.
86+
- The **Managed identity** field is automatically selected.
87+
- Under **Select**, select the name of the playbook you created.
8688

8789
:::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":::
8890

0 commit comments

Comments
 (0)