Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tsk544797-sfi-ssh

asudbring · asudbring · commit a5e5356f33dc · 2026-02-19T14:28:57.000-06:00
diff --git a/articles/application-gateway/configuration-infrastructure.md b/articles/application-gateway/configuration-infrastructure.md
@@ -84,7 +84,7 @@ Depending on whether you're creating new resources or using existing ones, add t
 
 | Resource | Resource status | Required Azure permissions |
 | --- | --- | --- |
-| Subnet | Create new | `Microsoft.Network/virtualNetworks/subnets/write' <br> 'Microsoft.Network/virtualNetworks/subnets/join/action` |
+| Subnet | Create new | `Microsoft.Network/virtualNetworks/subnets/write` <br> 'Microsoft.Network/virtualNetworks/subnets/join/action` |
 | Subnet | Use existing | `Microsoft.Network/virtualNetworks/subnets/read` <br> `Microsoft.Network/virtualNetworks/subnets/join/action` |
 | IP addresses | Create new | `Microsoft.Network/publicIPAddresses/write` <br> `Microsoft.Network/publicIPAddresses/join/action` |
 | IP addresses | Use existing | `Microsoft.Network/publicIPAddresses/read` <br> `Microsoft.Network/publicIPAddresses/join/action` |
diff --git a/articles/azure-resource-manager/management/tag-support.md b/articles/azure-resource-manager/management/tag-support.md
@@ -2900,7 +2900,7 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > [!div class="mx-tableFixed"]
 > | Resource type | Supports tags | Tag in cost report |
 > | ------------- | ----------- | ----------- |
-> | accounts | Yes | Yes |
+> | accounts | Yes | No |
 > | investigations | No | No |
 > | pipelineGroups | Yes | Yes |
 
diff --git a/articles/iot-edge/about-iot-edge.md b/articles/iot-edge/about-iot-edge.md
@@ -23,7 +23,7 @@ Azure IoT Edge is a device-focused runtime that enables you to deploy, run, and
 
 Analytics drives business value in IoT solutions, but not all analytics need to be in the cloud. Azure IoT Edge helps you bring the analytical power of the cloud closer to your devices to drive better business insights and enable offline decision making. For example, you can run anomaly detection at the edge to respond as quickly as possible to emergencies happening on a production line. If you want to reduce bandwidth costs and avoid transferring terabytes of raw data, you can clean and aggregate the data locally then only send the insights to the cloud for analysis.
 
-Azure IoT Edge brings edge-based capabilities to a cloud-based solution and is a feature of [Azure IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md) that enables you to scale out and manage an IoT solution from the cloud. By packaging your business logic into standard containers and using optional pre-built IoT Edge module images from partners or the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name), you can easily compose, deploy, and maintain your solution.
+Azure IoT Edge brings edge-based capabilities to a cloud-based solution and is a feature of [Azure IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md) that enables you to scale out and manage an IoT solution from the cloud. By packaging your business logic into standard containers and using optional pre-built IoT Edge module images from partners or the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name), you can easily compose, deploy, and maintain your solution.
 
 Azure IoT Edge is made up of three components:
 
diff --git a/articles/iot-edge/how-to-access-built-in-metrics.md b/articles/iot-edge/how-to-access-built-in-metrics.md
@@ -16,7 +16,7 @@ services: iot-edge
 
 The IoT Edge runtime components, IoT Edge hub, and IoT Edge agent, produce built-in metrics in the [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/). Access these metrics remotely to monitor and understand the health of an IoT Edge device.
 
