Configure Auto Deployments

September 12, 2018 ยท 2 minute read


This post is a continuation of “Six Easy Steps to Deploying Static HTML on Azure”. If you haven’t already deployed your new static HTML site following the steps outlined in that post, I suggest starting there first.

Now that our static HTML site is live, I want to take it one step further.

I’m not sure how often I’ll be making changes to the content of my site, but I know that I want to remove as many barriers to releasing new information as I can.

Luckily, because the HTML source code for my site is stored in a GitHub repository, I can synchronize my Azure App Service with the repo and any time a change is made to the codebase, Azure will rebuild my site and deploy it… auto-magically.

Here are the steps:

1. Configure Deployment Options

From within the Azure Dashboard, let’s begin by browsing to your new App Service (Resource) and select “Deployment Options” from the list.

2. Choose Source Control

Next, we will select the “Choose Source” (Configure required settings) option.

Select the correct source. I’m using GitHub, so that is the option I will choose.

3. Choose Account, Project, Branch

The next screen will prompt you to enter your GitHub account, project, branch, etc.

Once you have made your configuration choices, select “Save” at the bottom of the screen. That’s it!

4. Confirm Deployment

Any time new code is pushed to your repository, Azure will automatically deploy the changes for you. We can confirm this by making a change to our codebase from the local development environment followed by committing new code or changes to existing code to our repository on GitHub.

The next thing I want to do is point my own domain ( to this site (App Service). However, in order to do so, I will need to scale my App Service to a larger size. FREE tiers do not offer the ability to use custom domains.

In the next post, we’ll walk through the process of scaling our App Service up and configuring everything so my domain resolves to this new site.

Check it out: “Scale an App Service”