adding tip about alert dedup

Author: batamig

articles/defender-for-iot/organizations/alerts.md

@@ -1,7 +1,7 @@
 ---
 title: Microsoft Defender for IoT alerts
 description: Learn about Microsoft Defender for IoT alerts across the Azure portal, OT network sensors, and on-premises management consoles.
-ms.date: 12/12/2022
+ms.date: 08/06/2023
 ms.topic: how-to
 ms.custom: enterprise-iot
 ---
@@ -32,11 +32,16 @@ While you can view alert details, investigate alert context, and triage and mana
 |**OT network sensor consoles**     |   Alerts generated by that OT sensor      |    - View the alert's source and destination in the **Device map** <br>- View related events on the **Event timeline**  <br>- Forward alerts directly to partner vendors  <br>- Create alert comments <br> - Create custom alert rules <br>- Unlearn alerts    |
 |**An on-premises management console**     |  Alerts generated by connected OT sensors          |  - Forward alerts directly to partner vendors <br> - Create alert exclusion rules      |
 
+> [!TIP]
+> Any alerts generated from different sensors in the same zone within a 10-minute timeframe, with the same type, status, protocol, and associated devices, are listed as a single, unified alert.
+>
+
 For more information, see:
 
 - [Alert data retention](references-data-retention.md#alert-data-retention)
 - [Accelerating OT alert workflows](#accelerating-ot-alert-workflows)
 - [Alert statuses and triaging options](alerts.md#alert-statuses-and-triaging-options)
+- [Plan OT sites and zones](best-practices/plan-corporate-monitoring.md#plan-ot-sites-and-zones)
 
 Alert options also differ depending on your location and user role. For more information, see [Azure user roles and permissions](roles-azure.md) and [On-premises users and roles](roles-on-premises.md).