You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/understanding-pricing.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,14 @@ author: greg-lindsay
6
6
ms.service: application-gateway
7
7
ms.topic: conceptual
8
8
ms.custom: references_regions
9
-
ms.date: 09/01/2020
9
+
ms.date: 10/03/2022
10
10
ms.author: greglin
11
11
---
12
12
13
13
# Understanding Pricing for Azure Application Gateway and Web Application Firewall
14
14
15
-
>[!NOTE]
16
-
>Prices shown in this article are examples and are for illustration purposes only. For pricing information according to your region, see the [Pricing page](https://azure.microsoft.com/pricing/details/application-gateway/).
15
+
>[!NOTE]
16
+
>Prices shown in this article are examples and are for illustration purposes only. For pricing information according to your region, see the [Pricing page](https://azure.microsoft.com/pricing/details/application-gateway/).
17
17
18
18
Azure Application Gateway is a layer 7 load-balancing solution, which enables scalable, highly available, and secure web application delivery on Azure.
19
19
@@ -36,7 +36,7 @@ A single Capacity Unit consists of the following parameters:
36
36
* 2.22-Mbps throughput
37
37
* 1 Compute Unit
38
38
39
-
If any one of these parameters are exceeded, then another n capacity unit(s) are necessary, even if the other two parameters don’t exceed this single capacity unit’s limits.
39
+
If any of these parameters are exceeded, then another N capacity units are necessary, even if the other two parameters don’t exceed this single capacity unit’s limits.
40
40
The parameter with the highest utilization among the three above will be internally used for calculating capacity units, which is in turn billed.
41
41
42
42
##### Compute Unit
@@ -376,7 +376,7 @@ You can view the amount of consumption for different parameters (compute unit, t
376
376
377
377
* Estimated Billed Capacity units
378
378
379
-
Estimated Billed Capacity unitsindicates the number of capacity units using which the billing is estimated. This is calculated as the greater value between Current capacity units (capacity units required to load balance the traffic) and Fixed billable capacity units (minimum capacity units kept provisioned).
379
+
The **Estimated Billed Capacity units** metric indicates the number of capacity units estimated for billing. This metric is calculated as the greater value between **Current capacity units** (capacity units required to load balance the traffic) and **Fixed billable capacity units** (minimum capacity units kept provisioned).
380
380
381
381
More metrics such as throughput, current connections and compute units are also available to understand bottlenecks and estimate the number of capacity units required. Detailed information is available at [Application Gateway Metrics](application-gateway-metrics.md)
0 commit comments