Merge pull request #225622 from pritamso/Broken-link-fix-PatAltimore

Broken link fix

Author: prmerger-automator[bot]

articles/iot-edge/configure-connect-verify-gpu.md

@@ -168,7 +168,7 @@ If you have an existing module on your IoT Edge device, adding a configuration u
    You should see the parameters you specified for `DeviceRequests` in the JSON printout in the console.
 
 > [!NOTE]
-> To understand the `DeviceRequests` parameter better, view the source code: [moby/host_config.go](https://github.com/moby/moby/blob/master/api/types/container/host_config.go)
+> To understand the `DeviceRequests` parameter better, view the source code: [moby/host_config.go](https://github.com/moby/moby/blob/master/api/types/container/hostconfig.go)
 
 ### Enable a GPU in a prefabricated NVIDIA module
 
@@ -235,4 +235,4 @@ az group list
 
 ## Next steps
 
-This article helped you set up your virtual machine and IoT Edge device to be GPU-accelerated. To run an application with a similar setup, try the learning path for [NVIDIA DeepStream development with Microsoft Azure](/training/paths/nvidia-deepstream-development-with-microsoft-azure/?WT.mc_id=iot-47680-cxa). The Learn tutorial shows you how to develop optimized Intelligent Video Applications that can consume multiple video, image, and audio sources.
+This article helped you set up your virtual machine and IoT Edge device to be GPU-accelerated. To run an application with a similar setup, try the learning path for [NVIDIA DeepStream development with Microsoft Azure](/training/paths/nvidia-deepstream-development-with-microsoft-azure/?WT.mc_id=iot-47680-cxa). The Learn tutorial shows you how to develop optimized Intelligent Video Applications that can consume multiple video, image, and audio sources.

articles/iot-edge/includes/iot-edge-create-container-registry.md

@@ -10,7 +10,7 @@ ms.author: patricka
 
 In this tutorial, you use the [Azure IoT Edge](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge) and [Azure IoT Hub](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-toolkit) extensions to build a module and create a **container image** from the files. Then you push this image to a **registry** that stores and manages your images. Finally, you deploy your image from your registry to run on your IoT Edge device.
 
-You can use any Docker-compatible registry to hold your container images. Two popular Docker registry services are [Azure Container Registry](/articles/container-registry/index.yml) and [Docker Hub](https://docs.docker.com/docker-hub/repos/#viewing-repository-tags). This tutorial uses Azure Container Registry.
+You can use any Docker-compatible registry to hold your container images. Two popular Docker registry services are [Azure Container Registry](/azure/container-registry/index) and [Docker Hub](https://docs.docker.com/docker-hub/repos/#viewing-repository-tags). This tutorial uses Azure Container Registry.
 
 If you don't already have a container registry, follow these steps to create a new one in Azure:
 
@@ -32,8 +32,8 @@ If you don't already have a container registry, follow these steps to create a n
 
 1. In the left pane of your container registry, select **Access keys** from the menu located under **Settings**.
 
-   :::image type="content" source="/media/iot-edge-create-container-registry/access-keys.png" alt-text="Screenshot of the Access Keys menu location.":::
+   :::image type="content" source="../media/iot-edge-create-container-registry/access-keys.png" alt-text="Screenshot of the Access Keys menu location.":::
 
 1. Enable **Admin user** with the toggle button and view the **Username** and **Password** for your container registry.
 
-1. Copy the values for **Login server**, **Username**, and **password** and save them somewhere convenient. You use these values throughout this tutorial to provide access to the container registry.
+1. Copy the values for **Login server**, **Username**, and **password** and save them somewhere convenient. You use these values throughout this tutorial to provide access to the container registry.

articles/iot-edge/includes/iot-edge-create-dps-enrollment-x509.md

@@ -15,7 +15,7 @@ If you are looking to provision a single IoT Edge device, create an **individual
 
 When you create an enrollment in DPS, you have the opportunity to declare an **Initial Device Twin State**. In the device twin, you can set tags to group devices by any metric you need in your solution, like region, environment, location, or device type. These tags are used to create [automatic deployments](../how-to-deploy-at-scale.md).
 
-For more information about enrollments in the device provisioning service, see [How to manage device enrollments](/articles/iot-dps/how-to-manage-enrollments.md).
+For more information about enrollments in the device provisioning service, see [How to manage device enrollments](/azure/iot-dps/how-to-manage-enrollments).
 
 # [Individual enrollment](#tab/individual-enrollment)
 
@@ -101,7 +101,7 @@ When you create an enrollment group, you have the option of using a verified cer
 
 #### Create enrollment group
 
-For more information about enrollments in the device provisioning service, see [How to manage device enrollments](/articles/iot-dps/how-to-manage-enrollments.md).
+For more information about enrollments in the device provisioning service, see [How to manage device enrollments](/azure/iot-dps/how-to-manage-enrollments).
 
 > [!TIP]
 > The steps in this article are for the Azure portal, but you can also create group enrollments using the Azure CLI. For more information, see [az iot dps enrollment-group](/cli/azure/iot/dps/enrollment-group). As part of the CLI command, use the **edge-enabled** flag to specify that the enrollment is for IoT Edge devices. For a group enrollment, all devices must be IoT Edge devices or none of them can be.

articles/iot-edge/includes/iot-edge-create-release-pipeline-for-continuous-deployment.md

@@ -81,8 +81,8 @@ Create a new pipeline, and add a new stage:
     | Deployment file | Put the path `$(System.DefaultWorkingDirectory)/Drop/drop/configs/deployment.json`. This path is the file IoT Edge deployment manifest file. |
     | Azure subscription | Select the subscription that contains your IoT Hub.|
     | IoT Hub name | Select your IoT hub.|
-    | Choose single/multiple device | Choose whether you want the release pipeline to deploy to one or multiple devices. If you deploy to a single device, enter the **IoT Edge device ID**. If you are deploying to multiple devices, specify the device **target condition**. The target condition is a filter to match a set of IoT Edge devices in IoT Hub. If you want to use device tags as the condition, you need to update your corresponding devices tags with IoT Hub device twin. Update the **IoT Edge deployment ID** and **IoT Edge deployment priority** in the advanced settings. For more information about creating a deployment for multiple devices, see [Understand IoT Edge automatic deployments](/articles/iot-edge/module-deployment-monitoring.md). |
-    | Device ID or target condition | Depending on the prior selection, specify a device ID or [target condition](/articles/iot-edge/module-deployment-monitoring.md#target-condition) to deploy to multiple devices. |
+    | Choose single/multiple device | Choose whether you want the release pipeline to deploy to one or multiple devices. If you deploy to a single device, enter the **IoT Edge device ID**. If you are deploying to multiple devices, specify the device **target condition**. The target condition is a filter to match a set of IoT Edge devices in IoT Hub. If you want to use device tags as the condition, you need to update your corresponding devices tags with IoT Hub device twin. Update the **IoT Edge deployment ID** and **IoT Edge deployment priority** in the advanced settings. For more information about creating a deployment for multiple devices, see [Understand IoT Edge automatic deployments](/azure/iot-edge/module-deployment-monitoring). |
+    | Device ID or target condition | Depending on the prior selection, specify a device ID or [target condition](/azure/iot-edge/module-deployment-monitoring#target-condition) to deploy to multiple devices. |
     | Advanced | For the IoT Edge deployment ID, specify `$(System.TeamProject)-$(Release.EnvironmentName)`. This variable maps the project and release name with your IoT Edge deployment ID. |
     
 

articles/iot-edge/includes/iot-edge-install-linux-on-windows.md

@@ -62,14 +62,14 @@ Deploy Azure IoT Edge for Linux on Windows on your target device.
    >   Deploy-Eflow -cpuCount 1 -memoryInMB 1024 -vmDataSize 2
    >   ```
    >
-   >For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/articles/iot-edge/reference-iot-edge-for-linux-on-windows-functions.md#deploy-eflow).
+   >For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions#deploy-eflow).
 
    >[!WARNING]
    >By default, the EFLOW Linux virtual machine has no DNS configuration. Deployments using DHCP will try to obtain the DNS configuration propagated by the DHCP server. Please check your DNS configuration to ensure internet connectivity. For more information, see [AzEFLOW-DNS](https://aka.ms/AzEFLOW-DNS).
 
-   You can assign a GPU to your deployment to enable GPU-accelerated Linux modules. To gain access to these features, you will need to install the prerequisites detailed in [GPU acceleration for Azure IoT Edge for Linux on Windows](/articles/iot-edge/gpu-acceleration.md).
+   You can assign a GPU to your deployment to enable GPU-accelerated Linux modules. To gain access to these features, you will need to install the prerequisites detailed in [GPU acceleration for Azure IoT Edge for Linux on Windows](/azure/iot-edge/gpu-acceleration).
 
-   To use a GPU passthrough, add the **gpuName**, **gpuPassthroughType**, and **gpuCount** parameters to your `Deploy-Eflow` command. For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/articles/iot-edge/reference-iot-edge-for-linux-on-windows-functions.md#deploy-eflow).
+   To use a GPU passthrough, add the **gpuName**, **gpuPassthroughType**, and **gpuCount** parameters to your `Deploy-Eflow` command. For information about all the optional parameters available, see [PowerShell functions for IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions#deploy-eflow).
 
    >[!WARNING]
    >Enabling hardware device passthrough may increase security risks. Microsoft recommends a device mitigation driver from your GPU's vendor, when applicable. For more information, see [Deploy graphics devices using discrete device assignment](/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda).

articles/iot-edge/includes/iot-edge-install-linux.md

@@ -151,7 +151,7 @@ Install the latest version of IoT Edge and the IoT identity service package (if
      sudo apt-get install aziot-edge defender-iot-micro-agent-edge
    ```
 
-The `defender-iot-micro-agent-edge` package includes the Microsoft Defender for IoT security micro-agent that provides endpoint visibility into security posture management, vulnerabilities, threat detection, fleet management and more to help you secure your IoT Edge devices. It's recommended to install the micro agent with the Edge agent to enable security monitoring and hardening of your Edge devices. To learn more about Microsoft Defender for IoT, see [What is Microsoft Defender for IoT for device builders](/articles/defender-for-iot/device-builders/overview.md).
+The `defender-iot-micro-agent-edge` package includes the Microsoft Defender for IoT security micro-agent that provides endpoint visibility into security posture management, vulnerabilities, threat detection, fleet management and more to help you secure your IoT Edge devices. It's recommended to install the micro agent with the Edge agent to enable security monitoring and hardening of your Edge devices. To learn more about Microsoft Defender for IoT, see [What is Microsoft Defender for IoT for device builders](/azure/defender-for-iot/device-builders/overview).
 
 # [Debian](#tab/debian)
 
@@ -162,7 +162,7 @@ Install the latest version of IoT Edge and the IoT identity service package (if
      sudo apt-get install aziot-edge defender-iot-micro-agent-edge
    ```
 
-The defender-iot-micro-agent-edge package includes the Microsoft Defender for IoT security micro-agent that provides endpoint visibility into security posture management, vulnerabilities, threat detection, fleet management and more to help you secure your IoT Edge devices. It's recommended to install the micro agent with the Edge agent to enable security monitoring and hardening of your Edge devices. To learn more about Microsoft Defender for IoT, see [What is Microsoft Defender for IoT for device builders](/articles/defender-for-iot/device-builders/overview.md).
+The defender-iot-micro-agent-edge package includes the Microsoft Defender for IoT security micro-agent that provides endpoint visibility into security posture management, vulnerabilities, threat detection, fleet management and more to help you secure your IoT Edge devices. It's recommended to install the micro agent with the Edge agent to enable security monitoring and hardening of your Edge devices. To learn more about Microsoft Defender for IoT, see [What is Microsoft Defender for IoT for device builders](/azure/defender-for-iot/device-builders/overview).
 
 # [Red Hat Enterprise Linux](#tab/rhel)
 

articles/iot-edge/includes/iot-edge-install-windows.md

@@ -23,7 +23,7 @@ To install the IoT Edge runtime:
    (Get-Process -Id $PID).StartInfo.EnvironmentVariables["PROCESSOR_ARCHITECTURE"]
    ```
 
-2. Run the [Deploy-IoTEdge](/articles/iot-edge/reference-windows-scripts.md#deploy-iotedge) command, which performs the following tasks:
+2. Run the [Deploy-IoTEdge](/azure/iot-edge/reference-windows-scripts#deploy-iotedge) command, which performs the following tasks:
 
    * Checks that your Windows machine is on a supported version
    * Turns on the containers feature
@@ -41,4 +41,4 @@ When you install IoT Edge on a device, you can use additional parameters to modi
 * Direct traffic to go through a proxy server
 * Point the installer to a local directory for offline installation
 
-For more information about these additional parameters, see [PowerShell scripts for IoT Edge with Windows containers](/articles/iot-edge/reference-windows-scripts.md).
+For more information about these additional parameters, see [PowerShell scripts for IoT Edge with Windows containers](/azure/iot-edge/reference-windows-scripts).

articles/iot-edge/includes/iot-edge-prerequisites-at-scale-cloud-resources.md

@@ -11,5 +11,5 @@ services: iot-edge
 
 * An active IoT hub
 * An instance of the IoT Hub device provisioning service in Azure, linked to your IoT hub
-  * If you don't have a device provisioning service instance, you can follow the instructions in the [Create a new IoT Hub device provisioning service](/articles/iot-dps/quick-setup-auto-provision.md#create-a-new-iot-hub-device-provisioning-service) and [Link the IoT hub and your device provisioning service](/articles/iot-dps/quick-setup-auto-provision.md#link-the-iot-hub-and-your-device-provisioning-service) sections of the IoT Hub device provisioning service quickstart.
+  * If you don't have a device provisioning service instance, you can follow the instructions in the [Create a new IoT Hub device provisioning service](/azure/iot-dps/quick-setup-auto-provision#create-a-new-iot-hub-device-provisioning-service) and [Link the IoT hub and your device provisioning service](/azure/iot-dps/quick-setup-auto-provision#link-the-iot-hub-and-your-device-provisioning-service) sections of the IoT Hub device provisioning service quickstart.
   * After you have the device provisioning service running, copy the value of **ID Scope** from the overview page. You use this value when you configure the IoT Edge runtime.