formatting edits

Author: asudbring

articles/virtual-network/move-across-regions-vnet-portal.md

@@ -85,7 +85,7 @@ The following steps show how to prepare the virtual network for the move using a
 
     * **Address Space** - The address space of the VNET can be altered in the template before saving by modifying the **resources** > **addressSpace** section and changing the **addressPrefixes** property in the **template.json** file:
 
-            ```json
+        ```json
                 "resources": [
                             {
                                 "type": "Microsoft.Network/virtualNetworks",
@@ -100,11 +100,11 @@ The following steps show how to prepare the virtual network for the move using a
                                             "10.0.0.0/16"
                                         ]
                                     },
-            ```
+        ```
 
     * **Subnet** - The subnet name and the subnet address space can be changed or added to by modifying the **subnets** section of the **template.json** file. The name of the subnet can be changed by altering the **name** property in the **template.json** file.  The subnet address space can be changed by altering the **addressPrefix** property in the **template.json** file:
 
-            ```json
+        ```json
                  "subnets": [
                         {
                             "name": "subnet-1",
@@ -130,11 +130,11 @@ The following steps show how to prepare the virtual network for the move using a
                             }
                         }
                     ],
-            ```
+        ```
 
     In the **template.json** file, to change the address prefix, it must be edited in two places, the section listed above and the **type** section listed below.  Change the **addressPrefix** property to match the one above:
 
-            ```json
+    ```json
                  "type": "Microsoft.Network/virtualNetworks/subnets",
                                 "apiVersion": "2019-06-01",
                                 "name": "[concat(parameters('virtualNetworks_myVNET1_name'), '/GatewaySubnet')]",
@@ -166,7 +166,7 @@ The following steps show how to prepare the virtual network for the move using a
                                 }
                             }
                         ]
-            ```
+    ```
 
 13. Click **Save** in the online editor.
 

articles/virtual-network/move-across-regions-vnet-powershell.md

@@ -156,6 +156,40 @@ The following steps show you how to prepare the virtual network for the move usi
 
          In the **\<resource-group-name>.json** file, to change the address prefix, it must be edited in two places, the section listed above and the **type** section listed below.  Change the **addressPrefix** property to match the one above:
 
+        ```json
+         "type": "Microsoft.Network/virtualNetworks/subnets",
+           "apiVersion": "2019-06-01",
+           "name": "[concat(parameters('virtualNetworks_myVNET1_name'), '/GatewaySubnet')]",
+              "dependsOn": [
+                 "[resourceId('Microsoft.Network/virtualNetworks', parameters('virtualNetworks_myVNET1_name'))]"
+                   ],
+              "properties": {
+                 "provisioningState": "Succeeded",
+                 "addressPrefix": "10.0.1.0/29",
+                 "serviceEndpoints": [],
+                 "delegations": [],
+                 "privateEndpointNetworkPolicies": "Enabled",
+                 "privateLinkServiceNetworkPolicies": "Enabled"
+                  }
+                 },
+                  {
+                  "type": "Microsoft.Network/virtualNetworks/subnets",
+                  "apiVersion": "2019-06-01",
+                  "name": "[concat(parameters('virtualNetworks_myVNET1_name'), '/subnet-1')]",
+                     "dependsOn": [
+                        "[resourceId('Microsoft.Network/virtualNetworks', parameters('virtualNetworks_myVNET1_name'))]"
+                          ],
+                     "properties": {
+                        "provisioningState": "Succeeded",
+                        "addressPrefix": "10.0.0.0/24",
+                        "delegations": [],
+                        "privateEndpointNetworkPolicies": "Enabled",
+                        "privateLinkServiceNetworkPolicies": "Enabled"
+                         }
+                  }
+         ]
+        ```
+
 9.  Save the **\<resource-group-name>.json** file.
 
 10. Create a resource group in the target region for the target VNET to be deployed using [New-AzResourceGroup](https://docs.microsoft.com/powershell/module/az.resources/new-azresourcegroup?view=azps-2.6.0)