Merge pull request #250103 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/advisor/advisor-reference-reliability-recommendations.md

@@ -63,6 +63,12 @@ We recommend configuring the Azure Front Door customer certificate secret to ‘
 Learn more about [Front Door Profile - SwitchVersionBYOC (Switch Secret version to ‘Latest’ for the Azure Front Door customer certificate)](/azure/frontdoor/standard-premium/how-to-configure-https-custom-domain#certificate-renewal-and-changing-certificate-types).
 ## Compute
 
+### Migrate Virtual Machines to Availability Zones
+
+By migrating virtual machines to Availability Zones, you can ensure the isolation of your VMs from potential failures in other zones. With this, you can expect enhanced resiliency in your workload by avoiding downtime and business interruptions. 
+
+Learn more about [Availability Zones](../reliability/availability-zones-overview.md).
+
 ### Enable Backups on your Virtual Machines
 
 Enable backups for your virtual machines and secure your data

articles/azure-arc/data/limitations-managed-instance.md

@@ -34,7 +34,7 @@ This article describes limitations of Azure Arc-enabled SQL Managed Instance.
 
 - Transactional replication is currently not supported.
 - Log shipping is currently blocked.
-- Creating a database using SQL Server Management Studio does not work currently. Use the T-SQL command `CREATE DATABASE` to create databases.
+- All user databases need to be in a full recovery model because they participate in an always-on-availability group
 
 ## Roles and responsibilities
 

articles/azure-arc/servers/azcmagent-connect.md

@@ -20,19 +20,23 @@ azcmagent connect [authentication] --subscription-id [subscription] --resource-g
 Connect a server using the default login method (interactive browser or device code).
 
 ```
-azcmagent connect --subscription "Production" --resource-group "HybridServers" --location "eastus"
+azcmagent connect --subscription-id "Production" --resource-group "HybridServers" --location "eastus"
+```
+
+```
+azcmagent connect --subscription-id "Production" --resource-group "HybridServers" --location "eastus" --use-device-code
 ```
 
 Connect a server using a service principal.
 
 ```
-azcmagent connect --subscription "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee" --resource-group "HybridServers" --location "australiaeast" --service-principal-id "ID" --service-principal-secret "SECRET" --tenant-id "TENANT"
+azcmagent connect --subscription-id "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee" --resource-group "HybridServers" --location "australiaeast" --service-principal-id "ID" --service-principal-secret "SECRET" --tenant-id "TENANT"
 ```
 
 Connect a server using a private endpoint and device code login method.
 
 ```
-azcmagent connect --subscription "Production" --resource-group "HybridServers" --location "koreacentral" --use-device-code --private-link-scope "/subscriptions/.../Microsoft.HybridCompute/privateLinkScopes/ScopeName"
+azcmagent connect --subscription-id "Production" --resource-group "HybridServers" --location "koreacentral" --use-device-code --private-link-scope "/subscriptions/.../Microsoft.HybridCompute/privateLinkScopes/ScopeName"
 ```
 
 ## Authentication options

articles/azure-cache-for-redis/cache-how-to-premium-persistence.md

@@ -31,15 +31,15 @@ You have two options for persistence with Azure Cache for Redis: the _Redis data
 - _RDB persistence_ - When you use RDB persistence, Azure Cache for Redis persists a snapshot of your cache in a binary format. The snapshot is saved in an Azure Storage account. The configurable backup frequency determines how often to persist the snapshot. If a catastrophic event occurs that disables both the primary and replica cache, the cache is reconstructed automatically using the most recent snapshot. Learn more about the [advantages](https://redis.io/topics/persistence#rdb-advantages) and [disadvantages](https://redis.io/topics/persistence#rdb-disadvantages) of RDB persistence.
 - _AOF persistence_ - When you use AOF persistence, Azure Cache for Redis saves every write operation to a log. The log is saved at least once per second in an Azure Storage account. If a catastrophic event occurs that disables both the primary and replica caches, the cache is reconstructed automatically using the stored write operations. Learn more about the [advantages](https://redis.io/topics/persistence#aof-advantages) and [disadvantages](https://redis.io/topics/persistence#aof-disadvantages) of AOF persistence.
 
-Azure Cache for Redis persistence features are intended to be used to restore data automatically to the same cache after data loss. The RDB/AOF persisted data files can't be imported to a new cache. To move data across caches, use the _Import and Export_ feature. For more information, see [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md).
+Azure Cache for Redis persistence features are intended to be used to restore data automatically to the same cache after data loss. The RDB/AOF persisted data files can't be imported to a new cache or the existing cache. To move data across caches, use the _Import and Export_ feature. For more information, see [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md).
 
 To generate any backups of data that can be added to a new cache, you can write automated scripts using PowerShell or CLI that export data periodically.
 
 ## Prerequisites and limitations
 
 Persistence features are intended to be used to restore data to the same cache after data loss.
 
-- RDB/AOF persisted data files can't be imported to a new cache. Use the [Import/Export](cache-how-to-import-export-data.md) feature instead.
+- RDB/AOF persisted data files can't be imported to a new cache or the existing cache. Use the [Import/Export](cache-how-to-import-export-data.md) feature instead.
 - Persistence isn't supported with caches using [passive geo-replication](cache-how-to-geo-replication.md) or [active geo-replication](cache-how-to-active-geo-replication.md).
 - On the _Premium_ tier, AOF persistence isn't supported with [multiple replicas](cache-how-to-multi-replicas.md).
 - On the _Premium_ tier, data must be persisted to a storage account in the same region as the cache instance.

articles/azure-vmware/enable-sql-azure-hybrid-benefit.md

@@ -5,17 +5,18 @@ ms.author: jacobjaygbay
 description: This article shows you how to apply Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution to your Azure VMware Solution private cloud by configuring a placement policy.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 02/14/2023
+ms.date: 09/01/2023
 ---
 
 # Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution
 
-In this article, you’ll learn how to configure Azure Hybrid Benefit for SQL Server in an Azure VMware Solution private cloud by configuring a placement policy. The placement policy defines the hosts that are running SQL Server as well as the virtual machines on that host.  
+In this article, you’ll learn how to configure Azure Hybrid Benefit for SQL Server in an Azure VMware Solution private cloud by configuring a placement policy.
+The placement policy defines the hosts that are running SQL Server as well as the virtual machines on that host.  
 
 > [!IMPORTANT]
 > It is important to note that SQL Server benefits are applied at the host level.  
 
-For example, if each host in Azure VMware Solution has 36 cores and you intend to have 2 hosts run SQL Server then the Azure Hybrid Benefit will apply to 72 cores, irrespective of the number of SQL Server instances or other virtual machines are on that host. 
+For example, if each host in Azure VMware Solution has 36 cores and you intend to have 2 hosts run SQL Server then the Azure Hybrid Benefit will apply to 72 cores, regardless of the number of SQL Server instances or other virtual machines are on that host. 
 
 You can also choose to view a video tutorial for configuring Azure Hybrid Benefit for SQL Server in Azure VMware Solution [here](https://www.youtube.com/watch?v=vJIQ1K2KTa0).
 
@@ -28,12 +29,12 @@ You can also choose to view a video tutorial for configuring Azure Hybrid Benefi
 1. Fill in the required fields for creating the placement policy.
      1. **Name** – Select the name that identifies this policy.
      2. **Type** – Select the type of policy. This type must be a VM-Host affinity rule only.
-     3. **Azure hybrid benefit** – Select the checkbox to apply the SQL Azure hybrid benefit.
+     3. **Azure Hybrid Benefit** – Select the checkbox to apply the Azure Hybrid Benefit for SQL Server.
      4. **Cluster** – Select the correct cluster. The policy is scoped to host in this cluster only.
      5. **Enabled** – Select enabled to apply the policy immediately once created.
      :::image type="content" source="media/sql-azure-hybrid-benefit/create-placement-policy.png" alt-text="Diagram that shows how to create a host virtual machine placement policy using the host VM affinity.":::
 2. Select the hosts and VMs that will be applied to the VM-Host affinity policy.
-     1.	**Add Hosts** – Select the hosts that will be running SQL. When hosts are replaced, policies are re-created on the new hosts automatically.
+     1.	**Add Hosts** – Select the hosts that will be running SQL Server. When hosts are replaced, policies are re-created on the new hosts automatically.
      2.	**Add VMs** – Select the VMs that should run on the selected hosts.
      3. **Review and Create** the policy.
      :::image type="content" source="media/sql-azure-hybrid-benefit/select-policy-host.png" alt-text="Diagram that shows how to create a host virtual machine affinity.":::
@@ -46,8 +47,6 @@ By checking the Azure Hybrid Benefit checkbox in the configuration setting, you
 
 :::image type="content" source="media/sql-azure-hybrid-benefit/placement-policies.png" alt-text="Diagram that shows how to configure virtual machine placement policies."::: 
 
-## Next steps
+## More information
 
-[Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/)
-
-[Attach Azure NetApp Files datastores to Azure VMware Solution hosts](attach-azure-netapp-files-to-azure-vmware-solution-hosts.md) 
+[Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/)

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

@@ -8,9 +8,9 @@ ms.service: azure-vmware
 ms.date: 3/20/2023
 ms.custom: engagement-fy23
 ---
-# Migrate Microsoft SQL Server Always On cluster to Azure VMware Solution
+# Migrate a SQL Server Always On Availability Group to Azure VMware Solution
 
-In this article, you learn how to migrate Microsoft SQL Server Always On Cluster to Azure VMware Solution. For VMware HCX, you can follow the VMware vMotion migration procedure.
+In this article, you learn how to migrate a Microsoft SQL Server Always On Availability Group  to Azure VMware Solution. For VMware HCX, you can follow the VMware vMotion migration procedure.
 
 :::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":::
 
@@ -64,9 +64,9 @@ If the cluster uses a **File share witness** running on-premises, then the type
 
 For details about configuring and managing the quorum, see [Failover Clustering documentation](/windows-server/failover-clustering/manage-cluster-quorum). For information  about deployment of Cloud witness in Azure Blob Storage, see [Manage a cluster quorum for a Failover Cluster](/windows-server/failover-clustering/deploy-cloud-witness).
 
-## Migrate Microsoft SQL Server Always On cluster
+## Migrate SQL Server Always On Availability Group
 
-1. Access your Always On cluster with SQL Server Management Studio using administration credentials.
+1. Access your Always On Availability Group with SQL Server Management Studio using administration credentials.
    - Select your primary replica and open **Availability Group** **Properties**.
           :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-1.png" alt-text="Diagram showing Always On Availability Group properties." border="false" lightbox="media/sql-server-hybrid-benefit/sql-always-on-1.png":::
    - Change **Availability Mode** to **Asynchronous commit** only for the replica to be migrated.