Deployment slots is one of Azure App Service greatest features. With deployment slots in place, you shouldn't be worried if your new release doesn't work appropriately when it is released to production. This is because you can have different slots for dev/test purposes and a different slot for production.
Using deployment slots, you can verify that the application is functioning properly before publishing it. Then, you can swap it with the production slot, which will cause almost no downtime. If the application does not behave as expected, you can swap it with the application that was working in production right before you swapped the slots. When you create an App Service, it's running on the default production slot.
To add an additional deployment slot, follow these steps:
- Navigate to the App Service that you want to add another deployment slot to.
- Under Deployment, click on Deployment slots, as shown in the following screenshot:
- Click on Add Slot, and a new blade will pop up where you have to specify the following:
- Name: Specify a descriptive name for the slot.
- Configuration Source: Specify whether you want to clone the configuration from another slot or not:
