In order to change the slots for production and staging, for example, you can swap between them. You can have several slots for testing, staging and so forth, but the web app that will be presented to the world will be the one in the Production Slot. When you create an Azure App Service you have one deployment slot, called the Production slot, which is directly linked to the Azure URL you created when creating the App Service. The next item we are going to talk about are deployment slots. It automatically updates the code of your web app to Azure each time you commit the code to GitHub, Bitbucket, etc.
Kudu is a continuous deployment tool, which integrates with your GitHub, Bitbucket, and so forth. There are a couple of ways you can deploy a web app to Azure: FTP transfer, web deploy using Visual Studio and Kudu. Deployment Basicsīefore we dive in into each type of deployment, we need to remember that even if we don’t have to manage the backend infrastructure for the app service, we still need to deploy our web app to the IIS servers that are hosted by Azure.
In this article, we will deploy a Web App in our Web App Service environment and show you the different ways you can go about doing this. I hope you enjoyed my previous article, which was an introductory one that helped us create an Azure App Service. Welcome to another article on Microsoft Azure App Services.
