You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 21, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md
+2-21Lines changed: 2 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,25 +52,6 @@ After you complete this lab, you will be able to:
52
52
53
53
## Instructions
54
54
55
-
### Before you start
56
-
57
-
#### Sign in to the lab virtual machine
58
-
59
-
Ensure that you're signed in to your Windows 10 computer by using the following credentials:
60
-
61
-
- Username: **Student**
62
-
- Password: **Pa55w.rd**
63
-
64
-
#### Review applications required for this lab
65
-
66
-
Identify the applications that you'll use in this lab:
67
-
68
-
- Microsoft Edge
69
-
70
-
#### Set up an Azure DevOps organization.
71
-
72
-
If you don't already have an Azure DevOps organization that you can use for this lab, create one by following the instructions available at [Create an organization or project collection](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops).
73
-
74
55
### Exercise 0: Configure the lab prerequisites
75
56
76
57
In this exercise, you will set up the prerequisites for the lab, which consist of a new Azure DevOps project with a repository based on the [eShopOnWeb](https://dev.azure.com/unhueteb/_git/eshopweb-az400).
@@ -300,7 +281,7 @@ In this task, you will enable the post-deployment gate for the Canary Environmen
300
281
1. Close the **Post-deployment conditions** pane, by clicking the **x** mark in its upper right corner.
301
282
1. Back on the **New Release Pipeline** pane, click **Save**, and in the **Save** dialog box, click **OK**.
302
283
303
-
### Exercise 3: Test release gates
284
+
### Exercise 4: Test release gates
304
285
305
286
In this exercise, you will test the release gates by updating the application, which will trigger a deployment.
306
287
@@ -325,7 +306,7 @@ In this task, you will track the release process with the release gates enabled.
325
306
326
307
1. Wait another 3 minutes and validate the status of the Release Gates again. As it is now +8 minutes after the initial Release Gates got checked, and it's been more than 8 minutes since the initial Application Insight Alert got triggered with action "Fired", it should result in a successful Release Gate, having allowed the deployment of the Production Release Stage as well.
327
308
328
-
### Exercise 4: Remove the Azure lab resources
309
+
### Exercise 5: Remove the Azure lab resources
329
310
330
311
In this exercise, you will remove the Azure resources provisioned in this lab to eliminate unexpected charges.
0 commit comments