edit pass: migrating-to-application-gateway-v2

Author: ShawnJackson

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

@@ -56,7 +56,7 @@ This article focuses on the configuration stage of migration. Migration of clien
 > [!NOTE]
 > Application Gateway V2 includes [customer-controlled backend TLS relaxation](configuration-http-settings.md#backend-https-validation-settings), a capability that streamlines backend certificate validation during migration. You can use this feature to temporarily relax TLS checks by skipping the certificate chain, skipping expiry validation, or overriding Server Name Indication (SNI) validation. This action aligns behavior with what's already permitted in V1.
 >
-> When the [enhanced migration script](migrate-v1-v2.md#enhanced-cloning-script---recommended) runs, it enables these relaxation settings by default for HTTPS backends to prevent disruptions caused by the stricter certificate enforcement in V2. After you complete the migration, you can upload the appropriate trusted root certificates and disable backend TLS relaxation to align with the recommended security posture for V2.
+> When the [enhanced migration script](#enhanced-cloning-script-recommended) runs, it enables these relaxation settings by default for HTTPS backends to prevent disruptions caused by the stricter certificate enforcement in V2. After you complete the migration, you can upload the appropriate trusted root certificates and disable backend TLS relaxation to align with the recommended security posture for V2.
 
 [!INCLUDE [cloud-shell-try-it.md](~/reusable-content/ce-skilling/azure/includes/cloud-shell-try-it.md)]
 
@@ -164,7 +164,7 @@ Private Application Gateway deployments must have subnet delegation configured t
 
 - If you have FIPS mode enabled for your V1 gateway, it isn't migrated to your new V2 gateway.
 
-- Web Application Firewall V2 is configured to use CRS 3.0 by default. Because CRS 3.0 is on the path to deprecation, upgrade to the latest rule set (DRS 2.2) after migration. For more information, refer to [Web Application Firewall DRS and CRS rule groups and rules](../web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md).
+- Web Application Firewall V2 is configured to use Core Rule Set (CRS) 3.0 by default. Because CRS 3.0 is on the path to deprecation, upgrade to the latest rule set after migration: Default Rule Set (DRS) 2.2. For more information, see [Web Application Firewall DRS and CRS rule groups and rules](../web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md).
 
 > [!NOTE]
 > During migration, don't attempt any other operation on the V1 gateway or any associated resources.
@@ -323,10 +323,10 @@ The legacy script takes the following parameters:
 
 - The Web Application Firewall V2 instance is created in the old Web Application Firewall configuration mode. Migration to the Web Application Firewall policy is required.
 
-- Web Application Firewall V2 is configured to use CRS 3.0 by default. Because CRS 3.0 is on the path to deprecation, upgrade to the latest rule set (DRS 2.2) after migration. For more information, refer to [CRS and DRS rule groups and rules](../web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md).
+- Web Application Firewall V2 is configured to use CRS 3.0 by default. Because CRS 3.0 is on the path to deprecation, upgrade to the latest rule set (DRS 2.2) after migration. For more information, see [CRS and DRS rule groups and rules](../web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md).
 
 > [!NOTE]
-> Application Gateway V2 supports NTLM and Kerberos passthrough authentication. For more information, refer to [Dedicated backend connection](configuration-http-settings.md#dedicated-backend-connection).
+> Application Gateway V2 supports NTLM and Kerberos passthrough authentication. For more information, see [Dedicated backend connection](configuration-http-settings.md#dedicated-backend-connection).
 
 ## Installing the script
 
@@ -408,7 +408,7 @@ This script requires the following mandatory parameters:
 - `v1resourceId`. The resource ID of the V1 gateway whose public IP will be reserved and associated with V2.
 - `v2resourceId`. The resource ID of the V2 gateway to which the V1 public IP will be assigned. You can create the V2 gateway manually or by using any one of the cloning scripts.
 
-After you download and [install the script](../application-gateway/migrate-v1-v2.md#installing-the-script), run `AzureAppGWIPMigrate.ps1` with the required parameters:
+After you download and [install the script](#installing-the-script), run `AzureAppGWIPMigrate.ps1` with the required parameters:
 
 ```azurepowershell
    ./AzureAppGWIPMigrate.ps1
@@ -480,11 +480,11 @@ The scenarios in the following table are examples for illustration purposes only
 | Standard Large | 467.2 | 179.58 | For these variants, in most cases, moving to a V2 gateway can provide a better price benefit compared to V1. |
 | Web Application Firewall Large | 654.08 | 262.8 | Same as for Standard Large. |
 
-For further concerns about the pricing, work with your account manager or get in touch with our support team for assistance.
+For further concerns about the pricing, work with your customer success account manager (CSAM) or get in touch with our support team for assistance.
 
 ## Common questions
 
-For answers to common questions about migration, see [Frequently asked questions about Application Gateway V1 retirement](./retirement-faq.md#faq-on-v1-to-v2-migration).
+For answers to common questions about migration, see [Frequently asked questions about Application Gateway V1 retirement](./retirement-faq.md#common-questions-about-migration-from-v1-to-v2).
 
 ## Related content
 

articles/application-gateway/retirement-faq.md

@@ -12,7 +12,7 @@ ms.author: mbender
 ---
 # Frequently asked questions about Application Gateway V1 retirement
 
-On April 28, 2023, Microsoft announced that Application Gateway V1 is retiring on *April 28, 2026*. If you're still using V1 SKU resources, be sure to plan and complete your migration to V2 before this date to avoid service disruptions.
+On April 28, 2023, Microsoft announced that Application Gateway V1 is retiring on *April 28, 2026*. If you're still using V1 resources, be sure to plan and complete your migration to V2 before this date to avoid service disruptions.
 
 This article answers commonly asked questions about the V1 retirement timeline, what to expect after retirement, and how to migrate from V1 to V2. For migration guidance, see [Migrate Azure Application Gateway and Web Application Firewall from V1 to V2](./migrate-v1-v2.md).
 
@@ -103,7 +103,7 @@ No, the script doesn't replicate this configuration for V2. You must add the log
 
 ### Does the script support certificates uploaded to Azure Key Vault?
 
-Yes, you can download the certificate from Azure Key Vault and provide it as input to the migration script. The [enhanced cloning script](./migrate-v1-v2.md#enhanced-cloning-script---recommended) automatically copies all the TLS/SSL certificates from V1 to the newly created V2 gateway.
+Yes, you can download the certificate from Azure Key Vault and provide it as input to the migration script. The [enhanced cloning script](./migrate-v1-v2.md#enhanced-cloning-script-recommended) automatically copies all the TLS/SSL certificates from V1 to the newly created V2 gateway.
 
 ### I ran into some problems with the migration. How can I get help?
 

articles/application-gateway/v1-retirement.md

@@ -47,7 +47,7 @@ Complete the migration as soon as possible to prevent business impact and to tak
 
   > [!VIDEO 7ed01e33-80a9-4daa-9322-e771f963a2fe]
 
-- For answers to frequently asked questions, see [FAQ on V1 to V2 migration](./retirement-faq.md#faq-on-v1-to-v2-migration).
+- For answers to frequently asked questions, see [FAQ on V1 to V2 migration](./retirement-faq.md).
 
 - For the announcement about the capabilities of V2, see the blog post [Taking advantage of the new Azure Application Gateway V2](https://azure.microsoft.com/blog/taking-advantage-of-the-new-azure-application-gateway-v2/).