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_M03_L08_Control_Deployments_using_Release_Gates.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ In this task, you will create two Azure web apps representing the **DevTest** an
147
147
148
148
#### Task 2: Configure an Application Insights resource
149
149
150
-
1. In the Azure portal, use the **Search resources, services, and docs** text box at the top of the page to search for **Application Insights** and, in the list of results, select **Application Insights**.
150
+
1. In the Azure portal, use the **Search resources, services, and docs** text box at the top of the page to search for **`Application Insights`** and, in the list of results, select **Application Insights**.
151
151
1. On the **Application Insights** blade, select **+ Create**.
152
152
1. On the **Application Insights** blade, on the **Basics** tab, specify the following settings (leave others with their default values):
153
153
@@ -203,9 +203,9 @@ In this task, you will set up the release tasks as part of the Release Pipeline.
203
203
1. Click **New Pipeline**.
204
204
1. From the **Select a template** window, **choose****Azure App Service Deployment** (Deploy your application to Azure App Service. Choose from Web App on Windows, Linux, containers, Function Apps, or WebJobs) under the **Featured** list of templates.
205
205
1. Click **Apply**.
206
-
1. From the **Stage** window appearing, update the default "Stage 1" Stage Name to **DevTest**. Close the popup window by using the **X** button. You are now in the graphical editor of the Release Pipeline, showing the DevTest Stage.
207
-
1. On the top of the page, rename the current pipeline from **New release pipeline** to **eshoponweb-cd**.
208
-
1. Hover the mouse over the DevTest Stage, and click the **Clone** button, to copy the DevTest Stage to an additional Stage. Name this Stage **Production**.
206
+
1. From the **Stage** window appearing, update the default "Stage 1" Stage Name to **`DevTest`**. Close the popup window by using the **X** button. You are now in the graphical editor of the Release Pipeline, showing the DevTest Stage.
207
+
1. On the top of the page, rename the current pipeline from **New release pipeline** to **`eshoponweb-cd`**.
208
+
1. Hover the mouse over the DevTest Stage, and click the **Clone** button, to copy the DevTest Stage to an additional Stage. Name this Stage **`Production`**.
209
209
210
210
> **Note**: The pipeline now contains two stages named **DevTest** and **Production**.
0 commit comments