Merge pull request #242198 from pritamso/Broken-link-fix-hansgschossmann

Broken link fixed

Author: prmerger-automator[bot]

articles/industrial-iot/tutorial-deploy-industrial-iot-platform.md

@@ -49,7 +49,7 @@ The deployment script allows to select which set of components to deploy.
     - App Service Plan (shared with microservices), [App Service](https://azure.microsoft.com/services/app-service/) for hosting the Industrial IoT Engineering Tool cloud application
 - Simulation:
     - [Virtual machine](https://azure.microsoft.com/services/virtual-machines/), Virtual network, IoT Edge used for a factory simulation to show the capabilities of the platform and to generate sample telemetry
-- [Azure Kubernetes Service](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-deploy-aks.md) should be used to host the cloud microservices
+- [Azure Kubernetes Service](/azure/aks/learn/quick-kubernetes-deploy-cli) should be used to host the cloud microservices
 
 ## Deploy Azure IIoT Platform using the deployment script
 
@@ -98,14 +98,13 @@ The deployment script allows to select which set of components to deploy.
 
 Other hosting and deployment methods:
 
-- For production deployments that require staging, rollback, scaling, and resilience, the platform can be deployed into [Azure Kubernetes Service (AKS)](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-deploy-aks.md)
-- Deploying Azure Industrial IoT Platform microservices into an existing Kubernetes cluster using [Helm](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-deploy-helm.md).
+- For production deployments that require staging, rollback, scaling, and resilience, the platform can be deployed into [Azure Kubernetes Service (AKS)](/azure/aks/learn/quick-kubernetes-deploy-cli)
+- Deploying Azure Industrial IoT Platform microservices into an existing Kubernetes cluster using [Helm](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
 - Deploying [Azure Kubernetes Service (AKS) cluster on top of Azure Industrial IoT Platform created by deployment script and adding Azure Industrial IoT components into the cluster](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-add-aks-to-ps1.md).
 
 References:
-- [Deploying Azure Industrial IoT Platform](https://github.com/Azure/Industrial-IoT/tree/main/docs/deploy)
-- [How to deploy all-in-one](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-deploy-all-in-one.md)
-- [How to deploy platform into AKS](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-deploy-aks.md)
+- [Deploying Azure Industrial IoT Platform](/azure/industrial-iot/tutorial-deploy-industrial-iot-platform)
+- [How to deploy platform into AKS](/azure/aks/learn/quick-kubernetes-deploy-cli)
 
 
 ## Next steps

articles/industrial-iot/tutorial-publisher-configure-opc-publisher.md

@@ -42,7 +42,7 @@ To persist the security configuration of OPC Publisher, the certificate store mu
 
 ## Configuration via Configuration File
 
-The simplest way to configure OPC Publisher is via a configuration file. An example configuration file and format documentation are provided in the file [`publishednodes.json`](https://raw.githubusercontent.com/Azure/Industrial-IoT/main/components/opc-ua/src/Microsoft.Azure.IIoT.OpcUa.Edge.Publisher/tests/Engine/publishednodes.json) in this repository.
+The simplest way to configure OPC Publisher is via a configuration file. An example configuration file and format documentation are provided in the file [`publishednodes.json`](https://raw.githubusercontent.com/Azure/Industrial-IoT/main/src/Azure.IIoT.OpcUa.Publisher/tests/Publisher/publishednodes.json) in this repository.
 Configuration file syntax has changed over time. OPC Publisher still can read old formats, but converts them into the latest format when writing the file.
 
 A basic configuration file looks like this:
@@ -121,7 +121,7 @@ OPC Publisher implements the following [IoT Hub Direct Methods](../iot-hub/iot-h
 >[!NOTE]
 > This feature is only available in version 2.6 and above of OPC Publisher.
 
-A cloud-based, companion microservice with a REST interface is described and available [here](https://github.com/Azure/Industrial-IoT/blob/main/docs/services/publisher.md). It can be used to configure OPC Publisher via an OpenAPI-compatible interface, for example through Swagger.
+A cloud-based, companion microservice with a REST interface is described and available [here](https://github.com/Azure/Industrial-IoT/tree/main/docs/opc-publisher). It can be used to configure OPC Publisher via an OpenAPI-compatible interface, for example through Swagger.
 
 ## Configuration of the simple JSON telemetry format via Separate Configuration File