|
| 1 | +--- |
| 2 | +title: Azure Front Door - routing limits | Microsoft Docs |
| 3 | +description: This article helps you understand the composite limits around routing for Azure Front Door. |
| 4 | +services: front-door |
| 5 | +documentationcenter: '' |
| 6 | +author: johndowns |
| 7 | +ms.service: frontdoor |
| 8 | +ms.topic: article |
| 9 | +ms.tgt_pltfrm: na |
| 10 | +ms.workload: infrastructure-services |
| 11 | +ms.date: 02/27/2022 |
| 12 | +ms.author: jodowns |
| 13 | +--- |
| 14 | + |
| 15 | +# Front Door routing limits |
| 16 | + |
| 17 | +Each Front Door profile has a *composite route limit*. |
| 18 | + |
| 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 | + |
| 21 | +The composite route metric for each Front Door profile can't exceed 5000. |
| 22 | + |
| 23 | +> [!TIP] |
| 24 | +> Most Front Door profiles don't approach the composite route limit. However, if you have a large Front Door profiles, consider whether you could exceed the limit and plan accordingly. |
| 25 | +
|
| 26 | +## Calculate your profile's composite route metric |
| 27 | + |
| 28 | +Follow these steps to calculate the composite route metric for your Front Door profile: |
| 29 | + |
| 30 | +1. Select a route from your profile. |
| 31 | + 1. Multiply the number of HTTP domains by the number of HTTP paths. |
| 32 | + 1. Multiply the number of HTTPS domains by the number of HTTPS paths. |
| 33 | + 1. Add the results of steps 1a and 1b together to give the composite route metric for this individual route. |
| 34 | +1. Repeat these steps for each route in your profile. |
| 35 | + |
| 36 | +Add together all of the composite route metrics for each route. This is your profile's composite route metric. |
| 37 | + |
| 38 | +### Example |
| 39 | + |
| 40 | +Suppose you have have two routes in your Front Door profile. The routes are named *Route 1* and *Route 2*. You plan to configure the routes as follows: |
| 41 | +* *Route 1* will have 50 domains associated to it, and requires HTTPS for all inbound requests. *Route 1* specifies 80 paths. |
| 42 | +* *Route 2* will have 25 domains associated to it. *Route 2* specifies 25 paths, and supports both the HTTP and HTTPS protocols. |
| 43 | + |
| 44 | +The following calculation illustrates how to determine the composite route metric for this scenario: |
| 45 | + |
| 46 | +``` |
| 47 | +Profile composite route metric = Route 1 composite route metric + Route 2 composite route metric |
| 48 | += Route 1 [HTTPS (50 Domains * 80 Paths)] + Route 2 [HTTP (25 Domains * 25 Paths) + HTTPS(25 Domains * 25 Paths)] |
| 49 | += [50 * 80] + [(25 * 25) + (25 * 25)] |
| 50 | += 5250 |
| 51 | +``` |
| 52 | + |
| 53 | +The calculated metric of 5250 exceeds the limit of 5000, so you can't configure a Front Door profile in this way. |
| 54 | + |
| 55 | +## Mitigation |
| 56 | + |
| 57 | +If your profile's composite route metric exceed 5000, consider the following mitigation strategies: |
| 58 | + |
| 59 | +- Deploy multiple Front Door profiles, and spread your routes across them. The composite route limit applies within a single profile. |
| 60 | +- 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. |
| 61 | +- Require HTTPS for inbound traffic, which reduces the number of HTTP routes in your profile and also improves your solution's security. |
| 62 | + |
| 63 | +## Next steps |
| 64 | + |
| 65 | +Learn how to [create a Front Door](quickstart-create-front-door.md). |
0 commit comments