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/frontdoor/understanding-pricing.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
2
title: Compare pricing between Azure Front Door tiers
3
-
description: This article describes the billing model for Azure Front Door and compares the pricing for the Standard, Premium and (classic) tiers.
3
+
description: This article describes the billing model for Azure Front Door and compares the pricing for the Standard, Premium, and (classic) tiers.
4
4
services: frontdoor
5
5
author: duongau
6
6
ms.service: azure-frontdoor
7
7
ms.topic: conceptual
8
-
ms.date: 05/30/2023
8
+
ms.date: 08/12/2024
9
9
ms.author: duau
10
10
---
11
11
@@ -14,7 +14,7 @@ ms.author: duau
14
14
> [!NOTE]
15
15
> 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/frontdoor/)
16
16
17
-
Azure Front Door has three tiers: Standard, Premium, and (classic). This article describes the billing model for Azure Front Door and compares the pricing for the Standard, Premium and (classic) tiers. When migrating from Azure Front Door (classic) to Standard or Premium, we recommend you do a cost analysis to understand the pricing differences between the tiers. We show you how to evaluate cost that you can apply your environment.
17
+
Azure Front Door has three tiers: Standard, Premium, and (classic). This article describes the billing model for Azure Front Door and compares the pricing for the Standard, Premium, and (classic) tiers. When migrating from Azure Front Door (classic) to Standard or Premium, we recommend you do a cost analysis to understand the pricing differences between the tiers. We show you how to evaluate cost that you can apply your environment.
18
18
19
19
## Pricing model comparison
20
20
@@ -47,7 +47,7 @@ The following are general guidance for getting the right metrics to estimate the
47
47
48
48
| Azure Front Door Standard/Premium meter | How to calculate from Azure Front Door (classic) metrics |
49
49
|--|--|
50
-
| Base fee | - If you need managed WAF rules, bot protection, or Private Link: **$330/month** </br> - If you only need custom WAF rules: **$35/month**|
50
+
| Base fee | - If you need managed WAF (Web Application Firewall) rules, bot protection, or Private Link: **$330/month** </br> - If you only need custom WAF rules: **$35/month**|
51
51
| Requests | **For Standard:** </br>1. Go to your Azure Front Door (classic) profile, select **Metrics** from under *Monitor* in the left side menu pane. </br>2. Select the **Request Count** from the *Metrics* drop-down menu. </br> 3. To view regional metrics, you can apply a split to the data by selecting **Client Country** or **Client Region**. </br> 4. If you select *Client Country*, you need to map them to the corresponding Azure Front Door pricing zone. </br> :::image type="content" source="./media/understanding-pricing/request-count.png" alt-text="Screenshot of the request count metric for Front Door (classic)." lightbox="./media/understanding-pricing/request-count.png"::: </br> **For Premium:** </br>You can look at the **Request Count** and the **WAF Request Count** metric in the Azure Front Door (classic) profile. </br> :::image type="content" source="./media/understanding-pricing/waf-request-count.png" alt-text="Screenshot of the Web Application Firewall request count metric for Front Door (classic)." lightbox="./media/understanding-pricing/waf-request-count.png"::: |
52
52
| Egress from Azure Front Door edge to client | You can obtain this data from your Azure Front Door (classic) invoice or from the **Billable Response Size** metric in the Azure Front Door (classic) profile. To get a more accurate estimation, apply split by *Client Count* or *Client Region*.</br> :::image type="content" source="./media/understanding-pricing/billable-response-size.png" alt-text="Screenshot of the billable response size metric for Front Door (classic)." lightbox="./media/understanding-pricing/billable-response-size.png"::: |
53
53
| Ingress from Azure Front Door edge to origin | You can obtain this data from your Azure Front Door (classic) invoice. Refer to the quantities for Data transfer from client to edge location as an estimation. |
@@ -121,9 +121,9 @@ Azure Front Door Premium is ~45% cheaper than Azure Front Door (classic) for sta
@@ -181,7 +181,7 @@ In this comparison, Azure Front Door Premium is ~5% more expensive than Azure Fr
181
181
| WAF managed/ defaults rule set requests processed | $20 = 20 million requests * $1 per million requests | $0 |
182
182
| Total | $17,551 .30| $29,945 |
183
183
184
-
In this comparison, Azure Front Door Premium is 1.7x more expensive than Azure Front Door (classic) because of the higher base fee for each profile. The outbound data transfer is 45% less for Azure Front Door Premium compared to Azure Front Door (classic). With Premium tier, you don't have to pay for route rules which account for $7,700 of the total cost.
184
+
In this comparison, Azure Front Door Premium is 1.7x more expensive than Azure Front Door (classic) because of the higher base fee for each profile. The outbound data transfer is 45% less for Azure Front Door Premium compared to Azure Front Door (classic). With Premium tier, you don't have to pay for route rules, which account for $7,700 of the total cost.
0 commit comments