-Use your own solution to access these metrics, or use the [metrics-collector module](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-metrics-collector/tags), which collects the built-in metrics and sends them to Azure Monitor or Azure IoT Hub. For more information, see [Collect and transport metrics](how-to-collect-and-transport-metrics.md).
+Use your own solution to access these metrics, or use the [metrics-collector module](https://mcr.microsoft.com/artifact/mar/azureiotedge-metrics-collector/tags), which collects the built-in metrics and sends them to Azure Monitor or Azure IoT Hub. For more information, see [Collect and transport metrics](how-to-collect-and-transport-metrics.md).
 
 Metrics are exposed by default on **port 9600** of the **edgeHub** and **edgeAgent** modules (`http://edgeHub:9600/metrics` and `http://edgeAgent:9600/metrics`). They aren't mapped to the host by default.
 
diff --git a/articles/iot-edge/how-to-collect-and-transport-metrics.md b/articles/iot-edge/how-to-collect-and-transport-metrics.md
@@ -58,7 +58,7 @@ To configure monitoring on your IoT Edge device, follow the [tutorial about moni
 
 A Microsoft-supplied metrics-collector module can be added to an IoT Edge deployment to collect module metrics and send them to Azure Monitor. The module code is open-source and available in the [IoT Edge GitHub repo](https://github.com/Azure/iotedge/tree/main/edge-modules/metrics-collector).
 
-The metrics-collector module is provided as a multi-arch Docker container image that supports Linux X64, ARM32, ARM64, and Windows X64 (version 1809). It's publicly available from the Microsoft Artifact Registry at [`mcr.microsoft.com/azureiotedge-metrics-collector`](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-metrics-collector/tags).
+The metrics-collector module is provided as a multi-arch Docker container image that supports Linux X64, ARM32, ARM64, and Windows X64 (version 1809). It's publicly available from the Microsoft Artifact Registry at [`mcr.microsoft.com/azureiotedge-metrics-collector`](https://mcr.microsoft.com/artifact/mar/azureiotedge-metrics-collector/tags).
 
 ## Metrics collector configuration
 
diff --git a/articles/iot-edge/how-to-configure-api-proxy-module.md b/articles/iot-edge/how-to-configure-api-proxy-module.md
@@ -28,7 +28,7 @@ Without the API proxy, each service module must bind to a separate port on the h
 
 ## Deploy the proxy module
 
-The API proxy module is available from the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-api-proxy/tags), and the image URI is `mcr.microsoft.com/azureiotedge-api-proxy:latest`. Deploy the module using the [Azure portal](how-to-deploy-modules-portal.md) or [Azure CLI](how-to-deploy-modules-cli.md).
+The API proxy module is available from the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/artifact/mar/azureiotedge-api-proxy/tags), and the image URI is `mcr.microsoft.com/azureiotedge-api-proxy:latest`. Deploy the module using the [Azure portal](how-to-deploy-modules-portal.md) or [Azure CLI](how-to-deploy-modules-cli.md).
 
 ## Understand the proxy module
 
diff --git a/articles/iot-edge/how-to-connect-downstream-iot-edge-device.md b/articles/iot-edge/how-to-connect-downstream-iot-edge-device.md
@@ -620,7 +620,7 @@ The API proxy module was designed to be customized to handle most common gateway
     | Restart policy     | always                                            |
     | Desired status     | running                                           |
 
-    If you want to use a different version or architecture of the API proxy module, find the available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-api-proxy/tags).
+    If you want to use a different version or architecture of the API proxy module, find the available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/artifact/mar/azureiotedge-api-proxy/tags).
 
    1. In the **Environment variables** tab, add a variable named  `NGINX_DEFAULT_PORT` of type *Text* with a value of `443`.
    1. In the **Container create options** tab, update the port bindings to reference port 443.
@@ -866,7 +866,7 @@ The API proxy module was designed to be customized to handle most common gateway
     | Restart policy     | `always`                                          |
     | Desired status     | `running`                                         |
 
-    If you want to use a different version or architecture of the API proxy module, find the available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-api-proxy/tags).
+    If you want to use a different version or architecture of the API proxy module, find the available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/artifact/mar/azureiotedge-api-proxy/tags).
 
    1. In the **Environment variables** tab, add a variable named  `NGINX_DEFAULT_PORT` of type *Text* with a value of `443`.
    1. In the **Container create options** tab, update the port bindings to reference port 443.
