Merge pull request #271183 from limwainstein/2413-release-notes

24.1.3 what's new and release notes

Author: prmerger-automator[bot]

articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md

@@ -48,7 +48,7 @@ The **Cloud connectivity troubleshooting** pane covers the following types of is
 |**Proxy authentication issues**     |  Occurs when a proxy demands authentication, but no credentials, or incorrect credentials, are provided. <br><br>In such cases, make sure that you've configured the proxy credentials correctly. For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration).      |
 |**Name resolution failures**     | Occurs when the sensor can't perform name resolution for a specific endpoint. <br><br>In such cases, if your DNS server is reachable, make sure that the DNS server is configured on your sensor correctly. If the configuration is correct, we recommend reaching out to your DNS administrator.   <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration).      |
 |**Unreachable proxy server errors**     | Occurs when the sensor can't establish a connection with the proxy server. In such cases, confirm the reachability of your proxy server with your network team.    <br><br>For more information, see [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration).      |
-
+|**Time drift detected** |Occurs when the UTC time of the sensor isn't synchronized with Defender for IoT on the Azure portal.<br><br>In this case, configure a Network Time Protocol (NTP) server to synchronize the sensor in UTC time.<br><br>For more information, see [Configure OT sensor settings from the Azure portal](configure-sensor-settings-portal.md#ntp). |
 
 ## Check system health
 

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 |
 | ------- |  ------------ | ----------- | ------------------- |
 | **24.1** | | | |
+| 24.1.3  |04/2024 | Major |03/2025 |
 | 24.1.2  |02/2024 | Major |01/2025 |
 | **23.1** | | | |
 | 23.1.3 | 09/2023 | Patch | 08/2024 |
@@ -103,14 +104,25 @@ To understand whether a feature is supported in your sensor version, check the r
 
 ## Versions 24.1.x
 
-### Version 24.1.0
+### Version 24.1.3
 
-**Release date**: 02/2024
+**Release date**: 04/2024
 
 **Supported until**: 03/2025
 
 This version includes the following updates and enhancements:
 
+- [Sensor time drift detection](whats-new.md#sensor-time-drift-detection)
+- Bug fixes for stability improvements
+
+### Version 24.1.2
+
+**Release date**: 02/2024
+
+**Supported until**: 01/2025
+
+This version includes the following updates and enhancements:
+
 - [Alert suppression rules from the Azure portal](how-to-accelerate-alert-incident-response.md#suppress-irrelevant-alerts)
 - [Focused alerts in OT/IT environments](alerts.md#focused-alerts-in-otit-environments)
 - [Alert ID (ID field) is now aligned on the Azure portal and sensor console](how-to-manage-cloud-alerts.md#view-alerts-on-the-azure-portal)

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

@@ -16,6 +16,18 @@ Features released earlier than nine months ago are described in the [What's new
 > Noted features listed below are in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 >
 
+## March 2024
+
+|Service area  |Updates  |
+|---------|---------|
+| **OT networks** | [Sensor time drift detection](#sensor-time-drift-detection) |
+
+### Sensor time drift detection
+
+This version introduces a new troubleshooting test in the connectivity tool feature, specifically designed to identify time drift issues. 
+
+One common challenge when connecting sensors to Defender for IoT in the Azure portal arises from discrepancies in the sensor’s UTC time, which can lead to connectivity problems. To address this issue, we recommend that you configure a Network Time Protocol (NTP) server [in the sensor settings](configure-sensor-settings-portal.md#ntp).
+
 ## February 2024
 
 |Service area  |Updates  |