title | description | services | author | ms.service | ms.topic | ms.workload | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|
Front Door manager - Azure Front Door |
This article is about concepts of the Front Door manager. You'll learn about routes and security policies in an endpoint. |
frontdoor |
duongau |
frontdoor |
conceptual |
infrastructure-services |
03/16/2022 |
duau |
The Front Door manager in Azure Front Door Standard and Premium provides an overview of endpoints you've configured for your Azure Front Door profile. With Front Door manager, you can manage your collection of endpoints. You can also configure routings rules along with their domains and origin groups, and security policies you want to apply to protect your web application.
:::image type="content" source="./media/manager/manager.png" alt-text="Screen shot of the Azure Front Door manager page." lightbox="./media/manager/manager-expanded.png":::
An endpoint is a logical grouping of one or more routes that associates with domains. A route contains the origin group configuration and routing rules between domains and origins. An endpoint can have one or more routes. A route can have multiple domains but only one origin group. You need to have at least one configured route in order for traffic to route between your domains and the origin group.
Note
- You can enable or disable an endpoint or a route.
- Traffic will only flow to origins once both the endpoint and route is enabled.
Domains configured within a route can either be a custom domain or an endpoint domain. For more information about custom domains, see create a custom domain with Azure Front Door. Endpoint domains refer to the auto generated domain name when you create a new endpoint. The name is a unique endpoint hostname with a hash value in the format of endpointname-hash.z01.azurefd.net
. The endpoint domain will be accessible if you associate it with a route.
An endpoint domain can be reused within the same tenant, subscription, or resource group scope level. You can also choose to not allow the reuse of an endpoint domain. The Azure portal default settings allow tenant level reuse of the endpoint domain. You can use command line to configure the scope level of the endpoint domain reuse. The Azure portal will use the scope level you define through the command line once it has been changed.
Value | Behavior |
---|---|
TenantReuse | This is the default value. Object with the same name in the same tenant will receive the same domain label. |
SubscriptionReuse | Object with the same name in the same subscription will receive the same domain label. |
ResourceGroupReuse | Object with the same name in the same resource group will receive the same domain label. |
NoReuse | Object with the same will receive a new domain label for each new instance. |
A security policy is an association of one or more domains with a Web Application Firewall (WAF) policy. The WAF policy will provide centralized protection for your web applications. If you manage security policies using the Azure portal, you can only associate a security policy with domains that are in the Routes configuration of that endpoint.
Tip
- If you see one of your domains is unhealthy, you can select the domain to take you to the domains page. From there you can take appropriate actions to troubleshoot the unhealthy domain.
- If you're running a large Azure Front Door profile, review Azure Front Door service limits and Azure Front Door routing limits to better manage your Azure Front Door.
In Azure Front Door (classic), the Front Door manager is called Front Door designer. In Azure Front Door (classic), only one endpoint is supported for each Front Door profile.
:::image type="content" source="./media/manager/designer.png" alt-text="Screen shot of the Azure Front Door (classic) designer page." lightbox="./media/manager/designer-expanded.png":::
- Learn how to configure endpoints with Front Door manager.
- Learn about the Azure Front Door routing architecture.
- Learn how traffic is matched to a route in Azure Front Door.