add feedback

Author: greg-lindsay

articles/application-gateway/overview-v2.md

@@ -19,7 +19,7 @@ Application Gateway v2 is the latest version of Application Gateway. It provides
 
 ## Key capabilities
 
-The new v2 SKU includes the following enhancements:
+The v2 SKU includes the following enhancements:
 
 - **TCP/TLS proxy (Preview)**: Azure Application Gateway now also supports Layer 4 (TCP protocol) and TLS (Transport Layer Security) proxying. This feature is currently in public preview. For more information, see [Application Gateway TCP/TLS proxy overview](tcp-tls-proxy-overview.md).
 - **Autoscaling**: Application Gateway or WAF deployments under the autoscaling SKU can scale out or in based on changing traffic load patterns. Autoscaling also removes the requirement to choose a deployment size or instance count during provisioning. This SKU offers true elasticity. In the Standard_v2 and WAF_v2 SKU, Application Gateway can operate both in fixed capacity (autoscaling disabled) and in autoscaling enabled mode. Fixed capacity mode is useful for scenarios with consistent and predictable workloads. Autoscaling mode is beneficial in applications that see variance in application traffic.
@@ -53,9 +53,11 @@ The following table displays a comparison between Basic and Standard_v2.
 | Reliability              | SLA                                      | 99.9           | 99.95             |
 | Functionality - basic    | HTTP/HTTP2/HTTPS<br>Websocket<br>Public/Private IP<br>Cookie Affinity<br>Path-based affinity<br>Wildcard<br>Multisite<br>KeyVault<br>AKS (via AGIC)<br>Zone | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br> | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;|
 | Functionality - advanced | URL rewrite<br>mTLS<br>Private Link<br>Private-only<sup>1</sup><br>TCP/TLS Proxy |  | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; |
-| Scale                    | Max. connections per second<br>Number of listeners<br>Number of backend pools<br>Number of backend servers per pool<br>Number of rules | 200<br>5<br>5<br>5<br>5  | 1250<br>100<br>100<br>1200<br>400 |
+| Scale                    | Max. connections per second<br>Number of listeners<br>Number of backend pools<br>Number of backend servers per pool<br>Number of rules | 200<br>5<br>5<br>5<br>5  | 62500<sup>1</sup><br>100<br>100<br>1200<br>400 |
 | Capacity Unit            | Connections per second per compute unit<br>Throughput<br>Persistent new connections  | 10<br>2.22 Mbps<br>2500 | 50<br>2.22 Mbps<br>2500 |
 
+<sup>1</sup>Estimated based on using an RSA 2048-bit key TLS certificate.
+
 ## Pricing
 
 With the v2 SKU, consumption drives the pricing model and is no longer attached to instance counts or sizes. To learn more, see [Understanding pricing](understanding-pricing.md).

articles/application-gateway/quick-create-bicep.md

@@ -5,15 +5,15 @@ description: In this quickstart, you learn how to use Bicep to create an Azure A
 services: application-gateway
 author: greg-lindsay
 ms.author: greglin
-ms.date: 02/28/2024
+ms.date: 04/18/2024
 ms.topic: quickstart
 ms.service: application-gateway
 ms.custom: mvc, subject-armqs, mode-arm, devx-track-bicep
 ---
 
 # Quickstart: Direct web traffic with Azure Application Gateway - Bicep
 
-In this quickstart, you use Bicep to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly.
+In this quickstart, you use Bicep to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly. The Standard v2 SKU is used in this example.
 
 [!INCLUDE [About Bicep](../../includes/resource-manager-quickstart-bicep-introduction.md)]
 
@@ -27,13 +27,13 @@ In this quickstart, you use Bicep to create an Azure Application Gateway. Then y
 
 This Bicep file creates a simple setup with a public frontend IP address, a basic listener to host a single site on the application gateway, a basic request routing rule, and two virtual machines in the backend pool.
 
+> [!TIP]
+> You can modify values of the `Name` and `Tier` parameters under `resource\applicationGateWay\properties\sku` to use a different SKU. For example: `Basic`.
+
 The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/ag-docs-qs/)
 
 :::code language="bicep" source="~/quickstart-templates/demos/ag-docs-qs/main.bicep":::
 
-> [!TIP]
-> You can modify values of the `Name` and `Tier` parameters under `resource\applicationGateWay\properties\sku` to use a different SKU. For example: `Basic`.
-
 Multiple Azure resources are defined in the Bicep file:
 
 - [**Microsoft.Network/applicationgateways**](/azure/templates/microsoft.network/applicationgateways)

articles/application-gateway/quick-create-cli.md

