Merge pull request #261949 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: Taojunshen

articles/azure-monitor/agents/azure-monitor-agent-send-data-to-event-hubs-and-storage.md

@@ -603,6 +603,7 @@ Use custom template deployment to create the DCR association and AMA deployment.
             "authentication": {
                 "managedIdentity": {
                 "identifier-type": "mi_res_id",
+                "identifier-name": "mi_res_id",
                 "identifier-value": "[resourceID('Microsoft.ManagedIdentity/userAssignedIdentities/',parameters('identityName'))]"
                 }
             }
@@ -680,6 +681,7 @@ Use custom template deployment to create the DCR association and AMA deployment.
             "authentication": {
                 "managedIdentity": {
                 "identifier-type": "mi_res_id",
+                "identifier-name": "mi_res_id",
                 "identifier-value": "[resourceID('Microsoft.ManagedIdentity/userAssignedIdentities/',parameters('identityName'))]"
                 }
             }

articles/copilot/analyze-cost-management.md

@@ -30,7 +30,7 @@ Here are a few examples of the kinds of prompts you can use for Cost Management.
 - "Can you provide an estimate of our expected expenses for the next 6 months?"
 - "Show me the resource group with the highest spending in the last 6 months."
 - "How can we reduce our costs?"
-- "Which resources are covered by savings plans?
+- "Which resources are covered by savings plans?"
 
 ## Examples
 

articles/frontdoor/how-to-configure-endpoints.md

@@ -16,7 +16,7 @@ This article shows you how to add a new endpoint to an existing Azure Front Door
 
 ## Prerequisites
 
-Before you can create a new endpoint with Front Door manager, you must have an Azure Front Door profile created. To create an Azure Front Door profile, see [create a Azure Front Door](create-front-door-portal.md). The profile must have at least one endpoint.
+Before you can create a new endpoint with Front Door manager, you must have an Azure Front Door profile created. To create an Azure Front Door profile, see [create an Azure Front Door](create-front-door-portal.md). The profile must have at least one endpoint.
 
 ## Create a new Front Door endpoint
 

articles/governance/policy/concepts/initiative-definition-structure.md

@@ -139,7 +139,7 @@ Parameters work the same way when building policy initiatives. By including para
 initiative definition, you can reuse that parameter in the included policies.
 
 > [!NOTE]
-> Once an initiative is assigned, initative level parameters can't be altered. Due to this, the
+> Once an initiative is assigned, initiative level parameters can't be altered. Due to this, the
 > recommendation is to set a **defaultValue** when defining the parameter.
 
 ### Parameter properties

articles/machine-learning/concept-mlflow-models.md

@@ -57,7 +57,7 @@ mlflow.sklearn.log_model(sklearn_estimator, "classifier")
 
 ## The MLmodel format
 
-MLflow adopts the MLmodel format as a way to create a contract between the artifacts and what they represent. The MLmodel format stores assets in a folder. Among these assets, there's a file named `MLmodel`. this file is the single source of truth about how a model can be loaded and used.
+MLflow adopts the MLmodel format as a way to create a contract between the artifacts and what they represent. The MLmodel format stores assets in a folder. Among these assets, there's a file named `MLmodel`. This file is the single source of truth about how a model can be loaded and used.
 
 The following screenshot shows a sample MLflow model's folder in the Azure Machine Learning studio. The model is placed in a folder called `credit_defaults_model`. There is no specific requirement on the naming of this folder. The folder contains the `MLmodel` file among other model artifacts.
 

articles/role-based-access-control/built-in-roles.md

@@ -914,8 +914,8 @@ View Virtual Machines in the portal and login as administrator
 > | **DataActions** |  |
 > | [Microsoft.Compute](resource-provider-operations.md#microsoftcompute)/virtualMachines/login/action | Log in to a virtual machine as a regular user |
 > | [Microsoft.Compute](resource-provider-operations.md#microsoftcompute)/virtualMachines/loginAsAdmin/action | Log in to a virtual machine with Windows administrator or Linux root user privileges |
-> | [Microsoft.HybridCompute](resource-provider-operations.md#microsofthybridcompute)/machines/login/action | Log in to a Azure Arc machine as a regular user |
-> | [Microsoft.HybridCompute](resource-provider-operations.md#microsofthybridcompute)/machines/loginAsAdmin/action | Log in to a Azure Arc machine with Windows administrator or Linux root user privilege |
+> | [Microsoft.HybridCompute](resource-provider-operations.md#microsofthybridcompute)/machines/login/action | Log in to an Azure Arc machine as a regular user |
+> | [Microsoft.HybridCompute](resource-provider-operations.md#microsofthybridcompute)/machines/loginAsAdmin/action | Log in to an Azure Arc machine with Windows administrator or Linux root user privilege |
 > | **NotDataActions** |  |
 > | *none* |  |
 

articles/virtual-machines/image-version.md

@@ -15,7 +15,7 @@ ms.custom:
 
 # Create an image definition and an image version 
 
-A [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) simplifies custom image sharing across your organization. Custom images are like marketplace images, but you create them yourself. Images can be created from a VM, VHD, snapshot, managed image, or another image version. 
+An [Azure Compute Gallery](shared-image-galleries.md) (formerly known as Shared Image Gallery) simplifies custom image sharing across your organization. Custom images are like marketplace images, but you create them yourself. Images can be created from a VM, VHD, snapshot, managed image, or another image version. 
 
 The Azure Compute Gallery lets you share your custom VM images with others in your organization, within or across regions, within a Microsoft Entra tenant, or publicly using a [community gallery](azure-compute-gallery.md#community). Choose which images you want to share, which regions you want to make them available in, and who you want to share them with. You can create multiple galleries so that you can logically group images. Many new features like ARM64, Accelerated Networking and TrustedVM are only supported through Azure Compute Gallery and not available for managed images.