Skip to content

Commit eff13be

Browse files
committed
Update understanding-pricing.md
1 parent e714731 commit eff13be

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/application-gateway/understanding-pricing.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ author: greg-lindsay
66
ms.service: application-gateway
77
ms.topic: conceptual
88
ms.custom: references_regions
9-
ms.date: 09/01/2020
9+
ms.date: 10/03/2022
1010
ms.author: greglin
1111
---
1212

1313
# Understanding Pricing for Azure Application Gateway and Web Application Firewall
1414

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/).
1717
1818
Azure Application Gateway is a layer 7 load-balancing solution, which enables scalable, highly available, and secure web application delivery on Azure.
1919

@@ -36,7 +36,7 @@ A single Capacity Unit consists of the following parameters:
3636
* 2.22-Mbps throughput
3737
* 1 Compute Unit
3838

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.
4040
The parameter with the highest utilization among the three above will be internally used for calculating capacity units, which is in turn billed.
4141

4242
##### Compute Unit
@@ -376,7 +376,7 @@ You can view the amount of consumption for different parameters (compute unit, t
376376

377377
* Estimated Billed Capacity units
378378

379-
Estimated Billed Capacity units indicates 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).
380380

381381
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)
382382

0 commit comments

Comments
 (0)