MW fixes

Author: Ian Whyte

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

@@ -1,8 +1,8 @@
 ---
-title: Enable SQL Azure Hybrid Benefit for SQL Server in Azure VMware Solution
+title: Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution
 author: jjaygbay1
 ms.author: jacobjaygbay
-description: This article shows you how to apply SQL Azure hybrid benefits to your Azure VMware Solution private cloud by configuring a placement policy.
+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

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

@@ -10,7 +10,7 @@ ms.custom: engagement-fy23
 ---
 # Migrate Microsoft SQL Server Always On cluster 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 Microsoft SQL Server Always On Cluster 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":::
 
@@ -20,7 +20,7 @@ These are the prerequisites to migrating your SQL Server instance to Azure VMwar
 
 - Review and record the storage and network configuration of every node in the cluster.
 - Backup the full database.
-- Backup the virtual machine running the Microsoft SQL Server instance. 
+- Backup the virtual machine running the Microsoft SQL Server instance.
 - Remove the virtual machine from any VMware vSphere Distributed Resource Scheduler (DRS) groups and rules.
 - VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more information on how to configure HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
 - Ensure that all the network segments in use by the Microsoft SQL Server are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
@@ -59,7 +59,7 @@ If the cluster uses a **File share witness** running on-premises, then the type
 - **Datacenter Exit**: For this scenario, there are two options. In both options, you can maintain the file share witness on-premises during the migration in case you need to do rollback during the process.
   - Deploy a new **File share witness** in your Azure VMware Solution private cloud. 
   - Deploy a **Cloud witness** running in Azure Blob Storage in the same region as the Azure VMware Solution private cloud. 
-- **Disaster Recovery and Business Continuity**: For a disaster recovery scenario, the best and most reliable option is to create a **Cloud Witness** running in Azure Storage. 
+- **Disaster Recovery and Business Continuity**: For a disaster recovery scenario, the best and most reliable option is to create a **Cloud Witness** running in Azure Storage.
 - **Application Modernization**: For this use case, the best option is to deploy a **Cloud Witness**.
 
 For details about configuring and managing the quorum, see [Failover Clustering documentation](https://learn.microsoft.com/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](https://learn.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness).
@@ -74,7 +74,7 @@ For details about configuring and managing the quorum, see [Failover Clustering
 1. Access the on-premises vCenter Server and proceed to HCX area.
 1. Under **Services** select **Migration** > **Migrate**. 
    - Select one virtual machine running the secondary replica of the database the is going to be migrated.
-   - Set the vSphere cluster in the remote private cloud to run the migrated SQL cluster as the **Compute Container**.
+   - Set the vSphere cluster in the remote private cloud to run the migrated SQL Server cluster as the **Compute Container**.
    - Select the **vSAN Datastore** as remote storage.
    - Select a folder. This not mandatory, but is recommended to separate the different workloads in your Azure VMware Solution private cloud.
    - Keep **Same format as source**.

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

@@ -1,6 +1,6 @@
 ---
-title: Migrate SQL Server failover cluster to Azure VMware Solution
-description: Learn how to migrate SQL Server failover cluster to Azure VMware Solution
+title: Migrate SQL Server Failover cluster to Azure VMware Solution
+description: Learn how to migrate SQL Server Failover cluster to Azure VMware Solution
 author: jjaygbay1
 ms.author: jacobjaygbay
 ms.topic: how-to
@@ -9,13 +9,13 @@ ms.date: 6/20/2023
 ms.custom: engagement-fy23
 ---
 
-#  Migrate SQL Server failover cluster to Azure VMware Solution
+#  Migrate SQL Server Failover cluster to Azure VMware Solution
 
 In this article, you'll learn how to migrate a Microsoft SQL Server Failover cluster instance to Azure VMware Solution. Currently Azure VMware Solution service doesn't support VMware Hybrid Linked Mode to connect an on-premises vCenter Server with one running in Azure VMware Solution. Due to this constraint, this process requires the use of VMware HCX for the migration. For more details about configuring HCX, see [Install and activate VMware HCX in Azure VMware Solution](install-vmware-hcx.md). 
 
 VMware HCX doesn't support migrating virtual machines with SCSI controllers in physical sharing mode attached to a virtual machine. However, you can overcome this limitation by performing the steps shown in this procedure and by using VMware HCX Cold Migration to move the different virtual machines that make up the cluster. 
 
-:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png" alt-text="Diagram showing the architecture of SQL failover server for Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png":::
+:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png" alt-text="Diagram showing the architecture of SQL Server Failover for Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png":::
 
 > [!NOTE]
 > This procedure requires a full shutdown of the cluster. Since the Microsoft SQL Server service will be unavailable during the migration, plan accordingly for the downtime period.  
@@ -30,13 +30,18 @@ VMware HCX doesn't support migrating virtual machines with SCSI controllers in p
 - VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more details about installing VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
 - Ensure that all the network segments in use by the Microsoft SQL Server are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
 
-VMware HCX over VPN is supported in Azure VMware Solution for workload migration. However, due to the size of database workloads it isn't recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always-On migrations, especially for production workloads. ExpressRoute connectivity is recommended as more performant and reliable. For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate. 
+VMware HCX over VPN is supported in Azure VMware Solution for workload migration. 
+However, due to the size of database workloads it isn't recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always On migrations, especially for production workloads. 
+ExpressRoute connectivity is recommended as more performant and reliable. For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate. 
 
-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.
+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.
 
 ## Downtime considerations
 
-Predicting downtime during a migration will depend upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. Migration of SQL Server Failover Cluster Instances Always On to Azure VMware Solution requires a full downtime of the database and all cluster nodes, however you should plan for the migration to be executed during off-peak hours with an approved change window.
+Predicting downtime during a migration will depend upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. 
+Migration of SQL Server Failover Cluster Instances Always On to Azure VMware Solution requires a full downtime of the database and all cluster nodes, however you should plan for the migration to be executed during off-peak hours with an approved change window.
 
 The table below indicates the downtime for each Microsoft SQL Server topology.
 
@@ -124,11 +129,11 @@ For illustration purposes, in this document we're using a two-node cluster with
 
 :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-5.png" alt-text="Diagram showing a verification of SQL Server Management Studio connection  to the migrated cluster instance database." border="false" lightbox="media/sql-server-hybrid-benefit/sql-failover-5.png":::
 
-Finally, check the connectivity to SQL from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access them. 
+Finally, check the connectivity to SQL Server from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access them. 
 
 ## Next steps
 
-- [Enable SQL Azure hybrid benefit for Azure VMware Solution](enable-sql-azure-hybrid-benefit.md). 
+- [Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution](enable-sql-azure-hybrid-benefit.md). 
 - [Create a placement policy in Azure VMware Solution](create-placement-policy.md)  
 - [Windows Server Failover Clustering Documentation](https://learn.microsoft.com/windows-server/failover-clustering/failover-clustering-overview)
 - [Microsoft SQL Server 2019 Documentation](https://learn.microsoft.com/sql/sql-server/?view=sql-server-ver15)