Merge pull request #299015 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Stacyrch140

articles/container-apps/metrics.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 11/01/2024
+ms.date: 04/28/2025
 ms.author: cshoe
 ---
 
@@ -26,7 +26,7 @@ Container Apps provides these basic metrics.
 | Network In Bytes | Replica, Revision | Network received bytes | `RxBytes` | Bytes |
 | Network Out Bytes | Replica, Revision | Network transmitted bytes | `TxBytes` | Bytes |
 | Replica count | Revision | Number of active replicas | `Replicas` | Count |
-| Replica Restart Count | Replica, Revision | Restarts count of container app replicas | `RestartCount` | Count |
+| Total Replica Restart Count | Replica, Revision | Total number of restarts since the replica came online | `RestartCount` | Count |
 | Requests | Replica, Revision, Status Code, Status Code Category | Requests processed | `Requests` | Count |
 | Reserved Cores | Revision | Number of reserved cores for container app revisions | `CoresQuotaUsed` | Count |
 | Resiliency Connection Timeouts | Revision | Total connection timeouts | `ResiliencyConnectTimeouts` | Count |
@@ -42,9 +42,6 @@ Container Apps provides these basic metrics.
 
 The metrics namespace is `Microsoft.App/containerapps`.
 
-> [!NOTE]
-> Replica restart count is the aggregate restart count over the specified time range, not the number of restarts that occurred at a point in time.
-
 Container Apps environments provides this basic metric. You can only view this metric in [Azure Monitor metrics](https://ms.portal.azure.com/?feature.allrts=true#view/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/~/metrics). 
 
 | Title | Dimensions | Description | Metric ID | Unit |

articles/event-hubs/event-hubs-quickstart-powershell.md

@@ -43,7 +43,7 @@ Run the following command to create an Event Hubs namespace in the resource grou
 
 ```azurepowershell-interactive
 $namespaceName="myNamespace$(Get-Random)"
-New-AzEventHubNamespace -ResourceGroupName $rgName -NamespaceName $namespaceName -Location $region
+New-AzEventHubNamespace -ResourceGroupName $rgName -Name $namespaceName -Location $region
 ```
 
 You see the output similar to the following one. You see the name of the namespace in the `Name` field. 

articles/governance/machine-configuration/how-to/assign-configuration/terraform.md

@@ -11,11 +11,6 @@ ms.custom: devx-track-terraform
 
 You can use [Terraform][01] to [deploy][02] machine configuration assignments.
 
-> [!IMPORTANT]
-> The Terraform provider [azurerm_policy_virtual_machine_configuration_assignment][03] hasn't been
-> updated to support the **assignmentType** property so only configurations that perform audits are
-> supported.
-
 ## Assign a custom configuration
 
 The following example assigns a custom configuration.

articles/iot-edge/tutorial-develop-for-linux-on-windows.md

@@ -30,7 +30,7 @@ In this tutorial, you learn how to:
 >
 > * Set up your development machine.
 > * Use IoT Edge development tools to create a new project.
-> * Build your project as a container and store it in an Azure container registry.
+> * Build your project as a container and store it in an Azure Container Registry.
 > * Deploy your code to an IoT Edge device.
 
 ## Prerequisites
@@ -424,14 +424,14 @@ Use the module's Dockerfile to build the module's Docker image:
 docker build --rm -f "<DockerFilePath>" -t <ImageNameAndTag> "<ContextPath>" 
 ```
 
-For example, assume that your command shell is in your project directory and your module name is `IotEdgeModule1`. To build the image for the local registry or an Azure container registry, use the following commands:
+For example, assume that your command shell is in your project directory and your module name is `IotEdgeModule1`. To build the image for the local registry or an Azure Container Registry, use the following commands:
 
 ```bash
 # Build the image for the local registry
 
 docker build --rm -f "./IotEdgeModule1/Dockerfile.amd64.debug" -t localhost:5000/iotedgemodule1:0.0.1-amd64 "./IotEdgeModule1"
 
-# Or build the image for an Azure container registry
+# Or build the image for an Azure Container Registry
 
 docker build --rm -f "./IotEdgeModule1/Dockerfile.amd64.debug" -t myacr.azurecr.io/iotedgemodule1:0.0.1-amd64 "./IotEdgeModule1"
 ```
@@ -449,7 +449,7 @@ For example:
 
 docker push localhost:5000/iotedgemodule1:0.0.1-amd64
 
-# Or push the Docker image to an Azure container registry
+# Or push the Docker image to an Azure Container Registry
 az acr login --name myacr
 docker push myacr.azurecr.io/iotedgemodule1:0.0.1-amd64
 ```
@@ -460,7 +460,7 @@ In Visual Studio, open the `deployment.debug.template.json` deployment manifest
 
 Before deployment, you need to update your Azure Container Registry credentials, your module images, and the proper `createOptions` values. For more information about `createOption` values, see [How to configure container create options for IoT Edge modules](how-to-use-create-options.md).
 
-1. If you're using an Azure container registry to store your module image, add your credentials to `deployment.debug.template.json` in the `edgeAgent` settings. For example:
+1. If you're using an Azure Container Registry to store your module image, add your credentials to `deployment.debug.template.json` in the `edgeAgent` settings. For example:
 
     ```json
     "modulesContent": {

articles/load-testing/resource-limits-quotas-capacity.md

@@ -51,9 +51,9 @@ The following limits apply on a per-region, per-subscription basis.
 
 ### Notifications
 The following limits apply on a per-region, per-subscription basis.
-| Resource  | Default limit |  Maximum limit |
-|---------| ---------: | ---------: |
-|Tests per notification rule  | 20 | |
+| Resource  | Default limit |
+|---------| ---------: | 
+|Tests per notification rule  | 20 |
 |Action groups per notification rule| 5| 
 
 ### Data retention