Merge pull request #281815 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/active-directory-b2c/custom-email-sendgrid.md

@@ -542,9 +542,9 @@ The Localization element allows you to support multiple locales or languages in
     <LocalizedString ElementType="DisplayControl" ElementId="emailVerificationControl" StringId="but_send_new_code">Send new code</LocalizedString>
     <LocalizedString ElementType="DisplayControl" ElementId="emailVerificationControl" StringId="but_change_claims">Change e-mail</LocalizedString>
     <!-- Claims-->
-    <LocalizedString ElementType="ClaimType" ElementId="emailVerificationCode" StringId="DisplayName">Verification Code</LocalizedString>
-    <LocalizedString ElementType="ClaimType" ElementId="emailVerificationCode" StringId="UserHelpText">Verification code received in the email.</LocalizedString>
-    <LocalizedString ElementType="ClaimType" ElementId="emailVerificationCode" StringId="AdminHelpText">Verification code received in the email.</LocalizedString>
+    <LocalizedString ElementType="ClaimType" ElementId="VerificationCode" StringId="DisplayName">Verification Code</LocalizedString>
+    <LocalizedString ElementType="ClaimType" ElementId="VerificationCode" StringId="UserHelpText">Verification code received in the email.</LocalizedString>
+    <LocalizedString ElementType="ClaimType" ElementId="VerificationCode" StringId="AdminHelpText">Verification code received in the email.</LocalizedString>
     <LocalizedString ElementType="ClaimType" ElementId="email" StringId="DisplayName">Email</LocalizedString>
     <!-- Email validation error messages-->
     <LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfSessionDoesNotExist">You have exceeded the maximum time allowed.</LocalizedString>

articles/app-service/environment/migration-alternatives.md

