links

Author: tarTech23

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](whats-new.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](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.   |
 | **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** |
 |**An on-premises management console**     |  Devices detected across all connected OT sensors          | Enhance device data by importing data manually or via script  |

articles/defender-for-iot/organizations/how-to-manage-subscriptions.md

@@ -153,7 +153,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](whats-new.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](release-notes-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).
 

articles/defender-for-iot/organizations/includes/on-premises-management-deprecation.md

@@ -6,7 +6,7 @@ ms.topic: include
 ---
 
 > [!IMPORTANT]
-> Defender for IoT now recommends using Microsoft cloud services or existing IT infrastructure for central monitoring and sensor management, and [plans to retire the on-premises management console](../whats-new.md#new-architecture-for-hybrid-and-air-gapped-support) on **January 1st, 2025**.
+> Defender for IoT now recommends using Microsoft cloud services or existing IT infrastructure for central monitoring and sensor management, and [plans to retire the on-premises management console](../release-notes-archive.md#new-architecture-for-hybrid-and-air-gapped-support) on **January 1st, 2025**.
 >
 > For more information, see [Deploy hybrid or air-gapped OT sensor management](../ot-deploy/air-gapped-deploy.md).
 >

articles/defender-for-iot/organizations/ot-sensor-archive.md

@@ -1,6 +1,6 @@
 ---
 title: OT monitoring software versions archive for Microsoft Defender for IoT for organizations
-description: Learn about the features and enhancements released for Microsoft Defender for IoT for organizations more than six months ago.
+description: Learn about OT monitoring software versions released for Microsoft Defender for IoT for organizations more than six months ago.
 ms.topic: concept-article
 ms.date: 01/26/2025
 ---
@@ -11,7 +11,7 @@ ms.date: 01/26/2025
 
 This article serves as an archive for OT monitoring software versions released for Microsoft Defender for IoT for organizations more than six months ago.
 
-For more recent updates, see [OT monitoring software versions in Microsoft Defender for IoT?](release-notes.md.md).
+For more recent updates, see [OT monitoring software versions in Microsoft Defender for IoT?](release-notes.md).
 <!-- do we need this? -->
 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.
 
@@ -69,7 +69,7 @@ For more information, see [Threat intelligence research and packages](how-to-wor
 
 Defender for IoT provides **1 year of support** for every new version, starting with versions **22.1.7** and **22.2.7**. For example, version **22.2.7** was released in **October 2022** and is supported through **September 2023**.
 
-Earlier versions use a legacy support model, with support dates [detailed for each version](#ot-monitoring-software-versions).
+Earlier versions use a legacy support model, with support dates detailed for each version.
 
 ### On-premises appliance security
 
@@ -101,7 +101,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](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](release-notes-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]
@@ -156,7 +156,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](release-notes-archive.md#improved-monitoring-and-support-for-ot-sensor-logs)
 - Bug fixes for stability improvements.
 
 ### 22.3.8
@@ -444,5 +444,4 @@ This version includes the following new updates and fixes:
 - [PLC operating mode detections](how-to-create-risk-assessment-reports.md)
 - [New PCAP API](api/management-alert-apis.md#pcap-request-alert-pcap)
 - [Export logs from the on-premises management console for troubleshooting](legacy-central-management/how-to-troubleshoot-on-premises-management-console.md#export-logs-from-the-on-premises-management-console-for-troubleshooting)
-- [Support for Webhook extended to send data to endpoints](how-to-forward-alert-information-to-partners.md#webhook-extended)
 - [Unicode support for certificate passphrases](best-practices/plan-prepare-deploy.md#prepare-ca-signed-certificates)

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md

@@ -24,7 +24,7 @@ If you're using a legacy software version, you may have one or more of the follo
 
 |Legacy scenario  |Description  |
 |---------|---------|
-|**Sensor versions earlier than 23.2.0**     |   In sensor versions earlier than [23.2.0](whats-new.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 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.    |
 
 Other CLI users cannot be added.
 

articles/defender-for-iot/organizations/release-notes-archive.md

@@ -35,7 +35,7 @@ We now support the Open protocol. [See the updated protocol list](concept-suppor
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | - [Single sign-on for the sensor console](#single-sign-on-for-the-sensor-console)<br>- [Sensor time drift detection](#sensor-time-drift-detection)<br>- [Security update](#security-update-1) |
+| **OT networks** | - [Single sign-on for the sensor console](#single-sign-on-for-the-sensor-console)<br>- [Sensor time drift detection](#sensor-time-drift-detection)<br>- [Security update](#security-update) |
 
 ### Single sign-on for the sensor console
 
@@ -678,7 +678,7 @@ For more information, see:
 
 ### Update sensor software from the Azure portal (Public preview)
 
-For cloud-connected sensor versions [22.2.3](release-notes.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](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.
 
 :::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":::
 

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](whats-new.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](release-notes-archive.md#updates-to-the-microsoft-defender-for-iot-solution-in-microsoft-sentinels-content-hub).
 
 ## Version 2.0.0
 
@@ -62,10 +62,9 @@ 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](whats-new.md#microsoft-sentinel-incident-synch-with-defender-for-iot-alerts)
+- [Microsoft Sentinel incident synch with Defender for IoT alerts](release-notes-archive.md#microsoft-sentinel-incident-synch-with-defender-for-iot-alerts)
 - IoT device entities displayed in related Microsoft Sentinel incidents.
 
-
 ## Version 1.0.13
 
 **Released**: March 2022

articles/defender-for-iot/organizations/release-notes.md

@@ -127,7 +127,7 @@ This version includes the following updates and enhancements:
 
 This version includes the following updates and enhancements:
 
-- [Malicious URL path alert](whats-new.md#malicious-url-path-alert)
+- [Malicious URL path alert](release-notes-archive.md#malicious-url-path-alert)
 - The following CVE is resolved in this version:
   - CVE-2024-38089
 
@@ -139,7 +139,7 @@ This version includes the following updates and enhancements:
 
 This version includes the following updates and enhancements:
 
-- [Sensor time drift detection](whats-new.md#sensor-time-drift-detection)
+- [Sensor time drift detection](release-notes-archive.md#sensor-time-drift-detection)
 - Bug fixes for stability improvements
 - The following CVEs are resolved in this version:
   - CVE-2024-29055

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](whats-new.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.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](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).      |
 |**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

articles/defender-for-iot/organizations/update-ot-software.md

@@ -25,7 +25,7 @@ To perform the procedures described in this article, make sure that you have:
     |Update scenario  |Method details  |
     |---------|---------|
     |**On-premises management console**     |  If the OT sensors you want to update are connected to an on-premises management console, plan to [update your on-premises management console](#update-the-on-premises-management-console) *before* updating your sensors.|
-    |**Cloud-connected sensors**     |  Cloud connected sensors can be updated remotely, directly from the Azure portal, or manually using a downloaded update package.  <br><br>[Remote updates](#update-ot-sensors) require that your OT sensor has version [22.2.3](release-notes.md#2223) or later already installed.       |
+    |**Cloud-connected sensors**     |  Cloud connected sensors can be updated remotely, directly from the Azure portal, or manually using a downloaded update package.  <br><br>[Remote updates](#update-ot-sensors) require that your OT sensor has version [22.2.3](ot-sensor-archive.md#2223) or later already installed.       |
     |**Locally managed sensors**     |  Locally managed sensors can be updated using a downloaded update package, either via a connected on-premises management console, or directly on an OT sensor console. |
 
 - **Required access permissions**: