Microsoft Azure

Microsoft Azure offers various capabilities to host Docker containers. For our tutorial, we chose for the Web App for Containers.

We have used the Web App for Containers ourselves and experienced some stability issues, even though the technique is not in preview anymore.

Please test and monitor your Fonto Connectors instance on Web App for Containers thoroughly.

Create a Web App for Containers (Required)

Create a Web App for Containers on the Azure Portal. Make sure to create or select a Linux App Service plan.

The creation wizard of the Web App needs you to configure the source of the Docker Container. Fill in the credentials needed for the Docker registry. Make sure the user you fill in has enough rights to pull the image.

Setup a custom domain (Optional)

See the Microsoft Custom Domain documentation for more information.

Enable SSL (Required)

To configure SSL for your Web App, see the Microsoft Custom SSL documentation on binding your SSL certificate to your Web App.

Enable Always On (Optional)

By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources (and thus money). In Basic or Standard mode, you can enable Always On to keep the app loaded all the time.

When your web app is unloaded, it will take Azure some time to bring up the web app when it is accessed next. Enabling Always On will keep the web app loaded at all times.

To enable Always On, please see the Microsoft Application Settings documentation.

Environment Settings (Required)

Fill in the environment variables that you have configured for Fonto Connectors into the Application Settings section of your Web App. Please leave the existing settings as they are used by Azure.

Use the values that you have entered in the .env to set the environment variables.


You must specify the following environment variables for the Web App to function correctly:






Azure Web Apps have an SSL offloading loadbalancer. This configuration makes sure that the X-Forwarded-For and X-Forwarded-Proto headers are respected when constructing URL's (e.g. return-URLs during authentication).