If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back.Įach App Service plan tier supports a different number of deployment slots.
After a swap, the slot with previously staged app now has the previous production app. You can automate this entire workflow by configuring auto swap when pre-swap validation isn't needed. The traffic redirection is seamless, and no requests are dropped because of swap operations. 
This eliminates downtime when you deploy your app.
Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production. You can validate app changes in a staging deployment slot before swapping it with the production slot. App content and configurations elements can be swapped between two deployment slots, including the production slot.ĭeploying your application to a non-production slot has the following benefits: Deployment slots are live apps with their own host names. When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot when you're running in the Standard, Premium, or Isolated App Service plan tier.
0 kommentar(er)