diff --git a/articles/iot-edge/how-to-deploy-at-scale.md b/articles/iot-edge/how-to-deploy-at-scale.md
@@ -71,7 +71,7 @@ To add custom code as a module, or to manually add an Azure service module, foll
 1. In the **IoT Edge Modules** section of the page, select **Add**.
 1. Choose one of the types of modules from the drop-down menu:
 
-   * **IoT Edge Module** - You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is `mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.5`. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
+   * **IoT Edge Module** - You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is `mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.5`. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
    * **Azure Stream Analytics Module** - Modules generated from an Azure Stream Analytics workload.
 
 1. If needed, repeat steps 2 and 3 to add more modules to your deployment.
diff --git a/articles/iot-edge/how-to-deploy-modules-portal.md b/articles/iot-edge/how-to-deploy-modules-portal.md
@@ -58,7 +58,7 @@ The Azure portal has a wizard that walks you through creating the deployment man
 
 #### IoT Edge Module
 
-Use this option to add Microsoft modules, partner modules, or custom modules. You provide the module name and container image URI. The container image URI is the location of the module image in a container registry. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name). For partner modules, contact the IoT Edge module publisher to obtain the container image URI.
+Use this option to add Microsoft modules, partner modules, or custom modules. You provide the module name and container image URI. The container image URI is the location of the module image in a container registry. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name). For partner modules, contact the IoT Edge module publisher to obtain the container image URI.
 
 For example to add the Microsoft simulated temperature sensor module:
 
diff --git a/articles/iot-edge/quickstart-linux.md b/articles/iot-edge/quickstart-linux.md
@@ -191,7 +191,7 @@ Manage your Azure IoT Edge device from the cloud to deploy a module that sends d
 
 :::image type="content" source="./media/quickstart-linux/deploy-module.png" alt-text="Diagram of how to deploy a module from cloud to device.":::
 
-A key capability of Azure IoT Edge is deploying code to your IoT Edge devices from the cloud. *IoT Edge modules* are executable packages implemented as containers. In this section, you deploy a pre-built module from the [IoT Edge Modules section of Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
+A key capability of Azure IoT Edge is deploying code to your IoT Edge devices from the cloud. *IoT Edge modules* are executable packages implemented as containers. In this section, you deploy a pre-built module from the [IoT Edge Modules section of Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
 
 The module that you deploy in this section simulates a sensor and sends generated data. This module is a useful piece of code when you're getting started with IoT Edge because you can use the simulated data for development and testing. If you want to see exactly what this module does, you can view the [simulated temperature sensor source code](https://github.com/Azure/iotedge/blob/main/edge-modules/SimulatedTemperatureSensor/src/Program.cs).
 
diff --git a/articles/iot-edge/quickstart.md b/articles/iot-edge/quickstart.md
@@ -176,7 +176,7 @@ Manage your Azure IoT Edge device from the cloud to deploy a module that sends t
 
 :::image type="content" source="./media/quickstart/deploy-module.png" alt-text="Diagram that shows the step to deploy a module.":::
 
-One of the key capabilities of Azure IoT Edge is deploying code to your IoT Edge devices from the cloud. *IoT Edge modules* are executable packages implemented as containers. In this section, you'll deploy a pre-built module from the [IoT Edge Modules section of Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
+One of the key capabilities of Azure IoT Edge is deploying code to your IoT Edge devices from the cloud. *IoT Edge modules* are executable packages implemented as containers. In this section, you'll deploy a pre-built module from the [IoT Edge Modules section of Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
 
 The module that you deploy in this section simulates a sensor and sends generated data. This module is a useful piece of code when you're getting started with IoT Edge because you can use the simulated data for development and testing. If you want to see exactly what this module does, you can view the [simulated temperature sensor source code](https://github.com/Azure/iotedge/blob/main/edge-modules/SimulatedTemperatureSensor/src/Program.cs).
 
diff --git a/articles/iot-edge/tutorial-monitor-with-workbooks.md b/articles/iot-edge/tutorial-monitor-with-workbooks.md
@@ -36,7 +36,7 @@ Every IoT Edge device relies on two modules, called the *runtime modules*, that
 
 Both runtime modules create metrics that let you remotely monitor how an IoT Edge device or its individual modules perform. The IoT Edge agent reports on the state of individual modules and the host device, so it creates metrics like how long a module runs correctly, or the amount of RAM and percent of CPU used on the device. The IoT Edge hub reports on communications on the device, so it creates metrics like the total number of messages sent and received, or the time it takes to resolve a direct method. For the full list of available metrics, see [Access built-in metrics](how-to-access-built-in-metrics.md).
 
-Both modules automatically expose these metrics, so you can create your own solutions to access and report on them. To make this process easier, Microsoft provides the [azureiotedge-metrics-collector module](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-metrics-collector/tags), which handles this process if you don't have or want a custom solution. The metrics collector module collects metrics from the two runtime modules and any other modules you want to monitor, and sends them off the device.
+Both modules automatically expose these metrics, so you can create your own solutions to access and report on them. To make this process easier, Microsoft provides the [azureiotedge-metrics-collector module](https://mcr.microsoft.com/artifact/mar/azureiotedge-metrics-collector/tags), which handles this process if you don't have or want a custom solution. The metrics collector module collects metrics from the two runtime modules and any other modules you want to monitor, and sends them off the device.
 
 The metrics collector module sends your metrics to the cloud in one of two ways. The first option, used in this tutorial, sends the metrics directly to Log Analytics. The second option is recommended only if your networking policies require it. It sends the metrics through IoT Hub and then sets up a route to pass the metric messages to Log Analytics. Either way, once the metrics are in your Log Analytics workspace, you can view them through Azure Monitor workbooks.
 
@@ -114,7 +114,7 @@ Follow these steps to deploy and configure the collector module:
         | Restart policy     | always                                                               |
         | Desired status     | running                                                              |
 
-   To use a different version or architecture of the metrics collector module, find available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-metrics-collector/tags).
+   To use a different version or architecture of the metrics collector module, find available images in the [Microsoft Artifact Registry](https://mcr.microsoft.com/artifact/mar/azureiotedge-metrics-collector/tags).
 
    1. Go to the **Environment Variables** tab.
    1. Add the following text-type environment variables:
diff --git a/articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md b/articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md
@@ -26,7 +26,7 @@ This tutorial shows you how to create a hierarchy of IoT Edge devices using IoT
 > * Configure the IoT Edge runtime on the devices in your hierarchy.
 > * Install consistent certificates across your device hierarchy.
 > * Add workloads to the devices in your hierarchy.
-> * Use the [IoT Edge API Proxy module](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-api-proxy/) to securely route HTTP traffic over a single port from your lower layer devices.
+> * Use the [IoT Edge API Proxy module](https://mcr.microsoft.com/artifact/mar/azureiotedge-api-proxy/) to securely route HTTP traffic over a single port from your lower layer devices.
 
 >[!TIP]
 >This tutorial includes a mixture of manual and automated steps to provide a showcase of nested IoT Edge features.
diff --git a/articles/iot-edge/tutorial-nested-iot-edge.md b/articles/iot-edge/tutorial-nested-iot-edge.md
@@ -31,7 +31,7 @@ This tutorial shows you how to create a hierarchy of IoT Edge devices, deploy Io
 > * Configure the IoT Edge runtime on the devices in your hierarchy.
 > * Install consistent certificates across your device hierarchy.
 > * Add workloads to the devices in your hierarchy.
-> * Use the [IoT Edge API Proxy module](https://mcr.microsoft.com/en-us/artifact/mar/azureiotedge-api-proxy/tags) to securely route HTTP traffic over a single port from your lower layer devices.
+> * Use the [IoT Edge API Proxy module](https://mcr.microsoft.com/artifact/mar/azureiotedge-api-proxy/tags) to securely route HTTP traffic over a single port from your lower layer devices.
 
 >[!TIP]
 >This tutorial includes a mixture of manual and automated steps to provide a showcase of nested IoT Edge features.
