Breyta

Deila með

Add a new endpoint with Front Door manager

  • Grein

This article shows you how to add a new endpoint to an existing Azure Front Door profile in the Front Door manager.

Prerequisites

Before you can create a new endpoint with Front Door manager, you must have an Azure Front Door profile created. To create an Azure Front Door profile, see create an Azure Front Door. The profile must have at least one endpoint.

Create a new Front Door endpoint

  1. Sign in to the Azure portal and navigate to your Azure Front Door profile.

  2. Select Front Door manager from under Settings from the left side menu pane. Then select + Add an endpoint to create a new endpoint.

    Screenshot of add an endpoint through Front Door manager.

  3. On the Add an endpoint page, enter a unique name for the endpoint.

    Screenshot of add an endpoint page.

    • Name - Enter a unique name for the new Front Door endpoint. Azure Front Door generates a unique endpoint hostname based on the endpoint name in the form of <endpointname>-*.z01.azurefd.net.
    • Endpoint hostname - A deterministic DNS (domain name system) name that helps prevent subdomain takeover. This name is used to access your resources through your Azure Front Door at the domain <endpointname>-*.z01.azurefd.net.
    • Status - Set as checked to enable this endpoint.

Add a route

  1. To add a new route, first expand an endpoint from the list of endpoints in the Front Door manager.

    Screenshot of list of endpoints in Front Door manager.

  2. In the endpoint configuration pane, select + Add a route to configure the mapping of your domains and routing configuration to your origin group.

    Screenshot of add a route button from endpoint configuration pane.

  3. On the Add a route page, enter, or select the following information:

    Screenshot of the route configuration page.

    • Name - Enter a unique name for the new route

    • Enable route - Set as checked to enable this route.

    • Domains - Select one or more validated domains that aren't associated to another route. For more information, see add a custom domain.

    • Patterns to match - Configure all URL path patterns that this route accepts. For example, you can set the pattern to match to /images/* to accept all requests on the URL www.contoso.com/images/*. Azure Front Door determines the traffic based on exact match first. If no paths match exactly, then Front Door looks for a wildcard path that matches. If no routing rules are found with a matching path, then the request get rejected and returns a 400: Bad Request error HTTP response. Patterns to match paths aren't case sensitive, meaning paths with different casing are treated as duplicates. For example, you have a host using the same protocol with paths /FOO and /foo. These paths are considered duplicates, and aren't allowed in the Patterns to match field.

    • Accepted protocols - Specify the protocols you want Azure Front Door to accept when the client is making the request. You can specify HTTP, HTTPS, or both.

    • Redirect - Specify whether HTTPS is enforced for the incoming HTTP requests.

    • Origin group - Select the origin group to forward traffic to when requests are made to the origin. For more information, see configure an origin group.

    • Origin path - This path is used to rewrite the URL that Front Door uses when constructing the request forwarded to the origin. By default, this path isn't provided. Therefore, Front Door uses the incoming URL path in the request to the origin. You can also specify a wildcard path, which copies any matching part of the incoming path to the request path to the origin. The origin path is case sensitive.

      Pattern to match: /foo/* Origin path: /fwd/

      Incoming URL path: /foo/a/b/c/ URL from Front Door to origin: fwd/a/b/c

    • Forwarding protocol - Select the protocol used for forwarding request. You can specify HTTP only, HTTPS only, or match incoming request.

    • Caching - Select this option to enable caching of static content with Azure Front Door. For more information, see caching with Front Door.

    • Rules - Select rule sets that get applied to this route. For more information, see rule sets for Front Door.

  4. Select Add to create the new route. The route appears in the list of routes for the endpoints.

    Screenshot of new created route in an endpoint.

Add security policy

  1. Select + Add a policy, in the Security policy pane to apply or create a new web application firewall policy to associate to your domains.

    Screenshot of add a policy button from endpoint configuration pane.

  2. On the Add security policy page, enter, or select the following information:

    Screenshot of add security policy page.

    • Name - Enter a unique name within this Front Door profile for the security policy.
    • Domains - Select one or more domains you want to apply this security policy to.
    • WAF (Web Application Firewall) Policy - Select an existing or create a new WAF policy. When you select an existing WAF policy, it must be the same tier as the Front Door profile. For more information, see configure WAF policy for Front Door.

  3. Select Save to create the security policy and associate it with the endpoint.

    Screenshot of security policy associated with an endpoint.

Configure origin timeout

Origin timeout is the amount of time Azure Front Door waits until it considers the connection to origin valid. You can set this value on the overview page of the Azure Front Door profile. This value is applied to all endpoints in the profile.

Screenshot of the origin timeout settings on the overview page of the Azure Front Door profile.

Clean up resources

In order to remove an endpoint, you first have to remove any security policies associated with the endpoint. Then select Delete endpoint to remove the endpoint from the Azure Front Door profile.

Screenshot of the deleted endpoint button from inside an endpoint.

Next steps