Azure App Service And KUDU - The Deployment Framework

In one of my recent article on Azure App Service: Deployment Types And FTP Credential Types, we discussed two ways of deploying the Application Content. However, there is another way of deploying the application code to Azure App Service. It’s by Source Control. Yes, you can deploy the code sitting in your Source Control repository directly into Azure App Service. (Anyways, I will write a separate article on how to deploy the code from Source Control to Azure App Service soon)

Azure supports us to deploy the code from the following sources.



So, when you set one of these as the source of the code, you might be thinking that there should be some component in each of these products which is responsible for deploying the code into the Azure App Service. No, that's not how it is. The component is within the App Service that is responsible for pulling the code from the above sources and deploying the same into the App Service. Yes, this component's name is KUDU – The Deployment Framework (triggered by Git) that takes care of deploying the code to Azure App Service. The same is depicted in the below image.



Note

VSTS supports two type of repositories.

1. TFVC
2. Git

KUDU doesn’t deploy TFVC code. It just supports the second option, Git.

VSTS takes care of building and deploying the TFVC code. And, all other options (including VSTS – GIT) supported as “Deployment Source” in the above image are built and deployed within Azure App Service using KUDU behind the scenes.

When you can create an Azure App Service, Kudu’s website and related tools also get created within the Azure App Service’s Context. So, it means, KUDU is a Friend of our App Service which has access to all the resources that are in the App Service’s Context.

Please note that for each App Service that you create, a separate instance of KUDU’s website is also created for you.



How do I access the KUDU website? – There are two ways to access the KUDU website.