Merge pull request #257907 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: Saisang

articles/azure-monitor/agents/media/azure-monitor-agent/linux-agent-syslog-communication.png

@@ -602,6 +602,21 @@ Write-Host "My Azure AD Application (ObjectId): " + $myApp.ObjectId
 Write-Host "My Azure AD Application's Roles"
 Write-Host $myApp.AppRoles
 ```
+### Migrate Runbook action from "Run as account" to "Run as Managed Identity"  
+> [!NOTE]
+>
+> Azure Automation "Run as account" has [retired](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2023/) on 30 September 2023, which affects actions created with action type "Automation Runbook". Existing actions linking to "Run as account" runbooks won't be supported after retirement. However, those runbooks would continue to execute until the expiry of "Run as" certificate of the Automation account.
+
+To ensure you can continue using the runbook actions, you need to:
+1.  Edit the action group by adding a new action with action type "Automation Runbook" and choose the same runbook from the dropdown. (All 5 runbooks in the dropdown have been reconfigured at the backend to authenticate using Managed Identity instead of Run as account. System-assigned Managed Identity in Automation account would be enabled with VM Contributor role at the subscription level would be assigned automatically.)
+
+    :::image type="content" source="./media/action-groups/action-group-runbook-add.png" alt-text="Screenshot of adding a runbook action to an action group.":::
+
+    :::image type="content" source="./media/action-groups/action-group-runbook-configure.png" alt-text="Screenshot of configuring the runbook action.":::
+
+2. Delete old runbook action which links to a "Run as account" runbook.
+3. Save the action group.
+
 ## Next steps
 
 - Get an [overview of alerts](./alerts-overview.md) and learn how to receive alerts.

articles/azure-monitor/alerts/action-groups.md

@@ -169,7 +169,7 @@ For an end-to-end overview of this procedure, view the [Azure VMware Solution: C
    The selections define the resources where VMs can consume VMware HCX services.
 
    > [!NOTE]
-   > If you have a mixed mode SDDC with a AV64 cluster, deployment of service mesh appliances on AV64 cluster is not viable/supported. However, this would't prevent you from having HCX migration or network extention directly on to AV64 clusters with service appliances hosted on cluster-1.
+   > In a mixed-mode SDDC with an AV64 cluster, deploying service mesh appliances on the AV64 cluster is not viable or supported. Nevertheless, this doesn't impede you from conducting HCX migration or network extension directly onto AV64 clusters. The deployment container can be cluster-1, hosting the HCX appliances. 
 
    :::image type="content" source="media/tutorial-vmware-hcx/select-compute-profile-source.png" alt-text="Screenshot that shows selecting the source compute profile." lightbox="media/tutorial-vmware-hcx/select-compute-profile-source.png":::
 

articles/azure-monitor/alerts/media/action-groups/action-group-runbook-add.png

@@ -14,8 +14,6 @@ In this article, you learn how to migrate a SQL Server Always On Availability Gr
 
 :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-architecture.png" alt-text="Diagram showing the architecture of Always On SQL Server for  Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/sql-always-on-architecture.png":::
 
-## Tested configurations
-
 Microsoft SQL Server (2019 and 2022) was tested with Windows Server (2019 and 2022) Data Center edition with the virtual machines deployed in the on-premises environment. Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
 
 ## Prerequisites
@@ -30,13 +28,14 @@ These are the prerequisites to migrating your SQL Server instance to Azure VMwar
 - Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
 Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
-VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments). 
 
-For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
+With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
+
+For any of the following, ExpressRoute connectivity is recommended for a migration:
 
 - Production environments
 - Workloads with large database sizes
-- Any case where there is a need to minimize downtime
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.
 
 Further downtime considerations are discussed in the next section.
 

articles/azure-monitor/alerts/media/action-groups/action-group-runbook-configure.png

@@ -24,8 +24,6 @@ However, you can overcome this limitation by performing the steps shown in this
 > [!NOTE]
 > This procedure requires a full shutdown of the cluster. Since the SQL Server service will be unavailable during the migration, plan accordingly for the downtime period.  
 
-## Tested configurations
-
 Microsoft SQL Server 2019 and 2022 were tested with Windows Server 2019 and 2022 Data Center edition with the virtual machines deployed in the on-premises environment. 
 Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware. 
 The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
@@ -41,16 +39,14 @@ The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware
 - Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
 Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
-VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments). 
 
-For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
+With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
+
+For any of the following, ExpressRoute connectivity is recommended for a migration:
 
 - Production environments
 - Workloads with large database sizes
-- Any case where there is a need to minimize downtime
-
-Further downtime considerations are discussed in the next section.
-
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.
 
 ## Downtime considerations
 

articles/azure-vmware/configure-vmware-hcx.md

@@ -22,6 +22,13 @@ In both cases, consider the size and criticality of the database being migrated.
 For this how-to procedure, we have validated VMware HCX vMotion.
 VMware HCX Cold Migration is also valid, but it requires a longer downtime period.
 
+This scenario was validated using the following editions and configurations:
+
+- Microsoft SQL Server (2019 and 2022)  
+- Windows Server (2019 and 2022) Data Center edition  
+- Windows Server and SQL Server were configured following best practices and recommendations from Microsoft and VMware.  
+- The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware vSAN running on Dell PowerEdge servers and Intel Optane P4800X SSD NVMe devices.
+
 :::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-standalone-cluster.png" alt-text="Diagram showing the architecture of Standalone SQL Server for  Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/migrated-sql-standalone-cluster.png"::: 
 
 ## Tested configurations
@@ -43,10 +50,17 @@ This scenario was validated using the following editions and configurations:
 - Ensure that all the network segments in use by the SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step in the process, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
 Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
+
 VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments). 
 
+
 For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
 
+For any of the following, ExpressRoute connectivity is recommended for a migration:
+
+- Production environments
+- Workloads with large database sizes
+- Scenarios in which there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.migration.  
 - Production environments
 - Workloads with large database sizes
 - Any case where there is a need to minimize downtime

articles/azure-vmware/migrate-sql-server-always-on-availability-group.md

@@ -130,7 +130,7 @@ To enable Trusted Access between Backup vault and AKS cluster, use the following
    az aks trustedaccess rolebinding create \
    -g $myResourceGroup \ 
    --cluster-name $myAKSCluster 
-   –n <randomRoleBindingName> \ 
+   -n <randomRoleBindingName> \ 
    --source-resource-id <vaultID> \ 
    --roles Microsoft.DataProtection/backupVaults/backup-operator   
    ```

articles/azure-vmware/migrate-sql-server-failover-cluster.md

@@ -481,8 +481,8 @@ You can remediate previously assigned tags and add new tags using an Azure Polic
 1. Trigger the remediation task:
 
     ```
-    az policy assignment update -n $POLICY_ASSIGNMENT
-    	--params param-values.json
+    az policy remediation create --resource-group $MANAGED_RESOURCE_GROUP --name myRemediation --policy-assignment $POLICY_ASSIGNMENT
+
     ```
 
 1. Allow the remediation task time to run and observe the tags being updated on the managed resource group and its resources.