Skip to content

Commit a81edd1

Browse files
authored
Refine configuration migration section and script example
Rephrased the introduction to the configuration migration section for clarity. Adjusted the formatting of the PowerShell script example for consistency. Signed-off-by: MJyot <[email protected]>
1 parent 83ddd4f commit a81edd1

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/application-gateway/migrate-v1-v2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ This article primarily helps with the configuration migration. Client traffic mi
4747
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
4848

4949
## Configuration migration
50-
This phase focuses on setting up the new V2 gateway with the settings from your existing V1 environment. We provide two Azure PowerShell scripts designed to facilitate the migration of configurations from V1 (Standard or WAF) to V2 (Standard_V2 or WAF_V2) gateways. These scripts help streamline the transition process by automating key deployment and configuration tasks.
50+
The configuration migration focuses on setting up the new V2 gateway with the settings from your existing V1 environment. We provide two Azure PowerShell scripts designed to facilitate the migration of configurations from V1 (Standard or WAF) to V2 (Standard_V2 or WAF_V2) gateways. These scripts help streamline the transition process by automating key deployment and configuration tasks.
5151

5252
## 1. Enhanced Cloning Script
5353
This is the new experience that offers an improved migration experience by:
@@ -310,12 +310,12 @@ Execute AzureAppGWClone.ps1 with the required parameters:
310310
```
311311
AzureAppGWIPMigrate.ps1
312312
-v1resourceId <V1 application gateway Resource ID>
313-
-v2resourceId <V2 application gateway Resource ID>
313+
-v2resourceId <V2 application gateway Resource ID>
314314
```
315315
**Example**
316316
```azurepowershell
317317
./AzureAppGWIPMigrate.ps1 `
318-
-v1resourceId /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/MyResourceGroup/providers/Microsoft.Network/applicationGateways/myv1appgateway `
318+
-v1resourceId /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/MyResourceGroup/providers/Microsoft.Network/applicationGateways/myv1appgateway `
319319
-v2resourceId /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/MyResourceGroup/providers/Microsoft.Network/applicationGateways/myv2appgateway `
320320
```
321321
Once the IP swap is complete, customers should check control and data plane operations on the V2 gateway. All control plane actions except Delete will be disabled on the V1 gateway.,

0 commit comments

Comments
 (0)