Select the app URL on the slot's resource page. You can also see the slot as a separate app in your resource group, with the same designations.

To remind you that you're viewing the deployment slot, the app name is shown as /, and the app type is App Service (Slot). The staging slot has a management page just like any other App Service app. Select the new deployment slot to open that slot's resource page. By default, Traffic % is set to 0 for the new slot, with all customer traffic routed to the production slot. The new slot is now shown on the Deployment slots page. The app must be running in the Standard, Premium, or Isolated tier in order for you to enable multiple deployment slots.Ĭurrently, a private endpoint isn't cloned across slots.Īfter the slot is added, select Close to close the dialog box. Prerequisitesįor information on the permissions you need to perform the slot operation you want, see Resource provider operations (search for slot, for example). For example, if your app has more than five slots, you can't scale it down to the Standard tier, because the Standard tier supports only five deployment slots. To scale your app to a different tier, make sure that the target tier supports the number of slots your app already uses.

To find out the number of slots your app's tier supports, see App Service limits. There's no extra charge for using deployment slots. 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 nonproduction 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.

$transclude function in multislot