fixing links and d4iot home page post deployment

batamig · batamig · commit 94716bfd63e1 · 2023-04-18T16:48:17.000+03:00
diff --git a/articles/defender-for-iot/index.yml b/articles/defender-for-iot/index.yml
@@ -43,28 +43,28 @@ conceptualContent:
       links:
         - url: organizations/architecture.md
           itemType: concept
-          text: OT monitoring system architecture
-        - url: organizations/how-to-manage-subscriptions.md
-          itemType: how-to-guide
-          text: Manage Defender for IoT plans for OT network monitoring
-        - url: organizations/best-practices/traffic-mirroring-methods.md
+          text: Microsoft Defender for IoT components
+        - url: organizations/billing.md
           itemType: concept
-          text: Configure traffic mirroring
-        - url: organizations/ot-appliance-sizing.md
+          text: Subscription billing
+        - url: organizations/manage-users-overview.md
           itemType: concept
-          text: Which appliances do I need?
-        - url: organizations/onboard-sensors.md
-          itemType: how-to-guide
-          text: Onboard OT network sensors
-        - url: organizations/how-to-install-software.md
-          itemType: how-to-guide
-          text: Install monitoring software
-        - url: organizations/how-to-activate-and-set-up-your-sensor.md
-          itemType: how-to-guide
-          text: Activate and set up your OT network sensor
-        - url: organizations/roles-on-premises.md
+          text: User roles and permissions
+        - url: organizations/device-inventory.md
+          itemType: concept
+          text: Device inventories
+        - url: organizations/alerts.md
+          itemType: concept
+          text: Alerts
+        - url: organizations/concept-zero-trust.md
+          itemType: concept
+          text: Zero Trust and your OT networks
+        - url: organizations/concept-sentinel-integration.md
           itemType: concept
-          text: On-premises users and roles for OT monitoring
+          text: OT threat monitoring in your SOC
+        - url: organizations/ot-deploy/ot-deploy-path.md
+          itemType: deploy
+          text: Deploy Defender for IoT for OT monitoring
       footerLink:
         url: organizations/index.yml
         text: See more
diff --git a/articles/defender-for-iot/organizations/cli-ot-sensor.md b/articles/defender-for-iot/organizations/cli-ot-sensor.md
@@ -296,7 +296,7 @@ To use this command:
 - Verify that the certificate file you want to import is readable on the appliance. Upload certificate files to the appliance using tools such as WinSCP or Wget.
 - Confirm with your IT office that the appliance domain as it appears in the certificate is correct for your DNS server and the corresponding IP address.
 
