fixing links

batamig · batamig · commit 7d6429cd6cc4 · 2023-12-14T15:51:57.000+02:00
diff --git a/articles/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md b/articles/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md
@@ -62,7 +62,7 @@ To view alerts from connected OT sensors for a specific zone, use the **Site Man
 1. Locate the site and zone you want to view, using the filtering options at the top as needed:
 
     - **Connectivity**: Select to view only all OT sensors, or only connected / disconnected sensors only.
-    - **Upgrade Status**: Select to view all OT sensors, or only those with a specific [software update status](../update-ot-software.md#update-an-on-premises-management-console).
+    - **Upgrade Status**: Select to view all OT sensors, or only those with a [specific software update status](how-to-manage-sensors-from-the-on-premises-management-console.md#update-an-on-premises-management-console).
     - **Business Unit**: Select to view all OT sensors, or only those from a [specific business unit](../best-practices/plan-corporate-monitoring.md#plan-ot-sites-and-zones).
     - **Region**: Select to view all OT sensors, or only those from a [specific region](../best-practices/plan-corporate-monitoring.md#plan-ot-sites-and-zones).
 
diff --git a/articles/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console.md b/articles/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console.md
@@ -21,7 +21,7 @@ To perform the procedures in this article, make sure you have:
 
 - Access to the on-premises management console as an **Admin** user. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](../roles-on-premises.md).
 
-# Update sensors from an on-premises management console
+## Update sensors from an on-premises management console
 
 This procedure describes how to update several OT sensors simultaneously from a legacy on-premises management console.
 
@@ -44,13 +44,13 @@ The software version on your on-premises management console must be equal to tha
 
     The **Available versions** area lists all update packages available for your specific update scenario. You may have multiple options, but there will always be one specific version marked as **Recommended** for you. For example:
 
-    :::image type="content" source="media/update-ot-software/recommended-version.png" alt-text="Screenshot highlighting the recommended update version for the selected update scenario." lightbox="media/update-ot-software/recommended-version.png":::
+    :::image type="content" source="../media/update-ot-software/recommended-version.png" alt-text="Screenshot highlighting the recommended update version for the selected update scenario." lightbox="../media/update-ot-software/recommended-version.png":::
 
 1. Scroll down further in the **Local update** pane and select **Download** to download the software file.
 
     If you'd selected the **Are you updating through a local manager** option, files will be listed for both the on-premises management console and the sensor. For example:
 
-    :::image type="content" source="media/update-ot-software/download-update-package.png" alt-text="Screenshot of the Local update pane with two download files showing, for an on-premises management console and a sensor." lightbox="media/update-ot-software/download-update-package.png":::
+    :::image type="content" source="../media/update-ot-software/download-update-package.png" alt-text="Screenshot of the Local update pane with two download files showing, for an on-premises management console and a sensor." lightbox="../media/update-ot-software/download-update-package.png":::
 
     The update packages are downloaded with the following file syntax names:
 
@@ -59,7 +59,7 @@ The software version on your on-premises management console must be equal to tha
 
     Where `<version number>` is the software version number you're updating to.
 
-[!INCLUDE [root-of-trust](includes/root-of-trust.md)]
+[!INCLUDE [root-of-trust](../includes/root-of-trust.md)]
 
 ### Update an on-premises management console
 
@@ -81,7 +81,7 @@ The software version on your on-premises management console must be equal to tha
 
     Save your changes when you're finished selecting sensors to update. For example:
 
-   :::image type="content" source="media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png" alt-text="Screenshot of on-premises management console with Automatic Version Updates selected." lightbox="media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png":::
+   :::image type="content" source="../media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png" alt-text="Screenshot of on-premises management console with Automatic Version Updates selected." lightbox="../media/how-to-manage-sensors-from-the-on-premises-management-console/automatic-updates.png":::
 
     > [!IMPORTANT]
     > If your **Automatic Version Updates** option is red, you have an update conflict. An update conflict might occur if you have multiple sensors marked for automatic updates but the sensors currently have different software versions installed. Select the **Automatic Version Updates** option to resolve the conflict.
diff --git a/articles/defender-for-iot/organizations/legacy-central-management/how-to-set-up-high-availability.md b/articles/defender-for-iot/organizations/legacy-central-management/how-to-set-up-high-availability.md
@@ -6,7 +6,7 @@ ms.topic: how-to
 ---
 # About high availability (Legacy)
 
-[!INCLUDE [on-premises-management-deprecation](includes/on-premises-management-deprecation.md)]
+[!INCLUDE [on-premises-management-deprecation](../includes/on-premises-management-deprecation.md)]
 
 Increase the resiliency of your Defender for IoT deployment by configuring [high availability](legacy-air-gapped-deploy.md#high-availability-for-on-premises-management-consoles) on your on-premises management console. High availability deployments ensure your managed sensors continuously report to an active on-premises management console.
 
@@ -51,7 +51,7 @@ Before you perform the procedures in this article, verify that you've met the fo
 
     1.  The connection string is composed of the IP address and the token. The IP address is before the colon, and the token is after the colon. Copy the IP address and token separately. For example, if your connection string is ```172.10.246.232:a2c4gv9de23f56n078a44e12gf2ce77f```, copy the IP address ```172.10.246.232``` and the token ```a2c4gv9de23f56n078a44e12gf2ce77f``` separately.
 
-        :::image type="content" source="../media/how-to-set-up-high-availability/copy-connection-string-second-part.png" alt-text="Screenshot showing to copy each part of the connection string to use in the following command." lightbox="media/how-to-set-up-high-availability/copy-connection-string-second-part.png":::
+        :::image type="content" source="../media/how-to-set-up-high-availability/copy-connection-string-second-part.png" alt-text="Screenshot showing to copy each part of the connection string to use in the following command." lightbox="../media/how-to-set-up-high-availability/copy-connection-string-second-part.png":::
 
 1. **On the primary appliance**, use the following steps to connect the secondary appliance to the primary via CLI:
 
@@ -168,7 +168,7 @@ Perform the update in the following order. Make sure each step is complete befor
         sudo cyberx-management-trusted-hosts-apply
         ```
 
-1. Update both the primary and secondary appliances to the new version. For more information, see [Update an on-premises management console](../update-ot-software.md#update-an-on-premises-management-console).
+1. Update both the primary and secondary appliances to the new version. For more information, see [Update an on-premises management console](how-to-manage-sensors-from-the-on-premises-management-console.md#update-an-on-premises-management-console).
 
 1. Set up high availability again, on both the primary and secondary appliances. For more information, see [Create the primary and secondary pair](#create-the-primary-and-secondary-pair).
 
diff --git a/articles/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md b/articles/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md
@@ -86,7 +86,7 @@ To view alerts from connected OT sensors for a specific zone, use the **Site Man
 1. Locate the site and zone you want to view, using the filtering options at the top as needed:
 
     - **Connectivity**: Select to view only all OT sensors, or only connected / disconnected sensors only.
-    - **Upgrade Status**: Select to view all OT sensors, or only those with a specific [software update status](../update-ot-software.md#update-an-on-premises-management-console).
+    - **Upgrade Status**: Select to view all OT sensors, or only those with a specific [software update status](how-to-manage-sensors-from-the-on-premises-management-console.md#update-an-on-premises-management-console).
     - **Business Unit**: Select to view all OT sensors, or only those from a [specific business unit](../best-practices/plan-corporate-monitoring.md#plan-ot-sites-and-zones).
     - **Region**: Select to view all OT sensors, or only those from a [specific region](../best-practices/plan-corporate-monitoring.md#plan-ot-sites-and-zones).
 
