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_M07_Integrating_Azure_Key_Vault_with_Azure_DevOps.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ In this task, you will create a service principal by using the Azure CLI.
93
93
94
94
You will need a service principal to deploy an app to an Azure resource from Azure Pipelines. Since we are going to retrieve secrets in a pipeline, we will need to grant permission to the service when we create the Azure Key vault.
95
95
96
-
A service principal is automatically created by Azure Pipeline when you connect to an Azure subscription from inside a pipeline definition or when you create a new service connection from the project settings page. You can also manually create the service principal from the portal or using Azure CLI and re-use it across projects. It is recommended that you use an existing service principal when you want to have a pre-defined set of permissions.
96
+
A service principal is automatically created by Azure Pipeline when you connect to an Azure subscription from inside a pipeline definition or when you create a new service connection from the project settings page. You can also manually create the service principal from the portal or using Azure CLI and re-use it across projects. It is recommended that you use an existing service principal when you want to have a pre-bdefined set of permissions.
97
97
98
98
1. From the lab computer, start a web browser, navigate to the [**Azure Portal**](https://portal.azure.com), and sign in with the user account that has the Owner role in the Azure subscription you will be using in this lab and has the role of the Global Administrator in the Azure AD tenant associated with this subscription.
99
99
1. In the Azure portal, click the **Cloud Shell** icon, located directly to the right of the search textbox at the top of the page.
@@ -126,7 +126,7 @@ In this task, you will create an Azure Key vault by using the Azure portal.
126
126
For this lab scenario, we have an app that connects to a MySQL database. We intend to store the password for the MySQL database as a secret in the key vault.
127
127
128
128
1. In the Azure portal, in the **Search resources, services, and docs** text box, type **Key vaults** and press the **Enter** key.
129
-
1. On the **Key vaults** blade, click **+ Add**.
129
+
1. On the **Key vaults** blade, click **+ Create**.
130
130
1. On the **Basics** tab of the **Create key vault** blade, specify the following settings and click **Next: Access policy**:
131
131
132
132
| Setting | Value |
@@ -172,10 +172,10 @@ In this task, you will configure the Azure Pipeline to retrieve the secret from
172
172
1. On your lab computer, start a web browser and navigate to the Azure DevOps project **Integrating Azure Key Vault with Azure DevOps** you created in the previous exercise.
173
173
1. In the vertical navigational pane of the of the Azure DevOps portal, select **Pipelines** and verify that the **Pipelines** pane is displayed.
174
174
1. On the **Pipelines** pane, click the entry representing the **SmartHotel-CouponManagement-CI** pipeline. Click on **Edit**.
175
-
1. On the pipeline definition, modify the **Pipeline** > **Agent Specification** to **ubuntu 18.04**. Click **Save and Queue** > **Save and Run** to trigger a build.
176
-
1. In the vertical navigational pane of the of the Azure DevOps portal, in the **Pipelines** section, select **Releases**.
177
-
1. On the **SmartHotel-CouponManagement-CD** pane, click **Edit** in the upper right corner.
178
-
1. On the **All pipelines > SmartHotel-CouponManagement-CD** pane, select the **Task** tab and, in the dropdown menu, select **Dev**.
175
+
2. On the pipeline definition, make sure the **Pipeline** > **Agent Specification** is **ubuntu 18.04**. Click **Save and Queue** > **Queue** > **Run** to trigger a build.
176
+
3. In the vertical navigational pane of the of the Azure DevOps portal, in the **Pipelines** section, select **Releases**.
177
+
4. On the **SmartHotel-CouponManagement-CD** pane, click **Edit** in the upper right corner.
178
+
5. On the **All pipelines > SmartHotel-CouponManagement-CD** pane, select the **Task** tab and, in the dropdown menu, select **Dev**.
179
179
180
180
> **Note**: The release definition for **Dev** stage has an **Azure Key Vault** task. This task downloads *Secrets* from an Azure Key Vault. You will need to point to the subscription and the Azure Key Vault resource created earlier in the lab.
0 commit comments