-For more information, see [Certificates for appliance encryption and authentication (OT appliances)](how-to-deploy-certificates.md).
+For more information, see [Prepare CA-signed certificates](best-practices/plan-prepare-deploy.md#prepare-ca-signed-certificates) and [Create SSL/TLS certificates for OT appliances](ot-deploy/create-ssl-certificates.md).
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
diff --git a/articles/defender-for-iot/organizations/faqs-ot.md b/articles/defender-for-iot/organizations/faqs-ot.md
@@ -56,7 +56,7 @@ Change network configuration settings before or after you activate your sensor u
 - **From the sensor UI**: [Update the OT sensor network configuration](how-to-manage-individual-sensors.md#update-the-ot-sensor-network-configuration)
 - **From the sensor CLI**: [Network configuration](cli-ot-sensor.md#network-configuration)
 
-For more information, see [Activate and set up your sensor](how-to-activate-and-set-up-your-sensor.md), [Getting started with advanced CLI commands](references-work-with-defender-for-iot-cli-commands.md), and [CLI command reference from OT network sensors](cli-ot-sensor.md).
+For more information, see [Activate and set up your OT network sensor](ot-deploy/activate-deploy-sensor.md), [Getting started with advanced CLI commands](references-work-with-defender-for-iot-cli-commands.md), and [CLI command reference from OT network sensors](cli-ot-sensor.md).
 
 ## How do I check the sanity of my deployment
 
diff --git a/articles/defender-for-iot/organizations/how-to-forward-alert-information-to-partners.md b/articles/defender-for-iot/organizations/how-to-forward-alert-information-to-partners.md
@@ -302,7 +302,7 @@ If your forwarding alert rules aren't working as expected, check the following d
 
 - **Certificate validation**. Forwarding rules for [Syslog CEF](#syslog-server-actions), [Microsoft Sentinel](integrate-overview.md#microsoft-sentinel), and [QRadar](tutorial-qradar.md) support encryption and certificate validation.
 
-    If your OT sensors or on-premises management console are configured to [validate certificates](how-to-deploy-certificates.md#verify-crl-server-access) and the certificate can't be verified, the alerts aren't forwarded.
+    If your OT sensors or on-premises management console are configured to [validate certificates](ot-deploy/create-ssl-certificates.md#verify-crl-server-access) and the certificate can't be verified, the alerts aren't forwarded.
 
     In these cases, the sensor or on-premises management console is the session's client and initiator. Certificates are typically received from the server or use asymmetric encryption, where a specific certificate is provided to set up the integration.
 
diff --git a/articles/defender-for-iot/organizations/how-to-set-up-high-availability.md b/articles/defender-for-iot/organizations/how-to-set-up-high-availability.md
@@ -24,7 +24,7 @@ Before you perform the procedures in this article, verify that you've met the fo
 
 - Make sure that the primary on-premises management console is fully [configured](how-to-manage-the-on-premises-management-console.md), including at least two [OT network sensors connected](ot-deploy/connect-sensors-to-management.md) and visible in the console UI, as well as the scheduled backups or VLAN settings. All settings are applied to the secondary appliance automatically after pairing.
 
-- Make sure that your SSL/TLS certificates meet required criteria. For more information, see [Deploy OT appliance certificates](how-to-deploy-certificates.md).
+- Make sure that your SSL/TLS certificates meet required criteria. For more information, see [SSL/TLS certificate requirements for on-premises resources](best-practices/certificate-requirements.md).
 
 - Make sure that your organizational security policy grants you access to the following services, on the primary and secondary on-premises management console. These services also allow the connection between the sensors and secondary on-premises management console:
 
diff --git a/articles/defender-for-iot/organizations/how-to-work-with-the-sensor-device-map.md b/articles/defender-for-iot/organizations/how-to-work-with-the-sensor-device-map.md
@@ -15,7 +15,7 @@ Use a device map to retrieve, analyze, and manage device information, either all
 
 To perform the procedures in this article, make sure that you have:
 
-- An OT network sensor [installed](ot-deploy/install-software-ot-sensor.md), [activated, and configured](how-to-activate-and-set-up-your-sensor.md), with network traffic ingested
+- An OT network sensor [installed](ot-deploy/install-software-ot-sensor.md), [activated, and configured](ot-deploy/activate-deploy-sensor.md), with network traffic ingested 
 
 - Access to your OT sensor or on-premises management console. Users with the **Viewer** role can view data on the map. To import or export data or edit the map view, you need access as a **Security Analyst** or **Admin** user. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
 
diff --git a/articles/defender-for-iot/organizations/release-notes-archive.md b/articles/defender-for-iot/organizations/release-notes-archive.md
@@ -178,7 +178,7 @@ Webhook extended can be used to send extra data to the endpoint. The extended fe
 
 ### Unicode support for certificate passphrases
 
-Unicode characters are now supported when working with sensor certificate passphrases. For more information, see [About certificates](how-to-deploy-certificates.md).
+Unicode characters are now supported when working with sensor certificate passphrases. For more information, see [Prepare CA-signed certificates](best-practices/plan-prepare-deploy.md#prepare-ca-signed-certificates).
 
 ## April 2021
 
diff --git a/articles/defender-for-iot/organizations/release-notes.md b/articles/defender-for-iot/organizations/release-notes.md
@@ -111,7 +111,7 @@ Version 22.3.7 includes the same features as 22.3.6. If you have version 22.3.6
 - [Merging](how-to-investigate-sensor-detections-in-a-device-inventory.md#merge-devices) and [deleting](how-to-investigate-sensor-detections-in-a-device-inventory.md#delete-devices) devices on OT sensors now include confirmation messages when the action has completed
 - Support for [deleting multiple devices](how-to-investigate-sensor-detections-in-a-device-inventory.md#delete-devices) on OT sensors
 - An enhanced [editing device details](how-to-investigate-sensor-detections-in-a-device-inventory.md#edit-device-details) process on the OT sensor, using an **Edit** button in the toolbar at the top of the page
-- [Enhanced UI on the OT sensor for uploading an SSL/TLS certificate](how-to-deploy-certificates.md#deploy-ssltls-certificates-on-ot-appliances)
+- [Enhanced UI on the OT sensor for uploading an SSL/TLS certificate](ot-deploy/activate-deploy-sensor.md#deploy-an-ssltls-certificate)
 - [Activation files for locally managed sensors no longer expire](how-to-manage-individual-sensors.md#upload-a-new-activation-file)
 - Severity for all [**Suspicion of Malicious Activity**](alert-engine-messages.md#malware-engine-alerts) alerts is now **Critical**
 - [Allow internet connections on an OT network in bulk](how-to-accelerate-alert-incident-response.md#allow-internet-connections-on-an-ot-network)
@@ -215,12 +215,13 @@ This version includes the following new updates and fixes:
 - [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)
-- [Sensor connections restored after certificate rotation](how-to-deploy-certificates.md)
+- [Sensor connections restored after certificate rotation](ot-deploy/activate-deploy-sensor.md#deploy-an-ssltls-certificate)
 - [Upload diagnostic logs for support tickets from the Azure portal](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support)
 - [Improved security for uploading protocol plugins](resources-manage-proprietary-protocols.md)
 - [Sensor names shown in browser tabs](how-to-manage-individual-sensors.md)
 - [Site-based access control on the Azure portal](manage-users-portal.md#manage-site-based-access-control-public-preview)
 
+
 ## Versions 22.1.x
 
 Software versions 22.1.x support direct updates to the latest OT monitoring software versions available. For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md).
@@ -369,7 +370,7 @@ This version includes the following new updates and fixes:
 - [New PCAP API](api/management-alert-apis.md#pcap-request-alert-pcap)
 - [Export logs from the on-premises management console for troubleshooting](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](how-to-deploy-certificates.md)
+- [Unicode support for certificate passphrases](best-practices/plan-prepare-deploy.md#prepare-ca-signed-certificates)
 
 ## Next steps
 
diff --git a/articles/defender-for-iot/organizations/whats-new.md b/articles/defender-for-iot/organizations/whats-new.md
@@ -52,7 +52,7 @@ For more information, see [Device data retention periods](references-data-retent
 
 The OT sensor version 22.3.6 has an enhanced **SSL/TLS Certificates** configuration page for defining your SSL/TLS certificate settings and deploying a CA-signed certificate.
 
-For more information, see [Deploy SSL/TLS certificates on OT appliances](how-to-deploy-certificates.md).
+For more information, see [Deploy an SSL/TLS certificate](ot-deploy/activate-deploy-sensor.md#deploy-an-ssltls-certificate).
 
 ### Activation files expiration updates
 
@@ -554,9 +554,9 @@ For more information, see:
 
 ### Sensor connections restored after certificate rotation
 
-Starting in version 22.2.3, after rotating your certificates, your sensor connections are automatically restored to your central manager, and you don't need to reconnect them manually.
+Starting in version 22.2.3, after rotating your certificates, your sensor connections are automatically restored to your on-premises management console, and you don't need to reconnect them manually.
 
-For more information, see [About certificates](how-to-deploy-certificates.md).
+For more information, see [Prepare CA-signed certificates](best-practices/plan-prepare-deploy.md#prepare-ca-signed-certificates) and [Deploy an SSL/TLS certificate](ot-deploy/activate-deploy-sensor.md#deploy-an-ssltls-certificate).
 
 ### Support diagnostic log enhancements (Public preview)
 
