Mike's fixes

Author: Ian Whyte

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](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).
 
-## 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.

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

@@ -9,11 +9,15 @@ ms.date: 6/20/2023
 ms.custom: engagement-fy23
 ---
 
-#  Migrate SQL Server Failover cluster to Azure VMware Solution
+#  Migrate a SQL Server Always On Failover Cluster Instance 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). 
+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. 
+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 Server Failover for Azure VMware Solution." border="false" lightbox="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png":::
 
@@ -24,23 +28,24 @@ VMware HCX doesn't support migrating virtual machines with SCSI controllers in p
 
 - Review and record the storage and network configuration of every node in the cluster.
 - Review and record the WSFC configuration.
-- Back up the database(s) being executed in the cluster.
-- Back up the cluster virtual machines. 
+- Back up the database or databases being executed in the cluster.
+- Back up the cluster virtual machines.
 - Remove all cluster node VMs from any Distributed Resource Scheduler (DRS) groups and rules they're part of.
 - 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.
 
 ## 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. 
+Downtime during a migration depends on 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.
@@ -94,19 +99,19 @@ For illustration purposes, in this document we're using a two-node cluster with
    - Set **SCSI Bus Sharing** from **Physical** to **None** in the virtual SCSI controllers used for the shared storage. Usually, these controllers are of VMware Paravirtual type.
 1. Edit the first node virtual machine settings. Set **SCSI Bus Sharing** from **Physical** to **None** in the SCSI controllers.
 
-1. From the vSphere Client,** go to the HCX plugin area. Under **Services**, select **Migration** > **Migrate**. 
+1. From the **vSphere Client**, go to the HCX plugin area. Under **Services**, select **Migration** > **Migrate**. 
    - Select the second node virtual machine.
    - Set the vSphere cluster in the remote private cloud that will run the migrated SQL cluster as the **Compute Container**.
    - Select the **vSAN Datastore** as remote storage.
    - Select a folder if you want to place the virtual machines in specific folder, this not mandatory but is recommended to separate the different workloads in your Azure VMware Solution private cloud.
    - Keep **Same format as source**.
    - Select **Cold migration** as **Migration profile**. 
    - In **Extended** **Options** select **Migrate Custom Attributes**.
-    - Verify that on-premises network segments have the correct remote stretched segment in Azure.
-   - Select **Validate** and ensure that all checks are completed with pass status. The most common error here will be one related to the storage configuration. Verify again that there are no SCSI controllers with physical sharing setting. 
+   - Verify that on-premises network segments have the correct remote stretched segment in Azure.
+   - Select **Validate** and ensure that all checks are completed with pass status. The most common error here is one related to the storage configuration. Verify again that there are no SCSI controllers with physical sharing setting. 
    - Select **Go** and the migration will initiate. 
 1. Repeat the same process for the first node.
-1. Access **Azure VMware Solution vSphere Client** and edit the first node settings and set back to physical SCSI Bus sharing the SCSI controller(s) managing the shared disks.
+1. Access **Azure VMware Solution vSphere Client** and edit the first node settings and set back to physical SCSI Bus sharing the SCSI controller or controllers managing the shared disks.
 
 1. Edit node 2 settings in **vSphere Client**.
    - Set SCSI Bus sharing back to physical in the SCSI controller managing shared storage.
@@ -128,7 +133,7 @@ For illustration purposes, in this document we're using a two-node cluster with
 1. Using the **SQL Server Management Studio** connect to the SQL Server cluster resource network name. Check the database is online and accessible.
 
 :::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 Server from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access them. 
 
 ## Next steps

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

@@ -9,7 +9,7 @@ ms.date: 3/20/2023
 ms.custom: engagement-fy23
 ---
 
-# Migrate Microsoft SQL Server Standalone to Azure VMware Solution
+# Migrate a SQL Server standalone instance to Azure VMware Solution
 
 In this article, you learn how to migrate Microsoft SQL Server Standalone to Azure VMware Solution. 
 
@@ -39,12 +39,12 @@ However, due to the size of database workloads, VMware HCX over VPN isn't recomm
 For Microsoft SQL Server Standalone and non-production workloads HCX over VPN can be suitable, depending on 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 Microsoft SQL Server have been configured following best practices and recommendations from Microsoft and VMware.
+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
 
-Downtime during a migration depends upon the size of the database to be migrated and the speed of the private network connection to Azure cloud.
+Downtime during a migration depends on the size of the database to be migrated and the speed of the private network connection to Azure cloud.
 Migration of the Microsoft SQL Server Standalone instance doesn't require database downtime since it will be done using the VMware HCX vMotion mechanism. 
 We recommend migrating during off-peak hours with a pre-approved change window.
 
@@ -53,13 +53,13 @@ This table indicates the estimated downtime for each Microsoft SQL Server topolo
 | **Scenario** | **Downtime expected** | **Notes** |
 |:---|:-----|:-----|
 | **Standalone instance** | Low | Migration is done using VMware vMotion, the DB is available during migration time, but it isn't recommended to commit any critical data during it. |
-| **Always-On Availability Group** | Low | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
-| **Failover Cluster Instance** | High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
+| **Always On Availability Group** | Low | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
+| **Always On Failover Cluster Instance** | High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
 
 ## Migrate Microsoft SQL Server Standalone
 
 1. Log into your on-premises **vCenter Server** and access the VMware HCX plugin. 
-1. Under **Services** select **Migration** > **Migrate**. 
+1. Under **Services** select **Migration** > **Migrate**.
    - Select the Microsoft SQL Server virtual machine.
    - Set the vSphere cluster in the remote private cloud of the migrated SQL Server cluster as the **Compute Container**.
    - Select the vSAN Datastore as remote storage.
@@ -69,7 +69,7 @@ This table indicates the estimated downtime for each Microsoft SQL Server topolo
    - In **Extended Options** select **Migrate Custom Attributes**.
    - Verify that on-premises network segments have the correct remote stretched segment in Azure VMware Solution.
    - Select **Validate** and ensure that all checks are completed with pass status. 
-   - Select **Go** to start the migration. 
+   - Select **Go** to start the migration.
 1. After the migration has completed, access the virtual machine using VMware Remote Console in the vSphere Client.
    - Verify the network configuration and check connectivity both with on-premises and Azure VMware Solution resources.
    - Using Microsoft SQL Server Management Studio verify you can access the database.  
@@ -78,7 +78,7 @@ This table indicates the estimated downtime for each Microsoft SQL Server topolo
 
 ## Next steps
 
-- [Enable SQL Azure hybrid benefit for Azure VMware Solution](enable-sql-azure-hybrid-benefit.md). 
+- [Enable SQL Azure Hybrid Benefit for 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)