Skip to content

Commit 2015d31

Browse files
authored
changed files by pdets auto publish service, publishid[8085e686-533c-4471-8e8b-ccae7d395a0d] and do [publish].
1 parent d3a0688 commit 2015d31

File tree

5 files changed

+52
-3
lines changed

5 files changed

+52
-3
lines changed
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.exercise-swap-deployment-slots
3+
title: Exercise - Swap deployment slots in Azure App Service
4+
metadata:
5+
adobe-target: true
6+
prefetch-feature-rollout: true
7+
title: Exercise - Swap deployment slots in Azure App Service
8+
description: "Exercise - Swap deployment slots in Azure App Service"
9+
ms.date: 05/13/2025
10+
author: wwlpublish
11+
ms.author: jeffko
12+
ms.topic: unit
13+
ms.custom:
14+
- N/A
15+
durationInMinutes: 30
16+
content: |
17+
[!include[](includes/4a-exercise-swap-deployment-slots.md)]

learn-pr/wwl-azure/understand-app-service-deployment-slots/includes/2-app-service-staging-environments.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
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. This approach is available if you run in the **Standard**, **Premium**, or **Isolated** App Service plan tier. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot.
1+
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. This approach is available if you run in the **Standard**, **Premium**, or **Isolated** App Service plan tier. Deployment slots are live apps with their own host names. App content and configuration elements can be swapped between two deployment slots, including the production slot.
22

33
Deploying your application to a nonproduction slot has the following benefits:
44

5-
* You can validate app changes in a staging deployment slot before swapping it with the production slot.
6-
* Deploy 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. This eliminates downtime when you deploy your app. The traffic redirection is seamless, and no requests are dropped because of swap operations. You can automate this entire workflow by configuring auto swap when pre-swap validation isn't needed.
5+
* Validate app changes in a staging deployment slot before swapping it with the production slot.
6+
* Deploying an app to a slot first and then swapping it into production ensures that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your app. The traffic redirection is seamless, and no requests are dropped because of swap operations. You can automate this entire workflow by configuring auto swap when preswap validation isn't needed.
77
* After a swap, the previous production app is located in the staging slot. 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.
88

99
Each App Service plan tier supports a different number of deployment slots. There's no extra charge for using deployment slots. To find out the number of slots your app's tier supports, visit [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits).
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
In this exercise, you deploy a basic HTML+CSS site to Azure App Service with the Azure CLI **az webapp up** command. Next, you update the code and deploy the change to a staging slot. Finally, you swap the slots.
2+
3+
Tasks performed in this exercise:
4+
5+
* Download and deploy the sample app to Azure App Service.
6+
* Create a staging deployment slot.
7+
* Make a change to the sample app and deploy it to the staging slot.
8+
* Swap the staging and default production slots to move the changes to the production slot.
9+
10+
This exercise takes approximately **30** minutes to complete.
11+
12+
## Before you start
13+
14+
To complete the exercise, you need:
15+
16+
* An Azure subscription. If you don't already have one, you can sign up for one [https://azure.microsoft.com/](https://azure.microsoft.com/).
17+
18+
## Getting started
19+
20+
Select the **Launch Exercise** button, it opens the exercise instructions in a new browser window. When you're finished with the exercise, return here to:
21+
22+
> [!div class="checklist"]
23+
> * Complete the module
24+
> * Earn a badge for completing this module
25+
26+
<br/>
27+
28+
<a href="https://go.microsoft.com/fwlink/?linkid=2320044" target="_blank">
29+
<img src="../media/launch-exercise.png" alt="Button to launch exercise.">
30+
</a>
31+

learn-pr/wwl-azure/understand-app-service-deployment-slots/index.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ units:
4343
- learn.wwl.understand-app-service-deployment-slots.explore-staging-environments
4444
- learn.wwl.understand-app-service-deployment-slots.examine-slot-swapping
4545
- learn.wwl.understand-app-service-deployment-slots.swap
46+
- learn.wwl.exercise-swap-deployment-slots
4647
- learn.wwl.understand-app-service-deployment-slots.route-traffic
4748
- learn.wwl.understand-app-service-deployment-slots.knowledge-check
4849
- learn.wwl.understand-app-service-deployment-slots.summary
3.45 KB
Loading

0 commit comments

Comments
 (0)