In short, the Swap operation will exchange the website's content between 2 deployment slots.

The first feature of deployment slots is the Swap Slots and it's used for Staged Deployment You can add more than one deployment slot. In fact by default each Azure Web App has a single deployment slot called production which is the Azure Web App itself. It's important to emphasize that the slot is in itself a regular Azure Web App, it will have its own app settings, connection string, any other configuration settings and even an scm site ( ). If my Azure Web App is called mysite and I create a slot called staging then my slot will be an Azure Web App with the name mysite(staging) and its url will be. In this post I will go over the deployment slots concept and what you can do with it.įrom a (standard) website you can create deployment slots which will actually be Azure Web App instances that are tied to that Website.Ī deployment slot will carry the name of the Azure Web App + the name of the slot, for example: One of the premium features you get when using Azure Web Apps in a standard SKU is the deployment slots feature also known as staged deployment but it is actually more than that.

Azure web app deployment slots traffic