Merge branch 'reloc-vmss' of https://github.com/anaharris-ms/azure-docs-pr into reloc-vmss

Author: anaharris-ms

articles/operational-excellence/relocation-virtual-machine-scale-sets.md

@@ -15,15 +15,15 @@ ms.custom:
 
 # Relocate Azure Virtual Machine Scale Sets to another region
 
-This article covers the recommended approach, guidelines and practices for relocating Virtual Machine Scale Sets to another region.
+This article covers the recommended approach, guidelines, and practices for relocating Virtual Machine Scale Sets to another region.
 
 ## Prerequisites
 
-Before you begin, ensure that you have the following:
+Before you begin, ensure that you have the following prerequisites:
 
 - If the source VM supports availability zones, then the target region must also support availability zones. To see which regions support availability zones, see [Azure regions with availability zone support](../reliability/availability-zones-service-support.md#azure-services-with-availability-zone-support).
 
-- The subscription in the destination region needs enough quota to create the resources. If you have exceeded the quota, you can request an increase. For more information, see [Azure subscription and service limits, quotas, and constraints](..//azure-resource-manager/management/azure-subscription-service-limits.md).
+- The subscription in the destination region needs enough quota to create the resources. If you exceeded the quota, request an increase. For more information, see [Azure subscription and service limits, quotas, and constraints](..//azure-resource-manager/management/azure-subscription-service-limits.md).
 
 - Consolidate all the associated extensions from source Virtual Machine Scale Set, as some need to be reconfigured after relocation.
 
@@ -38,28 +38,28 @@ Before you begin, ensure that you have the following:
     - [Key Vault](./relocation-key-vault.md)
     - [Proximity Placement Group](/azure/virtual-machine-scale-sets/proximity-placement-groups)
     - Public IP address
-    - [Load Balancer](../load-balancer/move-across-regions-external-load-balancer-portal.md). 
+    - [Load Balancer](../load-balancer/move-across-regions-external-load-balancer-portal.md)
     - [Virtual Network](./relocation-virtual-network.md)
 
-- Ensure that you have have Network Contributor role or higher in order to configure and deploy a Load Balancer template in another region.
+- Ensure that you have a Network Contributor role or higher in order to configure and deploy a Load Balancer template in another region.
 
-- Identify the networking layout of the solution in the source region including NSGs, Public IPs, VNet address spaces, etc.
+- Identify the networking layout of the solution in the source region, such as NSGs, Public IPs, VNet address spaces, and more.
 
 
 
 ## Prepare
 
-In this section, follow the steps below to prepare for relocating a Virtual Machine Scale Set to another region.
+In this section, follow the instructions to prepare for relocating a Virtual Machine Scale Set to another region.
 
 
 1. Locate the image reference used by the source Virtual Machine Scale Set and replicate it to the Image Gallery in the target region.
 
     :::image type="content" source="media\relocation\virtual-machine-scale-sets\image-replication.png" alt-text="Screenshot showing how to locate image of virtual machine.":::
 
-1. Relocate Load balancer, along with the public IP by doing one of the following methods:
+1. Relocate the Load Balancer, along with the public IP by doing one of the following methods:
 
     - *Resource Mover*. Associate Load Balancer with public IP in the source region to the target region. For more information, see [Move resources across regions (from resource group) with Azure Resource Mover](../resource-mover/move-region-within-resource-group.md).
-    - *Explort Template*. Relocate the Load balancer along with public IP to the target region using the export template option. For information on how to do this, see [Move an external load balancer to another region using the Azure portal](../load-balancer/move-across-regions-external-load-balancer-portal.md).
+    - *Export Template*. Relocate the Load Balancer along with public IP to the target region using the export template option. For information on how to do this, see [Move an external load balancer to another region using the Azure portal](../load-balancer/move-across-regions-external-load-balancer-portal.md).
 
     >[!IMPORTANT]
     > Because public IPs are a regional resource, Azure Resource Mover re-creates Load Balancer at the target region with a new public IP address. 
@@ -70,19 +70,18 @@ In this section, follow the steps below to prepare for relocating a Virtual Mach
 
 1. Export the source Virtual Machine Scale Set template from Azure portal:
 
-    1. In the [Azure portal](https://portal.azure.com), navigate to your source Virtual Machine Scale Set .
+    1. In the [Azure portal](https://portal.azure.com), navigate to your source Virtual Machine Scale Set.
     1. In the menu, under **Automation**, select **Export template** > **Download**.
-    1. Locate the .zip file that you downloaded from the portal, and unzip that file to a folder of your choice.
+    1. Locate the .zip file that you downloaded from the portal, and unzip that file to a folder of your choice. This zip file contains the .json files that include the template and scripts to deploy the template.
 
-       This zip file contains the .json files that include the template and scripts to deploy the template.
 
 1. Edit the template:
 
     1. Remove associated resources if they’re present in the template, such as Log Analytics Workspace in the **Monitoring** section.
 
     1. Make any necessary changes to the template, such as updating all occurrences of the name and the location for the relocated source Virtual Machine Scale Set.
 
-    1. Update the parameter file with the below inputs:
+    1. Update the parameter file with these inputs:
         - Source Virtual Machine Scale set `name`.
         - Image Gallery `Resource id`.
         - Virtual network `subnet Id`. Also, make the necessary ARM code changes to the subnet section so that it can call the Virtual Network `subnet Id`.
@@ -101,12 +100,12 @@ In this section, follow the steps below to relocate a Virtual Machine Scale Set
 
 When the relocation is complete, validate the Virtual Machine Scale Set in the target region by performing the following steps:
 
- - Virtual Machine Scale Set does not keep the same IP after relocation to new target location. However, make sure to validate the private IP configuration.
+ - Virtual Machine Scale Set doesn't keep the same IP after relocation to new target location. However, make sure to validate the private IP configuration.
 
- - Run a smoke test and integration test (either through a script or manually) to validate that all configurations and dependent resources have been properly linked and all configured data are accessible.
+ - Run a scripted or manual smoke test and integration test to validate that all configurations and dependent resources have been properly linked and all configured data are accessible.
 
 - Validate Virtual Machine Scale Set components and integration.
 
 ## Related content
 
-- To move registry resources to a new resource group either in the same subscription or a [new subscription], see [Move Azure resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).
+- To move registry resources to a new resource group either in the same subscription or a new subscription, see [Move Azure resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).