Merge pull request #271437 from tarTech23/senon

sensor connection problems

Author: prmerger-automator[bot]

articles/defender-for-iot/organizations/ot-deploy/activate-deploy-sensor.md

@@ -131,6 +131,12 @@ If you've configured the initial settings [via the CLI](#configure-setup-via-the
 1. Select the terms and conditions option and then select **Activate**.
 1. Select **Next: Certificates**.
 
+If you have a connection problem between the cloud-based sensor and the Azure portal during the activation process that causes the activation to fail, a message appears below the Activate button. To solve the connectivity problem select **Learn more** and the **Cloud connectivity** pane opens. The pane lists the causes for the problem and recommendations to solve it.
+
+Even without solving the problem you're able to continue to the next stage, by selecting **Next: Certificates**.
+
+The only connection problem that must be fixed before moving to the next stage, is when a time drift is detected and the sensor isn't synchronized to the cloud. In this case the sensor must be correctly synchronized, as described in the recommendations, before moving to the next stage.
+
 ### Define SSL/TLS certificate settings
 
 Use the **Certificates** tab to deploy an SSL/TLS certificate on your OT sensor. We recommend that you use a [CA-signed certificate](create-ssl-certificates.md) for all production environments.

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

@@ -17,6 +17,18 @@ 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)]
 
+## October 2024
+
+|Service area  |Updates  |
+|---------|---------|
+| **OT networks** | [Improved OT sensor onboarding](#improved-ot-sensor-onboarding) |
+
+### Improved OT sensor onboarding
+
+If there are connection problems, during sensor onboarding, between the OT sensor and the Azure portal at the configuration stage, the process can't be completed until the connection problem is solved.
+
+We now support completing the configuration process without the need to solve the communication problem, allowing you to continue the onboarding of your OT sensor quickly and solve the problem at a later time. For more information, see [activate your OT sensor](ot-deploy/activate-deploy-sensor.md#activate-your-ot-sensor).
+
 ## July 2024
 
 |Service area  |Updates  |