Continuous Delivery in Azure

Configuring Continuous Delivery in the Cloud for Azure Web Apps

Using Azure, you can build and deploy your code continuously in most comfortable way that suites you and your team. Some of the ways, but not limited to what is mentioned below are:-

  • Using power shell script
  • Using build definition with configurable build steps
  • Using a hybrid build environment, where you can configure, Azure cloud to run build on-premise
  • Using Azure portal to configure builds.

In this post, we will learn how we can easily configure builds for Azure Web Site using Azure Portal.

If you have not yet tried to configure continuous delivery for Azure Web Apps. Here is an easy way to get it up and running in few minutes.

Assuming you have an Azure account and have already created a web app. If not, you can sign up for a free account here.

To get started log in to Azure Portal at

Click on browse and then select Web Apps tab. Select the application you want to configure continuous delivery. Like in my case I will be using the highlighted application.

You can create up to 10 Free websites, unless you are using some advanced features. To understand Azure pricing click here.

After selecting Web App, you will see below screen. Here you have options to configure continues deployment. It is advisable to create a deployment slot to test your code changes, before moving to Production. If you already have a deployment slot click on it then select from the list of slots. It will open a similar screen that you are on.

Click on the Deployment tile (highlighted in red). You now have option to choose your code repository source.

Build hub on Visual studio online supports external code repositories as well. Some of the repositories are listed below in the image.

 Next select team project from the available list

After selecting Team project you are required to select the code repository.  In the example below we have only one code repository.

Last setting is about the branch you are require to build. In this case we have only one branch, so we choose master.

This completes setting up your continuous deployment. Check all you settings and click ok to save it.

Now, if you log in to your Visual Studio Online account, you should be able to see the configured build definition on the build tab.

Each time you push your code to the repository, you will be able to kick off a build, then at the end, it will deploy it to configures slot. It is staging slot in this this case.

You can see the status update and activity on the portal page as well as shown on the highlighted deployment button. Once the test and validation is passed, you can quickly make your changes live by clicking on the SWAP button on either of the blade.

I will post about other ways to do build on Azure portal soon. If there is a special case that you would like to get address, please do feel free to contact me.