Merge pull request #297640 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: v-alje

articles/azure-vmware/configure-azure-elastic-san.md

@@ -92,7 +92,7 @@ Start by providing an IP block for deploying external storage. Navigate to the *
 After you provide an External storage address block, you need to connect your private cloud express route with the private endpoint(s) you set up for your Elastic SAN volume group(s). To learn how to establish these connections, see [Configure networking for your VMware private cloud in Azure](../azure-vmware/tutorial-configure-networking.md). 
 
 > [!NOTE]
-> Connection to Elastic SAN from Azure VMWare Solution happens via private endpoints to provide the highest network security. Since your private cloud connects to Elastic SAN in Azure through an ExpressRoute virtual network gateway, you may experience intermittent connectivity issues during [gateway maintenance](/azure/expressroute/expressroute-about-virtual-network-gateways). 
+> Connection to Elastic SAN from Azure VMware Solution happens via private endpoints to provide the highest network security. Since your private cloud connects to Elastic SAN in Azure through an ExpressRoute virtual network gateway, you may experience intermittent connectivity issues during [gateway maintenance](/azure/expressroute/expressroute-about-virtual-network-gateways). 
 > These connectivity issues aren't expected to impact the availability of the datastore backed by Elastic SAN as the connection will be re-established within seconds. The potential impact from gateway maintenance is covered under the [Service Level Agreement](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) for ExpressRoute virtual network gateways and private endpoints.
 ## Add an Elastic SAN volume as a datastore
 

articles/azure-vmware/configure-identity-source-vcenter.md

@@ -38,7 +38,7 @@ In this article, you learn how to:
 
 - Ensure that your Windows Server Active Directory network is connected to your Azure VMware Solution private cloud.
 
-- Windows Server Active Directory authentication with LDAPS, see [Configure LDAPS within Azure Vmware Solution](https://techcommunity.microsoft.com/blog/fasttrackforazureblog/configure-ldaps-within-azure-vmware-solution/3725759).
+- Windows Server Active Directory authentication with LDAPS, see [Configure LDAPS within Azure VMware Solution](https://techcommunity.microsoft.com/blog/fasttrackforazureblog/configure-ldaps-within-azure-vmware-solution/3725759).
 
 - Configure DNS resolution for Azure VMware Solution to your on-premises Windows Server Active Directory. Set up a DNS forwarder in the Azure portal. For more information, see [Configure a DNS forwarder for Azure VMware Solution](configure-dns-azure-vmware-solution.md).
 

articles/backup/manage-backup-vault.md

@@ -161,7 +161,7 @@ The Cross Region Restore option allows you to restore data in a secondary Azur
 Some datasources of Backup vault support restore to a subscription different from that of the source machine. Cross Subscription Restore (CSR) is enabled for existing vaults by default, and you can use it if supported for the intended datasource.
 
 >[!Note]
->The feature is currently not supported for Azure Kubernetes Service (AKS) and Azure VMWare Service (AVS) backup.
+>The feature is currently not supported for Azure Kubernetes Service (AKS) and Azure VMware Service (AVS) backup.
 
 To do Cross Subscription Restore, follow these steps: