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/front-door-routing-limits.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ Each Front Door profile has a *composite route limit*.
18
18
19
19
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.
20
20
21
+
The composite route metric for each Front Door profile can't exceed 5000.
22
+
21
23
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.
22
24
23
25
## Calculate your composite route metric
@@ -27,34 +29,32 @@ Use the following formula to calculate the composite route metric for your Front
**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
40
32
41
-
Suppose you have have two routes in your Front Door profile. The routes are named *Route1* and *Route2*.
33
+
### Example
42
34
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.
46
38
47
39
The following calculation illustrates how to determine the composite route metric for this scenario:
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.
Copy file name to clipboardExpand all lines: includes/front-door-limits.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
ms.custom: include file
11
11
---
12
12
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).
14
14
15
15
| Resource | Limit |
16
16
| --- | --- |
@@ -37,7 +37,7 @@
37
37
### Azure Front Door Standard/Premium (Preview) Service Limits
38
38
39
39
* 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).
0 commit comments