Deployment slots for staging in Azure - Step-by-Step Execution

Process Flow - Deployment slots for staging

Create Web App

↓

Add Deployment Slot: Staging

↓

Deploy Code to Staging Slot

↓

Test Staging Slot

↓

Swap Slots: Staging <-> Production

↓

Production Runs New Version

↓

Old Production Becomes Staging

This flow shows how a staging slot is created, code is deployed and tested there, then swapped with production for safe release.

Execution Sample

Azure

az webapp deployment slot create --name MyApp --resource-group MyRG --slot staging
az webapp deployment slot swap --name MyApp --resource-group MyRG --slot staging

Creates a staging slot for the web app and then swaps it with production to release new code safely.

Process Table

Step	Action	Slot State	Result
1	Create Web App 'MyApp'	Production: running, Staging: none	Web app created with only production slot
2	Create staging slot	Production: running, Staging: created (empty)	Staging slot ready for deployment
3	Deploy code to staging	Production: running, Staging: running new code	New version running in staging slot
4	Test staging slot	Production: running, Staging: running new code	Tests passed, ready to swap
5	Swap staging with production	Production: running new code, Staging: running old code	Slots swapped; production runs new code
6	Post-swap state	Production: running new code, Staging: running old code	Old production version now in staging slot

💡 Swap completes, production runs new version safely with rollback option in staging slot

Status Tracker

Slot	Initial	After Creation	After Deploy	After Swap
Production	Running old code	Running old code	Running old code	Running new code
Staging	None	Created empty	Running new code	Running old code

Key Moments - 3 Insights

Why do we create a separate staging slot instead of deploying directly to production?

Creating a staging slot lets us test new code safely without affecting users. Execution table step 3 shows new code running only in staging before swap.

What happens during the swap step?

The swap exchanges the content and traffic between production and staging slots. Step 5 shows production running new code after swap, step 6 confirms the post-swap state.

Can we quickly rollback if the new code has issues?

Yes, because the old production version moves to staging slot after swap (step 6), we can swap again to rollback.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of the staging slot after step 3?

A Staging slot is empty

B Staging slot is running new code

C Staging slot is running old code

D Staging slot does not exist

💡 Hint

Check the 'Slot State' column for step 3 in the execution table

At which step does production start running the new code?

A Step 5

B Step 4

C Step 6

D Step 3

💡 Hint

Look at the 'Slot State' column after swap completes in the execution table

If we skip testing in staging (step 4), what risk increases?

A No risk, swap is safe

B Staging slot will be deleted automatically

C New code might have bugs affecting production

D Production slot will stop running

💡 Hint

Refer to the purpose of step 4 in the concept flow and key moments

Concept Snapshot

Deployment slots let you run a staging version of your app.
Deploy and test new code in staging without affecting users.
Swap staging with production to release safely.
Old production version moves to staging for quick rollback.
Use Azure CLI commands to create slots and swap them.

Full Transcript

Deployment slots for staging in Azure let you create a separate environment for your web app. You first create your main web app with a production slot. Then you add a staging slot where you deploy new code. You test the staging slot to ensure the new version works well. When ready, you swap the staging slot with production. This swap makes the new code live for users while moving the old production version to staging. This way, you can quickly rollback if needed. The process uses Azure CLI commands to create slots and swap them. This method helps release updates safely without downtime or risk to users.