Skip to content

Commit 98dd3a3

Browse files
committed
Update limits
1 parent c955aa7 commit 98dd3a3

File tree

2 files changed

+18
-18
lines changed

2 files changed

+18
-18
lines changed

articles/frontdoor/front-door-routing-limits.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ Each Front Door profile has a *composite route limit*.
1818

1919
Your Front Door profile's composite route metric is derived from the number of routes, as well as the front end domains, protocols, and paths associated with that route.
2020

21+
The composite route metric for each Front Door profile can't exceed 5000.
22+
2123
Most Front Door deployments don't approach this limit. However, if you have a large Front Door deployment, consider whether you could exceed the limit.
2224

2325
## Calculate your composite route metric
@@ -27,34 +29,32 @@ Use the following formula to calculate the composite route metric for your Front
2729
```
2830
Composite route metric = [Route1 [HTTP (#Domains * #Paths)] + Route1 [HTTPS (#Domains * #Paths)] + Route2 [HTTP (#Domains * #Paths)]+ HTTPS(#Domains * #Paths)] +… [RouteN [HTTP (#Domains * #Paths)]+ RouteN [HTTPS (#Domains * #Paths)]
2931
```
30-
31-
**The composite route metric for each Front Door profile can't exceed 5000.**
32-
33-
If you exceed 5000, you can consider the following mitigation strategies:
34-
35-
- Deploy multiple Front Door profiles, and spread your routes across them. The composite route limit applies within a single profile.
36-
- Use [wildcard domains](front-door-wildcard-domain.md) instead of specifying subdomains individually, which might help to reduce the number of domains in your profile.
37-
- Require HTTPS for inbound traffic, which reduces the number of HTTP routes in your profile and also improves your solution's security.
38-
39-
## Example
4032

41-
Suppose you have have two routes in your Front Door profile. The routes are named *Route1* and *Route2*.
33+
### Example
4234

43-
*Route1* has 50 domains associated to it, and requires HTTPS for all inbound requests. *Route1* specifies 80 paths.
44-
45-
*Route2* has 25 domains associated to it. *Route2* specifies 25 paths, and supports both HTTP and HTTPS protocols.
35+
Suppose you have have two routes in your Front Door profile. The routes are named *Route1* and *Route2*. You want to configure the routes as follows:
36+
* *Route1* will have 50 domains associated to it, and requires HTTPS for all inbound requests. *Route1* specifies 80 paths.
37+
* *Route2* will have 25 domains associated to it. *Route2* specifies 25 paths, and supports both the HTTP and HTTPS protocols.
4638

4739
The following calculation illustrates how to determine the composite route metric for this scenario:
4840

4941
```
5042
= Route1 [HTTPS(50 Domains*80 Paths)] + Route2 [HTTP (25 Domains*25 Paths) + HTTPS(25 Domains*25 Paths)]
5143
52-
= (50*80)+ (25*25)+ (25*25)
44+
= (50*80) + [(25*25) + (25*25)]
5345
5446
= 5250
5547
```
5648

57-
This exceeds the limit, so you can't configure a Front Door profile in this way.
49+
The calculated metric of 5250 exceeds the limit of 5000, so you can't configure a Front Door profile in this way.
50+
51+
## Mitigation
52+
53+
If your profile's composite route metric exceed 5000, consider the following mitigation strategies:
54+
55+
- Deploy multiple Front Door profiles, and spread your routes across them. The composite route limit applies within a single profile.
56+
- Use [wildcard domains](front-door-wildcard-domain.md) instead of specifying subdomains individually, which might help to reduce the number of domains in your profile.
57+
- Require HTTPS for inbound traffic, which reduces the number of HTTP routes in your profile and also improves your solution's security.
5858

5959
## Next steps
6060

includes/front-door-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
ms.custom: include file
1111
---
1212

13-
* In addition to the limits below, there is a [composite limit on the number of routing rules, front-end domains, protocols, and paths](TODO).
13+
* In addition to the limits below, there is a [composite limit on the number of routing rules, front-end domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
1414

1515
| Resource | Limit |
1616
| --- | --- |
@@ -37,7 +37,7 @@
3737
### Azure Front Door Standard/Premium (Preview) Service Limits
3838

3939
* Maximum **500** total Standard and Premium profiles per subscription.
40-
* In addition to the limits below, there is a [composite limit on the number of routes, domains, protocols, and paths](TODO).
40+
* In addition to the limits below, there is a [composite limit on the number of routes, domains, protocols, and paths](../articles/frontdoor/front-door-routing-limits.md).
4141

4242
| Resource | Standard SKU Limit | Premium SKU Limit |
4343
| --- | --- | --- |

0 commit comments

Comments
 (0)