@@ -145,6 +145,8 @@ done
 
 Create an application gateway using `az network application-gateway create`. When you create an application gateway with the Azure CLI, you specify configuration information, such as capacity, SKU (for example: `Basic`), and HTTP settings. Azure then adds the private IP addresses of the network interfaces as servers in the backend pool of the application gateway.
 
+The Standard v2 SKU is used in this example.
+
 ```azurecli-interactive
 address1=$(az network nic show --name myNic1 --resource-group myResourceGroupAG | grep "\"privateIPAddress\":" | grep -oE '[^ ]+$' | tr -d '",')
 address2=$(az network nic show --name myNic2 --resource-group myResourceGroupAG | grep "\"privateIPAddress\":" | grep -oE '[^ ]+$' | tr -d '",')

articles/application-gateway/quick-create-portal.md

@@ -29,7 +29,7 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
 
 ## Create an application gateway
 
-Create the application gateway using the tabs on the **Create application gateway** page. The Standard v2 SKU is used. To create a Basic SKU using the Azure portal, see [Deploy Application Gateway basic (Preview)](deploy-basic-portal.md)
+Create the application gateway using the tabs on the **Create application gateway** page. The Standard v2 SKU is used in this example. To create a Basic SKU using the Azure portal, see [Deploy Application Gateway basic (Preview)](deploy-basic-portal.md)
 
 1. On the Azure portal menu or from the **Home** page, select **Create a resource**.
 2. Under **Categories**, select **Networking** and then select **Application Gateway** in the **Popular Azure services** list.

articles/application-gateway/quick-create-powershell.md

@@ -13,7 +13,7 @@ ms.custom: devx-track-azurepowershell, mvc, mode-api
 
 # Quickstart: Direct web traffic with Azure Application Gateway using Azure PowerShell
 
-In this quickstart, you use Azure PowerShell to create an application gateway. Then you test it to make sure it works correctly. 
+In this quickstart, you use Azure PowerShell to create an application gateway. Then you test it to make sure it works correctly.
 
 The application gateway directs application web traffic to specific resources in a backend pool. You assign listeners to ports, create rules, and add resources to a backend pool. For the sake of simplicity, this article uses a simple setup with a public frontend IP address, a basic listener to host a single site on the application gateway, a basic request routing rule, and two virtual machines in the backend pool.
 
@@ -76,6 +76,8 @@ New-AzPublicIpAddress `
 ```
 ## Create an application gateway
 
+The Standard v2 SKU is used in this example.
+
 ### Create the IP configurations and frontend port
 
 1. Use `New-AzApplicationGatewayIPConfiguration` to create the configuration that associates the subnet you created with the application gateway. 

articles/application-gateway/quick-create-template.md

@@ -5,15 +5,15 @@ description: In this quickstart, you learn how to use a Resource Manager templat
 services: application-gateway
 author: greg-lindsay
 ms.author: greglin
-ms.date: 01/23/2024
+ms.date: 04/18/2024
 ms.topic: quickstart
 ms.service: application-gateway
 ms.custom: mvc, subject-armqs, mode-arm, devx-track-arm-template
 ---
 
 # Quickstart: Direct web traffic with Azure Application Gateway - ARM template
 
-In this quickstart, you use an Azure Resource Manager template (ARM template) to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly.
+In this quickstart, you use an Azure Resource Manager template (ARM template) to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly. The Standard v2 SKU is used in this example.
 
 :::image type="content" source="media/quick-create-portal/application-gateway-qs-resources.png" alt-text="application gateway resources":::
 

articles/application-gateway/quick-create-terraform.md

@@ -16,7 +16,7 @@ ai-usage: ai-assisted
 
 # Quickstart: Direct web traffic with Azure Application Gateway - Terraform
 
-In this quickstart, you use Terraform to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly.
+In this quickstart, you use Terraform to create an Azure Application Gateway. Then you test the application gateway to make sure it works correctly. The Standard v2 SKU is used in this example.
 
 [!INCLUDE [About Terraform](~/azure-dev-docs-pr/articles/terraform/includes/abstract.md)]
 

articles/application-gateway/understanding-pricing.md

@@ -65,7 +65,7 @@ Compute unit guidance:
 * Standard_v2 - Each compute unit is capable of approximately 50 connections per second with RSA 2048-bit key TLS certificate.
 * WAF_v2 - Each compute unit can support approximately 10 concurrent requests per second for 70-30% mix of traffic with 70% requests less than 2 KB GET/POST and remaining higher. WAF performance isn't affected by response size currently.
 
-The following table shows example prices based on a snapshot of East US pricing and are for illustration purposes only.
+The following table shows example prices using Application Gateway Standard v2 SKU. These prices are based on a snapshot of East US pricing and are for illustration purposes only.
 
 #### Fixed Costs (East US region pricing)