move tested configs sections

Author: Whyte

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

@@ -14,6 +14,10 @@ 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
 
 These are the prerequisites to migrating your SQL Server instance to Azure VMware Solution.
@@ -30,7 +34,6 @@ However, due to the size of database workloads, VMware HCX over VPN is not recom
 ExpressRoute connectivity is recommended as more performant and reliable. 
 For Microsoft SQL Server standalone and non-production workloads this may be suitable, depending upon the size of the database, to migrate. 
 
-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.
 
 ## Downtime considerations
 

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

@@ -24,6 +24,12 @@ 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.
+
 ## Prerequisites
 
 - Review and record the storage and network configuration of every node in the cluster.
@@ -39,9 +45,6 @@ However, due to the size of database workloads it isn't recommended for Microsof
 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
 

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

@@ -24,6 +24,14 @@ VMware HCX Cold Migration is also valid, but it requires a longer downtime perio
 
 :::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
+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.+
+
 ## Prerequisites
 
 - Review and record the storage and network configuration of every node in the cluster.
@@ -42,14 +50,6 @@ For production environments, or workloads with large database sizes or where the
 
 Further downtime considerations are discussed in the next section.
 
-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.
-
-
 ## Downtime considerations
 
 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.