View and Manage Alerts on your OT Sensor
In brief
The page title and metadata were updated, and alert-viewing, management, and export instructions were reformatted with clearer step numbering and wording.
What Defender admins need to know
Administrators will see a more consistent, easier-to-follow reference when viewing or exporting OT alerts. No action is required.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Sign into your OT sensor console and select the Alerts page on the left.
By default, the following details are shown in the grid:
Name Description Severity A predefined alert severity assigned by the sensor that you can modify as needed, including: Critical, Major, Minor, Warning. Name The alert title Engine The Defender for IoT detection engine that detected the activity and triggered the alert. Last detection The last time the alert was detected.
- If an alert's status is New, and the same traffic is seen again, the Last detection time is updated for the same alert.
- If the alert's status is Closed and traffic is seen again, the Last detection time is not updated, and a new alert is triggered.
Note: While the sensor console displays an alert's Last detection field in real-time, Defender for IoT in the Azure portal may take up to one hour to display the updated time. This display delay explains a scenario where the last detection time in the sensor console isn't the same as the last detection time in the Azure portal.Status The alert status: New, Active, Closed
For more information, see Alert statuses and triaging options.Source Device The source device IP address, MAC, or device name. Id The unique alert ID, aligned with the ID on the Azure portal.
Note: If the alert was merged with other alerts from sensors that detected the same alert, the Azure portal displays the alert ID of the first sensor that generated the alerts.To view more details, select the :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/edit-columns-icon.png" border="false"::: Edit Columns button.
In the Edit Columns pane on the right, select Add Column and any of the following extra columns:
Name Description Destination Device The destination device IP address. First detection The first time the alert activity was detected. ID The alert ID. Last activity The last time the alert was changed, including manual updates for severity or status, or automated changes for device updates or device/alert de-duplication
Filter alerts displayed
For more information, see Alert statuses and triaging options.
To manage alert
status:status:Sign into your OT sensor console and select the Alerts page on the left.
The :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/status-icon.png" border="false"::: Status option is also available on the alert details page.
To learn one or more
alerts:alerts:Sign into your OT sensor console and select the Alerts page on the left, and then do one of the following:
- Select one or more learnable alerts in the grid and then select :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/learn-icon.png" border="false"::: Learn in the toolbar.
- On an alert details page, in the Take Action tab, select Learn.
To mute an
alert:alert:- Sign into your OT sensor console and select the Alerts page on the left.
- Locate the alert you want to mute and open its alert details page.
- On the Take action tab, toggle on the Alert mute option.
To unlearn or unmute an
alert:alert:- Sign into your OT sensor console and select the Alerts page on the left.
- Locate the alert you've learned or muted and open its alert details page.
Export alerts to a CSV file from the main Alerts page. Export alerts one at a time or in bulk.
Export alerts to a PDF file one at a time only, either from the main Alerts page or an alert details page.
To export alerts to a CSV file:file:
Sign into your OT sensor console and select the Alerts page on the left.
In the toolbar above the grid, select Export to CSV.
The file is generated, and you're prompted to open or save itthe file locally.
To export an alert to a PDF file:file:
Sign into your OT sensor console and select the Alerts page on the left, and then do one of the following:
- On the Alerts page, select an alert and then select Export to PDF from the toolbar above the grid.
- On an alerts details page, select Export to PDF.
The file is generated, and you're prompted to save itthe file locally.
Add alert comments
Next step
[!div class="nextstepaction"] Data retention across Microsoft Defender for IoT
@@ -1,9 +1,9 @@ ----title: View and manage alerts on your OT sensor - Microsoft Defender for IoT+title: View and Manage Alerts on your OT Sensor description: Learn about viewing and managing alerts on an OT network sensor.-ms.date: 06/12/2026+ms.date: 07/03/2026 ms.topic: how-to-ms.custom: sfi-image-nochange, msecd-doc-authoring-1014+ms.custom: sfi-image-nochange, msecd-doc-authoring-1016 ai-usage: ai-assisted --- @@ -30,30 +30,28 @@ For more information, see [On-premises users and roles for OT monitoring with De > [!NOTE] > When you view alerts in the Azure portal **Alerts** page, some alerts may not correlate with alerts on specific sensors. For more information, see [Investigate alerts that don't correlate with specific sensors](respond-ot-alert.md#investigate-alerts-that-dont-correlate-with-a-specific-sensor). -1. Sign into your OT sensor console and select the **Alerts** page on the left.-- By default, the following details are shown in the grid:+1. Sign into your OT sensor console and select the **Alerts** page on the left. By default, the following details are shown in the grid: | Name | Description | |--|--| | **Severity** | A predefined alert severity assigned by the sensor that you can modify as needed, including: *Critical*, *Major*, *Minor*, *Warning*. | | **Name** | The alert title | | **Engine** | The [Defender for IoT detection engine](architecture.md#defender-for-iot-analytics-engines) that detected the activity and triggered the alert. |- | **Last detection** | The last time the alert was detected. <br><br>- If an alert's status is **New**, and the same traffic is seen again, the **Last detection** time is updated for the same alert. <br>- If the alert's status is **Closed** and traffic is seen again, the **Last detection** time is *not* updated, and a new alert is triggered.<br><br>**Note**: While the sensor console displays an alert's **Last detection** field in real-time, Defender for IoT in the Azure portal may take up to one hour to display the updated time. This delay explains a scenario where the last detection time in the sensor console isn't the same as the last detection time in the Azure portal. |+ | **Last detection** | The last time the alert was detected. <br><br>- If an alert's status is **New**, and the same traffic is seen again, the **Last detection** time is updated for the same alert. <br>- If the alert's status is **Closed** and traffic is seen again, the **Last detection** time is *not* updated, and a new alert is triggered.<br><br>**Note**: While the sensor console displays an alert's **Last detection** field in real-time, Defender for IoT in the Azure portal may take up to one hour to display the updated time. This display delay explains a scenario where the last detection time in the sensor console isn't the same as the last detection time in the Azure portal. | | **Status** |The alert status: *New*, *Active*, *Closed*<br><br>For more information, see [Alert statuses and triaging options](alerts.md#alert-statuses-and-triaging-options).| | **Source Device** | The source device IP address, MAC, or device name. | | **Id** | The unique alert ID, aligned with the ID on the Azure portal.<br><br> **Note:** If the [alert was merged with other alerts](alerts.md#alert-management-options) from sensors that detected the same alert, the Azure portal displays the alert ID of the first sensor that generated the alerts. | - 1. To view more details, select the :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/edit-columns-icon.png" border="false"::: **Edit Columns** button.+ To view more details, select the :::image type="icon" source="media/how-to-manage-device-inventory-on-the-cloud/edit-columns-icon.png" border="false"::: **Edit Columns** button. - In the **Edit Columns** pane on the right, select **Add Column** and any of the following extra columns:+1. In the **Edit Columns** pane on the right, select **Add Column** and any of the following extra columns: - | Name | Description |- |--|--|- | **Destination Device** | The destination device IP address. |- | **First detection** | The first time the alert activity was detected. |- | **ID** | The alert ID. |- | **Last activity** | The last time the alert was changed, including manual updates for severity or status, or automated changes for device updates or device/alert de-duplication |+ | Name | Description |+ |--|--|+ | **Destination Device** | The destination device IP address. |+ | **First detection** | The first time the alert activity was detected. |+ | **ID** | The alert ID. |+ | **Last activity** | The last time the alert was changed, including manual updates for severity or status, or automated changes for device updates or device/alert de-duplication | ### Filter alerts displayed @@ -97,7 +95,7 @@ Make sure to update your alert status once you've taken remediation steps so tha For more information, see [Alert statuses and triaging options](alerts.md#alert-statuses-and-triaging-options). -- **To manage alert status**:+- To manage alert status: 1. Sign into your OT sensor console and select the **Alerts** page on the left. @@ -107,20 +105,20 @@ For more information, see [Alert statuses and triaging options](alerts.md#alert- The :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/status-icon.png" border="false"::: **Status** option is also available on the alert details page. -- **To learn one or more alerts**:+- To learn one or more alerts: Sign into your OT sensor console and select the **Alerts** page on the left, and then do one of the following: - Select one or more learnable alerts in the grid and then select :::image type="icon" source="media/how-to-manage-sensors-on-the-cloud/learn-icon.png" border="false"::: **Learn** in the toolbar. - On an alert details page, in the **Take Action** tab, select **Learn**. -- **To mute an alert**:+- To mute an alert: 1. Sign into your OT sensor console and select the **Alerts** page on the left. 1. Locate the alert you want to mute and open its alert details page. 1. On the **Take action** tab, toggle on the **Alert mute** option. -- **To unlearn or unmute an alert**:+- To unlearn or unmute an alert: 1. Sign into your OT sensor console and select the **Alerts** page on the left. 1. Locate the alert you've learned or muted and open its alert details page.@@ -147,7 +145,7 @@ You may want to export a selection of alerts to a CSV or PDF file for offline sh - Export alerts to a CSV file from the main **Alerts** page. Export alerts one at a time or in bulk. - Export alerts to a PDF file one at a time only, either from the main **Alerts** page or an alert details page. -**To export alerts to a CSV file**:+To export alerts to a CSV file: 1. Sign into your OT sensor console and select the **Alerts** page on the left. @@ -155,16 +153,16 @@ You may want to export a selection of alerts to a CSV or PDF file for offline sh 1. In the toolbar above the grid, select **Export to CSV**. -The file is generated, and you're prompted to open or save it locally.+The file is generated, and you're prompted to open or save the file locally. -**To export an alert to a PDF file**:+To export an alert to a PDF file: Sign into your OT sensor console and select the **Alerts** page on the left, and then do one of the following: - On the **Alerts** page, select an alert and then select **Export to PDF** from the toolbar above the grid. - On an alerts details page, select **Export to PDF**. -The file is generated, and you're prompted to save it locally.+The file is generated, and you're prompted to save the file locally. ## Add alert comments @@ -203,7 +201,7 @@ To reduce alert fatigue, multiple versions of the same alert violation with iden > [!NOTE] > An alert with specific violations does not prevent new alerts with different violations from appearing. After you learn an alert, the same alert might be triggered again if the new alert has different violation parameters. To check why the alert was triggered, review the list of violations in the alert list (for the first 10 alerts) or the CSV file you downloaded in step 3. -## Next steps+## Next step > [!div class="nextstepaction"] > [Data retention across Microsoft Defender for IoT](references-data-retention.md) 