When you deploy Cloudmersive Reverse Proxy server in Azure App Service, Azure Front Door can be applied in front to provide CDN routing and additional protections, such as DDOS protection. In this guide, we will walk through how to configure this.

Prerequisites

• An existing Azure website that is already deployed and reachable (for example, an App Service web app) running Cloudmersive Reverse Proxy Server
• Azure permissions to create resources in a subscription (Contributor or higher typically works)
• The origin hostname for your existing site (for App Service, this is the site’s default hostname shown in the app’s Overview)

Procedure

Step 1: Start the Front Door creation wizard

1. Sign in to the Azure portal.
2. Select Create a resource.
3. Search for Front Door and CDN profiles.
4. Select Create.

Step 2: Choose Quick create

1. On the offering selection screen, choose Quick create.
2. Continue to create a new Front Door configuration.

Step 3: Configure the Front Door basics

In the Quick create form, fill in the required fields:

1. Subscription: select the subscription that contains (or will contain) the Front Door resource.

2. Resource group: select an existing resource group or create a new one.

3. Tier / SKU:

   • Choose Standard for the simplest “global entry point in front of my site” setup.
   • Choose Premium if you specifically need advanced features such as Private Link to origins or more advanced security and routing scenarios.

4. Profile name (if prompted): enter a name for the Front Door profile.

5. Endpoint name: enter the public endpoint name for your Front Door. (Azure will generate a default hostname for it automatically.)

Step 4: Add your existing website as the origin

1. Origin type: choose the appropriate type for your existing website (for many “Azure website” scenarios, this will be an App Service origin type).

2. Origin name (if prompted): give the origin a friendly name (for example, webapp-origin).

3. Origin hostname: select or enter the hostname of your existing site (this is the address Front Door will forward to).

4. HTTP/HTTPS ports:

   • Leave defaults unless your origin uses a non-standard port (most Azure websites use the defaults).

Step 5: Set the default routing behavior (Quick create defaults)

Quick create typically sets up a default route so Front Door forwards traffic to your origin.

If the wizard exposes these options, use these common settings:

• Redirect HTTP to HTTPS: enable (recommended)
• Patterns to match: keep the default “match all” behavior (so all paths go to the origin)

Step 6: Review and create

1. Select Review + create.

2. Confirm the configuration looks correct:

   • The profile is Standard or Premium
   • The endpoint is created
   • The origin points to your existing website’s hostname

3. Select Create to deploy.

Notes when Using Power Pages

Update your redirect and transform policies to use the Azure Frontdoor domain name/FQDN rather than the Azure App Service FQDN. For the redirect_uri use the Azure Frontdoor domain name/FQDN.