@@ -13,7 +13,7 @@ ms.author: jordanselig
 > There are two automated migration features available to help you upgrade to App Service Environment v3. To learn more about those features and for help deciding which migration option is right for you, see [Migration path decision tree](upgrade-to-asev3.md#migration-path-decision-tree). Consider one of the automated options for a quicker path to [App Service Environment v3](overview.md).
 >
 
-If you're currently using App Service Environment v1 or v2, you have the opportunity to migrate your workloads to [App Service Environment v3](overview.md). App Service Environment v3 has [advantages and feature differences](overview.md#feature-differences) that provide enhanced support for your workloads and can reduce overall costs. Consider using the [the automated migration features](upgrade-to-asev3.md) if your environment meets the criteria described in the [migration path decision tree](upgrade-to-asev3.md#migration-path-decision-tree).
+If you're currently using App Service Environment v1 or v2, you have the opportunity to migrate your workloads to [App Service Environment v3](overview.md). App Service Environment v3 has [advantages and feature differences](overview.md#feature-differences) that provide enhanced support for your workloads and can reduce overall costs. Consider using [the automated migration features](upgrade-to-asev3.md) if your environment meets the criteria described in the [migration path decision tree](upgrade-to-asev3.md#migration-path-decision-tree).
 
 If your App Service Environment isn't supported for the migration features, you must use one of the manual methods to migrate to App Service Environment v3.
 

articles/azure-resource-manager/management/tag-resources.md

@@ -63,7 +63,7 @@ For REST API operations, see [Azure Billing REST API Reference](/rest/api/billin
 
 ## Unique tags pagination 
 
-When calling the [Unique Tags API](/rest/api/resources/tags/list) there is a limit to the size of each API response page that is returned. A tag that has a large set of unique values will require the API to fetch the next page to retrieve the remaining set of values. When this happens the tag key is shown again to indicate that the vales are still under this key.  
+When calling the [Unique Tags API](/rest/api/resources/tags/list) there is a limit to the size of each API response page that is returned. A tag that has a large set of unique values will require the API to fetch the next page to retrieve the remaining set of values. When this happens the tag key is shown again to indicate that the values are still under this key.  
 
 This can result in some tools, like the Azure portal, to show the tag key twice.  
 

articles/chaos-studio/chaos-studio-tutorial-aad-outage-portal.md

@@ -1,6 +1,6 @@
 ---
-title: Use a chaos experiment template to induce an outage on an Azure Active Directory instance
-description: Use the Azure portal to create an experiment from the AAD outage experiment template.
+title: Use a chaos experiment template to induce an outage on a Microsoft Entra ID instance
+description: Use the Azure portal to create an experiment from the Microsoft Entra ID outage experiment template.
 author: prasha-microsoft
 ms.author: abbyweisberg
 ms.reviewer: prashabora
@@ -10,9 +10,9 @@ ms.date: 09/27/2023
 ms.custom: template-how-to
 ---
 
-# Use a chaos experiment template to induce an outage on an Azure Active Directory instance
+# Use a chaos experiment template to induce an outage on a Microsoft Entra ID instance
 
-You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you induce an outage on an Azure Active Directory resource using a pre-populated experiment template and Azure Chaos Studio.
+You can use a chaos experiment to verify that your application is resilient to failures by causing those failures in a controlled environment. In this article, you induce an outage on a Microsoft Entra ID resource using a pre-populated experiment template and Azure Chaos Studio.
 
 ## Prerequisites
 
@@ -40,7 +40,7 @@ Now you can create your experiment from a pre-filled experiment template. A chao
 1. In Chaos Studio, go to **Experiments** > **Create** > **New from template**.
 
    [![Screenshot that shows the Experiments screen, with the New from template button highlighted.](images/tutorial-aad-outage-create.png)](images/tutorial-aad-outage-create.png#lightbox)
-1. Select **AAD Outage**.
+1. Select **Microsoft Entra ID Outage**.
 
    [![Screenshot that shows the experiment templates screen, with the AAD outage template button highlighted.](images/tutorial-aad-outage-select.png)](images/tutorial-aad-outage-select.png#lightbox)
 1. Add a name for your experiment that complies with resource naming guidelines. Select **Next: Permissions**.
@@ -67,6 +67,6 @@ You're now ready to run your experiment.
 1. When **Status** changes to *Running*, select **Details** for the latest run under **History** to see details for the running experiment.
 
 ## Next steps
-Now that you've run an AAD outage template experiment, you're ready to:
+Now that you've run a Microsoft Entra ID outage template experiment, you're ready to:
 - [Manage your experiment](chaos-studio-run-experiment.md)
 - [Create an experiment that shut down all targets in a zone](chaos-studio-tutorial-dynamic-target-portal.md)

articles/container-apps/java-eureka-server.md

@@ -133,7 +133,7 @@ Now that you have an existing environment, you can create your container app and
 
     This command returns the URL of your container app that consumes registers with the Eureka server component. Copy the URL to a text editor so you can use it in a coming step.
 
-    Navigate top the `/allRegistrationStatus` route view all applications registered with the Eureka Server for Spring.
+    Navigate to the `/allRegistrationStatus` route to view all applications registered with the Eureka Server for Spring.
 
     The binding injects several configurations into the application as environment variables, primarily the `eureka.client.service-url.defaultZone` property. This property indicates the internal endpoint of the Eureka Server Java component.
 

articles/cost-management-billing/costs/tutorial-acm-opt-recommendations.md

@@ -87,6 +87,9 @@ After you choose a suitable size, select **Resize** to start the resize action.
 
 Resizing requires an actively running virtual machine to restart. If the virtual machine is in a production environment, we recommend that you run the resize operation after business hours. Scheduling the restart can reduce disruptions caused by momentarily unavailability.
 
+> [!TIP]  
+> If you’re unsure whether shutting down a VM will cause a problem for others, you can first restrict access to the VM. Consider [Configuring role assignments for the VM](/entra/identity/devices/howto-vm-sign-in-azure-ad-windows#configure-role-assignments-for-the-vm) to limit access to it. Afterward, you can [Monitor Azure Virtual Machines](../../virtual-machines/monitor-vm.md) to assess the VM’s usage and determine if limiting access caused problems for others.
+
 ## Verify the action
 
 When the VM resizing completes successfully, an Azure notification is shown.

articles/machine-learning/prompt-flow/how-to-end-to-end-llmops-with-prompt-flow.md

@@ -17,7 +17,7 @@ ms.date: 01/02/2024
 
 # LLMOps with prompt flow and GitHub
 
-Large Language Operations, or **LLMOps**, has become the cornerstone of efficient prompt engineering and LLM-infused application development and deployment. As the demand for LLM-infused applications continues to soar, organizations find themselves in need of a cohesive and streamlined process to manage their end-to-end lifecycle.
+Large Language Models Operations, or **LLMOps**, has become the cornerstone of efficient prompt engineering and LLM-infused application development and deployment. As the demand for LLM-infused applications continues to soar, organizations find themselves in need of a cohesive and streamlined process to manage their end-to-end lifecycle.
 
 Azure Machine Learning allows you to integrate with GitHub to automate the LLM-infused application development lifecycle with prompt flow.
 

articles/search/cognitive-search-defining-skillset.md

@@ -166,7 +166,7 @@ Context also determines where outputs are produced in the [enrichment tree](cogn
 
 Skills read from and write to an enriched document. Skill inputs specify the origin of the incoming data. It's often the root node of the enriched document. For blobs, a typical skill input is the document's content property. 
 
-[Skill reference documentation](cognitive-search-predefined-skills.md) for each skill describes the inputs it can consume. Each input has a "name" that identifies a specific input, and a "source" that specifies the location fo the data in the enriched document. The following example is from the Entity Recognition skill:
+[Skill reference documentation](cognitive-search-predefined-skills.md) for each skill describes the inputs it can consume. Each input has a "name" that identifies a specific input, and a "source" that specifies the location of the data in the enriched document. The following example is from the Entity Recognition skill:
 
 ```json
 "inputs": [

articles/virtual-desktop/troubleshoot-app-attach.md

@@ -48,7 +48,7 @@ To validate that your session hosts have the necessary access to a file share co
       ```powershell
       # Install the CimDiskImage PowerShell module, if it's not already installed.
       If (!(Get-Module -ListAvailable | ? Name -eq CimDiskImage)) {
-          Install-Module CimDiskImage -WhatIf
+          Install-Module CimDiskImage
       }
       
       # Import the CimDiskImage PowerShell module.

articles/virtual-machines/trusted-launch-existing-vm.md

@@ -17,7 +17,7 @@ ms.custom: template-how-to, devx-track-azurepowershell
 
 Azure Virtual Machines supports enabling Azure Trusted launch on existing [Azure Generation 2](generation-2.md) virtual machines (VMs) by upgrading to the [Trusted launch](trusted-launch.md) security type.
 
-[Trusted launch](trusted-launch.md) is a way to enable foundational compute security on [Azure Generation 2 VMs](generation-2.md) VMs and protects against advanced and persistent attack techniques like boot kits and rootkits. It does so by combining infrastructure technologies like Secure Boot, virtual Trusted Platform Module (vTPM), and boot integrity monitoring on your VM.
+[Trusted launch](trusted-launch.md) is a way to enable foundational compute security on [Azure Generation 2 VMs](generation-2.md) and protects against advanced and persistent attack techniques like boot kits and rootkits. It does so by combining infrastructure technologies like Secure Boot, virtual Trusted Platform Module (vTPM), and boot integrity monitoring on your VM.
 
 > [!IMPORTANT]
 > Support for *enabling Trusted launch on existing Azure Generation 1 VMs* is currently in private preview. You can gain access to preview by using the [registration form](https://aka.ms/Gen1ToTLUpgrade).