links

tarTech23 · tarTech23 · commit 1bc6198d81ef · 2025-04-08T12:35:54.000+03:00
diff --git a/articles/defender-for-iot/organizations/TOC.yml b/articles/defender-for-iot/organizations/TOC.yml
@@ -419,8 +419,8 @@
   - name: Videos
     href: https://azure.microsoft.com/resources/videos/index/?services=security-center&service=internet-of-things&page=1&sort=newest
   - name: Release notes archive
-    href: release-notes-archive.md
+    href: whats-new-archive.md
   - name: OT monitoring software versions archive
-    href: release-notes-ot-monitoring-software-archive.md
+    href: release-notes-ot-monitoring-sensor-archive.md
   - name: Custom columns sample script
     href: custom-columns-sample-script.md
diff --git a/articles/defender-for-iot/organizations/appliance-catalog/neousys-nuvo-5006lp.md b/articles/defender-for-iot/organizations/appliance-catalog/neousys-nuvo-5006lp.md
@@ -10,14 +10,14 @@ ms.topic: reference
 This article describes the Neousys Nuvo-5006LP appliance for OT sensors.
 
 > [!NOTE]
-> Neousys Nuvo-5006LP is a legacy appliance, and is supported for Defender for IoT software up to the latest patch for versions [22.2.x](../ot-sensor-archive.md#versions-222x). We recommend that you replace these appliances with newer certified models, such as the [YS-FIT2](ys-techsystems-ys-fit2.md) or [HPE DL20 (NHP 2LFF)](hpe-proliant-dl20-plus-smb.md).
+> Neousys Nuvo-5006LP is a legacy appliance, and is supported for Defender for IoT software up to the latest patch for versions [22.2.x](../release-notes-ot-monitoring-sensor-archive.md#versions-222x). We recommend that you replace these appliances with newer certified models, such as the [YS-FIT2](ys-techsystems-ys-fit2.md) or [HPE DL20 (NHP 2LFF)](hpe-proliant-dl20-plus-smb.md).
 
 | Appliance characteristic |Details |
 |---------|---------|
 |**Hardware profile** | L100 |
 |**Performance** | Max bandwidth: 30 Mbps<br>Max devices: 400 |
 |**Physical specifications** | Mounting: Mounting kit, Din Rail<br>Ports: 5x RJ45|
-|**Status** | Supported up to the latest Defender for IoT software patch for versions [22.2.x](../ot-sensor-archive.md#versions-222x)|
+|**Status** | Supported up to the latest Defender for IoT software patch for versions [22.2.x](../release-notes-ot-monitoring-sensor-archive.md#versions-222x)|
 
 :::image type="content" source="../media/ot-system-requirements/cyberx.png" alt-text="Photo of a Neousys Nuvo-5006LP." border="false":::
 
diff --git a/articles/defender-for-iot/organizations/device-inventory.md b/articles/defender-for-iot/organizations/device-inventory.md
@@ -44,7 +44,7 @@ Defender for IoT device inventory is available in the following locations:
 
 |Location  |Description   | Extra inventory support |
 |---------|---------|---------|
-|**Azure portal**     | OT devices detected from all cloud-connected OT sensors.      |     - If you also use [Microsoft Sentinel](iot-solution.md), incidents in Microsoft Sentinel are linked to related devices in Defender for IoT. <br><br>- Use Defender for IoT [workbooks](workbooks.md) for visibility into all cloud-connected device inventory, including related alerts and vulnerabilities.    <br><br>- If you have a [legacy Enterprise IoT plan](release-notes-archive.md#enterprise-iot-protection-now-included-in-microsoft-365-e5-and-e5-security-licenses) on your Azure subscription, the Azure portal also includes devices detected by Microsoft Defender for Endpoint agents. If you have an [Enterprise IoT sensor](eiot-sensor.md), the Azure portal also includes devices detected by the Enterprise IoT sensor.   |
+|**Azure portal**     | OT devices detected from all cloud-connected OT sensors.      |     - If you also use [Microsoft Sentinel](iot-solution.md), incidents in Microsoft Sentinel are linked to related devices in Defender for IoT. <br><br>- Use Defender for IoT [workbooks](workbooks.md) for visibility into all cloud-connected device inventory, including related alerts and vulnerabilities.    <br><br>- If you have a [legacy Enterprise IoT plan](whats-new-archive.md#enterprise-iot-protection-now-included-in-microsoft-365-e5-and-e5-security-licenses) on your Azure subscription, the Azure portal also includes devices detected by Microsoft Defender for Endpoint agents. If you have an [Enterprise IoT sensor](eiot-sensor.md), the Azure portal also includes devices detected by the Enterprise IoT sensor.   |
 | **Microsoft Defender XDR** | Enterprise IoT devices detected by Microsoft Defender for Endpoint agents | Correlate devices across Microsoft Defender XDR in purpose-built alerts, vulnerabilities, and recommendations. |
 |**OT network sensor consoles**     |   Devices detected by that OT sensor      |    - View all detected devices across a network device map<br><br>- View related events on the **Event timeline** |
 
diff --git a/articles/defender-for-iot/organizations/how-to-manage-subscriptions.md b/articles/defender-for-iot/organizations/how-to-manage-subscriptions.md
@@ -148,7 +148,7 @@ After migrating your plan to a site-based Microsoft 365 plan, edits are supporte
 
 ## Legacy procedures for plan management in the Azure portal
 
-Starting June 1, 2023, Microsoft Defender for IoT licenses for OT monitoring are available for purchase only in the [Microsoft 365 admin center](https://admin.microsoft.com/Adminportal/Home), and OT sensors are onboarded to Defender for IoT based on your licensed site sizes. For more information, see [OT plans billed by site-based licenses](release-notes-archive.md#ot-plans-billed-by-site-based-licenses).
+Starting June 1, 2023, Microsoft Defender for IoT licenses for OT monitoring are available for purchase only in the [Microsoft 365 admin center](https://admin.microsoft.com/Adminportal/Home), and OT sensors are onboarded to Defender for IoT based on your licensed site sizes. For more information, see [OT plans billed by site-based licenses](whats-new-archive.md#ot-plans-billed-by-site-based-licenses).
 
 Existing customers can continue to use any legacy OT plan, with no changes in functionality. For legacy customers, *committed devices* are the number of devices you're monitoring. For more information, see [Devices monitored by Defender for IoT](architecture.md#devices-monitored-by-defender-for-iot).
 
diff --git a/articles/defender-for-iot/organizations/release-notes-ot-monitoring-sensor-archive.md b/articles/defender-for-iot/organizations/release-notes-ot-monitoring-sensor-archive.md
@@ -91,7 +91,7 @@ To understand whether a feature is supported in your sensor version, check the r
 
 This version includes the following updates and enhancements:
 
-- [Sensor software runs on a Debian 11 operating system](ot-deploy/install-software-ot-sensor.md) and [updates to this version may be heavier and longer than usual](release-notes-archive.md#ot-network-sensors-now-run-on-debian-11)
+- [Sensor software runs on a Debian 11 operating system](ot-deploy/install-software-ot-sensor.md) and [updates to this version may be heavier and longer than usual](whats-new-archive.md#ot-network-sensors-now-run-on-debian-11)
 - [The legacy, privileged default *support* user is replaced by the default *admin* user](roles-on-premises.md#legacy-users)
 
 > [!IMPORTANT]
@@ -146,7 +146,7 @@ This version includes bug fixes for stability improvements.
 
 This version includes:
 
-- [Improved monitoring and support for OT sensor logs](release-notes-archive.md#improved-monitoring-and-support-for-ot-sensor-logs)
+- [Improved monitoring and support for OT sensor logs](whats-new-archive.md#improved-monitoring-and-support-for-ot-sensor-logs)
 - Bug fixes for stability improvements.
 
 ### 22.3.8
@@ -276,7 +276,7 @@ This version includes the following new updates and fixes:
 This version includes the following new updates and fixes:
 
 - [Define and view OT sensor settings from the Azure portal](configure-sensor-settings-portal.md)
-- [Update your sensors from the Azure portal](update-ot-software.md#update-ot-sensors)
+- [Update your sensors from the Azure portal](update-ot-software.md#update-ot-sensors-with-the-latest-ot-monitoring-software)
 - [New naming convention for hardware profiles](ot-appliance-sizing.md)
 - [PCAP access from the Azure portal](how-to-manage-cloud-alerts.md)
 - [Bi-directional alert synch between OT sensors and the Azure portal](alerts.md#managing-ot-alerts-in-a-hybrid-environment)
diff --git a/articles/defender-for-iot/organizations/release-notes-sentinel.md b/articles/defender-for-iot/organizations/release-notes-sentinel.md
@@ -46,7 +46,7 @@ New features in this version include:
 
 - New SOC playbooks for automation with CVEs, triaging incidents that involve sensitive devices, and email notifications to device owners for new incidents.
 
-For more information, see [Updates to the Microsoft Defender for IoT solution](release-notes-archive.md#updates-to-the-microsoft-defender-for-iot-solution-in-microsoft-sentinels-content-hub).
+For more information, see [Updates to the Microsoft Defender for IoT solution](whats-new-archive.md#updates-to-the-microsoft-defender-for-iot-solution-in-microsoft-sentinels-content-hub).
 
 ## Version 2.0.0
 
@@ -62,7 +62,7 @@ For more information, see [Centrally discover and deploy Microsoft Sentinel out-
 
 New features in this version include:
 
-- [Microsoft Sentinel incident synch with Defender for IoT alerts](release-notes-archive.md#microsoft-sentinel-incident-synch-with-defender-for-iot-alerts)
+- [Microsoft Sentinel incident synch with Defender for IoT alerts](whats-new-archive.md#microsoft-sentinel-incident-synch-with-defender-for-iot-alerts)
 - IoT device entities displayed in related Microsoft Sentinel incidents.
 
 ## Version 1.0.13
diff --git a/articles/defender-for-iot/organizations/release-notes.md b/articles/defender-for-iot/organizations/release-notes.md
@@ -159,7 +159,7 @@ This version includes the following updates and enhancements:
 
 This version includes the following updates and enhancements:
 
-- [Malicious URL path alert](release-notes-ot-monitoring-sensor-archive.md#malicious-url-path-alert)
+- [Malicious URL path alert](whats-new-archive.md#malicious-url-path-alert)
 - The following CVE is resolved in this version:
   - CVE-2024-38089
 
@@ -171,7 +171,7 @@ This version includes the following updates and enhancements:
 
 This version includes the following updates and enhancements:
 
-- [Sensor time drift detection](release-notes-ot-monitoring-sensor-archive.md#sensor-time-drift-detection)
+- [Sensor time drift detection](whats-new-archive.md#sensor-time-drift-detection)
 - Bug fixes for stability improvements
 - The following CVEs are resolved in this version:
   - CVE-2024-29055
@@ -206,7 +206,7 @@ This version includes the following updates and enhancements:
 
 This version includes the following updates and enhancements:
 
-- [Sensor software runs on a Debian 11 operating system](ot-deploy/install-software-ot-sensor.md) and [updates to this version may be heavier and longer than usual](whats-new.md#ot-network-sensors-now-run-on-debian-11)
+- [Sensor software runs on a Debian 11 operating system](ot-deploy/install-software-ot-sensor.md) and [updates to this version may be heavier and longer than usual](whats-new-archive.md#ot-network-sensors-now-run-on-debian-11)
 - [The legacy, privileged default *support* user is replaced by the default *admin* user](roles-on-premises.md#legacy-users)
 
 > [!IMPORTANT]
@@ -261,7 +261,7 @@ This version includes bug fixes for stability improvements.
 
 This version includes:
 
-- [Improved monitoring and support for OT sensor logs](whats-new.md#improved-monitoring-and-support-for-ot-sensor-logs)
+- [Improved monitoring and support for OT sensor logs](whats-new-archive.md#improved-monitoring-and-support-for-ot-sensor-logs)
 - Bug fixes for stability improvements.
 
 ### 22.3.8
@@ -552,4 +552,4 @@ This version includes the following new updates and fixes:
 
 ## Next steps
 
-For more information about the features listed in this article, see [What's new in Microsoft Defender for IoT](whats-new.md) and [What's new archive for in Microsoft Defender for IoT for organizations](release-notes-ot-monitoring-sensor-archive.md.md).
+For more information about the features listed in this article, see [What's new in Microsoft Defender for IoT](whats-new.md) and [What's new archive for in Microsoft Defender for IoT for organizations](whats-new-archive.md.md).
diff --git a/articles/defender-for-iot/organizations/roles-on-premises.md b/articles/defender-for-iot/organizations/roles-on-premises.md
@@ -32,8 +32,8 @@ For more information, see:
 
 |Legacy scenario  |Description  |
 |---------|---------|
-|**Sensor versions earlier than 23.2.0**     |   In sensor versions earlier than [23.2.0](release-notes-archive.md#default-privileged-user-is-now-admin-instead-of-support), the default *admin* user is named *support*. The *support* user is available and supported only on versions earlier than 23.2.0.<br><br>Documentation refers to the *admin* user to match the latest version of the software.      |
-|**Sensor software versions earlier than 23.1.x**     |   In sensor software versions earlier than [23.1.x](release-notes-archive.md#july-2023), the *cyberx* and *cyberx_host* privileged users are also in use. <br><br>In newly installed versions 23.1.x and higher, the *cyberx* and *cyberx_host* users are available, but not enabled by default. <br><br>To enable these extra privileged users, such as to use the [Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md), change their passwords. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).      |
+|**Sensor versions earlier than 23.2.0**     |   In sensor versions earlier than [23.2.0](whats-new-archive.md#default-privileged-user-is-now-admin-instead-of-support), the default *admin* user is named *support*. The *support* user is available and supported only on versions earlier than 23.2.0.<br><br>Documentation refers to the *admin* user to match the latest version of the software.      |
+|**Sensor software versions earlier than 23.1.x**     |   In sensor software versions earlier than [23.1.x]whats-new-archive.md#july-2023), the *cyberx* and *cyberx_host* privileged users are also in use. <br><br>In newly installed versions 23.1.x and higher, the *cyberx* and *cyberx_host* users are available, but not enabled by default. <br><br>To enable these extra privileged users, such as to use the [Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md), change their passwords. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).      |
 |**On-premises management consoles**     | The [on-premises management console](legacy-central-management/install-software-on-premises-management-console.md) is installed with privileged *support* and *cyberx* users. <br><br> When first setting up an on-premises management console, first sign in with the *support* user, create an initial user with an **Admin** role, and then use that admin user to create other users with other roles.        |
 
 ### Access per privileged user
diff --git a/articles/defender-for-iot/organizations/whats-new-archive.md b/articles/defender-for-iot/organizations/whats-new-archive.md
@@ -538,7 +538,7 @@ For more information, see [Manage SSL/TLS certificates](how-to-manage-individual
 
 Activation files on locally managed OT sensors now remain activated for as long as your Defender for IoT plan is active on your Azure subscription, just like activation files on cloud-connected OT sensors.
 
-You only need to update your activation file if you're [updating an OT sensor from a recent version](update-ot-software.md?tabs=portal#update-ot-sensors) or switching the sensor management mode, such as moving from locally managed to cloud-connected.
+You only need to update your activation file if you're [updating an OT sensor from a recent version](update-ot-software.md?tabs=portal#update-ot-sensors-with-the-latest-ot-monitoring-software) or switching the sensor management mode, such as moving from locally managed to cloud-connected.
 
 For more information, see [Manage individual sensors](how-to-manage-individual-sensors.md).
 
@@ -678,11 +678,11 @@ For more information, see:
 
 ### Update sensor software from the Azure portal (Public preview)
 
-For cloud-connected sensor versions [22.2.3](ot-sensor-archive.md#2223) and higher, now you can update your sensor software directly from the new **Sites and sensors** page on the Azure portal.
+For cloud-connected sensor versions [22.2.3](release-notes-ot-monitoring-sensor-archive.md#2223) and higher, now you can update your sensor software directly from the new **Sites and sensors** page on the Azure portal.
 
 :::image type="content" source="media/update-ot-software/send-package.png" alt-text="Screenshot of the Send package option." lightbox="media/update-ot-software/send-package.png":::
 
-For more information, see [Update your sensors from the Azure portal](update-ot-software.md#update-ot-sensors).
+For more information, see [Update your sensors from the Azure portal](update-ot-software.md#update-ot-sensors-with-the-latest-ot-monitoring-software).
 
 ### Azure connectivity status shown on OT sensors
 
diff --git a/articles/defender-for-iot/organizations/whats-new.md b/articles/defender-for-iot/organizations/whats-new.md
@@ -42,7 +42,7 @@ The “Excessive Number of Sessions” alert now includes support by default to
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | [Aggregating multiple alerts violations with the same parameters](#aggregating-multiple-alerts-violations-with-the-same-parameters) |
+| **OT networks** | - [Aggregating multiple alerts violations with the same parameters](#aggregating-multiple-alerts-violations-with-the-same-parameters)|
 
 ### Aggregating multiple alerts violations with the same parameters
 
@@ -74,7 +74,7 @@ We now support the OCPI protocol. See [the updated protocol list](concept-suppor
 
 ### New sensor setting type Public addresses
 
-We're adding the **Public addresses** type to the sensor settings that allows you to register the public addresses of internal devices and ensure that the sensor doesn't treat them as internet communication. For more information, see [add sensor settings](configure-sensor-settings-portal.md#add-sensor-settings).
+We're adding the **Public addresses** type to the sensor settings, that allows you to exclude public IP addresses that might have been used for internal use and shouldn't be tracked. For more information, see [add sensor settings](configure-sensor-settings-portal.md#add-sensor-settings).
 
 ### Improved OT sensor onboarding
 
