Merge pull request #190259 from batamig/patch-160

updates for 4.1.2

Author: PRMerger7

articles/defender-for-iot/device-builders/release-notes.md

@@ -19,15 +19,15 @@ Listed below are the support, breaking change policies for Defender for IoT, and
 
 ## February 2022
 
-**Version 4.1.1**:
+**Version 4.1.2**:
 
 - **Micro agent for Edge is now in Public Preview**: The micro-agent supports IoT Edge devices, with an easy installation and identity provisioning process that uses an automatically provisioned module identity to authenticate Edge devices without the need to perform any manual authentication.
 
     For more information, see [Install Defender for IoT micro agent for Edge (Preview)](how-to-install-micro-agent-for-edge.md).
 
 - **New directory structure**: Now aligned with the standard Linux installation directory structure.
 
-    Due to this change, updates to version 4.1.1 require you to reauthenticate the micro agent and save your connection string in the new location. For more information, see [Upgrade the Microsoft Defender for IoT micro agent](upgrade-micro-agent.md).
+    Due to this change, updates to version 4.1.2 require you to reauthenticate the micro agent and save your connection string in the new location. For more information, see [Upgrade the Microsoft Defender for IoT micro agent](upgrade-micro-agent.md).
 
 - **SBoM collector**: The SBoM collector now collects the packages installed on the device periodically. For more information, see [Micro agent event collection (Preview)](concept-event-aggregation.md).
 

articles/defender-for-iot/device-builders/upgrade-micro-agent.md

@@ -41,9 +41,9 @@ For more information, see our [release notes for device builders](release-notes.
 
 ## Upgrade a standalone micro agent from a legacy version
 
-This section is relevant specifically when upgrading a micro agent from version 3.13.1 or lower to version 4.1.1 or higher.
+This section is relevant specifically when upgrading a micro agent from version 3.13.1 or lower to version 4.1.2 or higher.
 
-In version 4.1.1, the standalone micro agent directory changed to align with standard Linux installation directory structures. This change requires customers to reauthenticate the micro agent and modify the connection string location.
+In version 4.1.2, the standalone micro agent directory changed to align with standard Linux installation directory structures. This change requires customers to reauthenticate the micro agent and modify the connection string location.
 
 1. Upgrade your micro agent as described [above](#upgrade-a-standalone-micro-agent).