Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/defender-for-iot/organizations/how-to-set-up-snmp-mib-monitoring.md

@@ -63,6 +63,19 @@ Defender for IoT in the Azure portal provides a downloadable MIB file for you to
 
 **To download the SNMP MIB file** from [Defender for IoT](https://portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **More actions** > **Download SNMP MIB file**.
 
+## Query SNMP configuration on the sensor
+
+> [!NOTE]
+> - You can query the SNMP configuration on the sensor in version **25.2.1 or later.**
+
+To validate and query the SNMP MIB monitoring configuration in the OT sensor:
+
+1. In the OT sensor, go to **System settings > Sensor management**
+1. To [access the Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md#defender-for-iot-cli-access), sign in to your OT or Enterprise IoT sensor as the *cyberx* user, using a terminal emulator and SSH.
+1. Run the following query depending on what SNMP version was configured and update the variables accordingly:
+- For version 2 type: `snmpwalk -v 2c -c<community-string> <sensor-ip> isa`
+- For version 3 type: `snmpwalk -v 3 -aMD5|SHA -xDES|AES -A<password> -X<secret-key> -u<username> -|autoPriv <sensor-ip> isa`
+
 ## OT sensor OIDs for manual SNMP configurations
 
 If you're configuring Defender for IoT sensors on your SNMP monitoring system manually, use the following table for reference regarding sensor object identifier values (OIDs):

articles/defender-for-iot/organizations/release-notes.md

@@ -38,6 +38,7 @@ Cloud features may be dependent on a specific sensor version. Such features are
 | Version / Patch |  Release date | Scope     | Supported until |
 | ------- |  ------------ | ----------- | ------------------- |
 | **25.2** | | | |
+| 25.2.1 | 12/2025 | Minor |11/2026 |
 | 25.2.0 | 09/2025 | Major |08/2026 |
 | **25.1** | | | |
 | 25.1.2 | 06/2025 | Minor |05/2026 |
@@ -85,6 +86,14 @@ To understand whether a feature is supported in your sensor version, check the r
 
 ## Versions 25.2.x
 
+### Version 25.2.1
+
+**Release date**: 12/2025
+
+**Supported until**: 11/2026
+
+This version includes bug fixes for stability improvements.
+
 ### Version 25.2.0
 
 **Release date**: 09/2025

articles/defender-for-iot/organizations/whats-new.md

@@ -20,6 +20,12 @@ Features released earlier than nine months ago are described in the [What's new
 
 [!INCLUDE [defender-iot-defender-reference](../includes/defender-for-iot-defender-reference.md)]
 
+## December 2025
+
+|Service area  |Updates  |
+|---------|---------|
+| **OT networks** | Sensor version 25.2.1 is now available. See [release details and updates](release-notes.md#version-2521). |
+
 ## September 2025
 
 |Service area  |Updates  |
@@ -72,16 +78,6 @@ To reduce alert fatigue, multiple versions of the same alert violation and with
 
 The legacy on-premises management console isn't available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [on-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
 
-## December 2024
-
-|Service area  |Updates  |
-|---------|---------|
-| **OT networks** | - [Support Multiple Source Devices in DDoS Attack Alerts](#support-multiple-source-devices-in-ddos-attack-alerts) |
-
-### Support Multiple Source Devices in DDoS Attack Alerts
-
-Alert details now display up to 10 source devices involved in DDoS attack.
-
 ## Next steps
 
 [Getting started with Defender for IoT](getting-started.md)