Update how-to-configure-with-sentinel.md

Author: ElazarK

articles/defender-for-iot/organizations/how-to-configure-with-sentinel.md

@@ -2,14 +2,14 @@
 title: Configure Azure Sentinel with Defender for IoT for organizations
 description: Explains how to configure Azure Sentinel to receive data from your Defender for IoT solution.
 ms.topic: how-to
-ms.date: 06/14/2021
+ms.date: 11/04/2021
 ---
 
 # Connect your data from Defender for IoT for organizations to Azure Sentinel (Public preview)
 
 Use the Defender for IoT connector to stream all your Defender for IoT events into Azure Sentinel. 
 
-This integration enables organizations to quickly detect multistage attacks that often cross IT and OT boundaries. Additionally, Defender for IoT’s integration with Azure Sentinel's security orchestration, automation, and response (SOAR) capabilities enables automated response and prevention using built-in OT-optimized playbooks. 
+This integration enables organizations to quickly detect multistage attacks that often cross IT and OT boundaries. Additionally, Defender for IoT’s integration with Azure Sentinel's security orchestration, automation, and response (SOAR) capabilities enables automated response and prevention using built-in OT-optimized playbooks.
 
 ## Prerequisites
 
@@ -24,12 +24,14 @@ This integration enables organizations to quickly detect multistage attacks that
 1. From the bottom of the right pane, click **Open connector page**.
 
 1. Click **Connect**, next to each IoT Hub subscription whose alerts and device alerts you want to stream into Azure Sentinel.
-    - You will receive an error message if Defender for IoT is not enabled on  at least one IoT Hub within a subscription. Enable Defender for IoT within the IoT Hub to remove the error.
 
-1. You can decide whether you want the alerts from Defender for IoT to automatically generate incidents in Azure Sentinel. Under **Create incidents**,  select **Enable** to enable the default analytics rule to automatically create incidents from the generated alerts. This rule can be changed or edited under **Analytics** > **Active rules**.
+    > [!NOTE]
+    > You will receive an error message if Defender for IoT is not enabled on at least one IoT Hub within that subscription. Enable Defender for IoT within the IoT Hub to remove the error.
+
+1. You can decide whether you want the alerts from Defender for IoT to automatically generate incidents in Azure Sentinel. Under **Create incidents**, select **Enable** to enable the default analytics rule to automatically create incidents from the generated alerts. This rule can be changed or edited under **Analytics** > **Active rules**.
 
 > [!NOTE]
-> It can take 10 seconds or more for the **Subscription** list to refresh after making connection changes. 
+> It can take 10 seconds or more for the **Subscription** list to refresh after making connection changes.
 
 ## Log Analytics alert view
 
@@ -51,4 +53,4 @@ After connecting a **Subscription**, the hub data is available in Azure Sentinel
 
 In this document, you learned how to connect Defender for IoT to Azure Sentinel. To learn more about threat detection and security data access, see the following articles:
 
-- Learn how to use Azure Sentinel to [Quickstart: Get started with Azure Sentinel](../../sentinel/get-visibility.md).
+- Learn how to use Azure Sentinel to [Quickstart: Get started with Azure Sentinel](../../sentinel/get-visibility.md)