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_M05_L10_Integrating_Azure_Key_Vault_with_Azure_DevOps.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Azure Key Vault provides secure storage and management of sensitive data, such a
22
22
23
23
In this lab, you will see how you can integrate Azure Key Vault with an Azure Pipelines by using the following steps:
24
24
25
-
- Create an Azure Key vault to store a ACR password as a secret.
25
+
- Create an Azure Key Vault to store a ACR password as a secret.
26
26
- Create an Azure Service Principal to provide access to secrets in the Azure Key Vault.
27
27
- Configure permissions to allow the Service Principal to read the secret.
28
28
- Configure pipeline to retrieve the password from the Azure Key Vault and pass it on to subsequent tasks.
@@ -120,7 +120,7 @@ A Service Principal is automatically created by Azure Pipelines, when you connec
120
120
121
121
9. Fill in the empty fields using the information gathered during previous steps:
122
122
- Subscription Id and Name.
123
-
- Service Principal Id (or clientId), Key (or Password) and TenantId.
123
+
- Service Principal Id (appId), Service principal key (password) and Tenant ID (tenant).
124
124
- In **Service connection name**type**azure subs**. This name will be referenced in YAML pipelines when needing an Azure DevOps Service Connection to communicate with your Azure subscription.
125
125
126
126

@@ -158,15 +158,15 @@ In this task, you will import an existing CI YAML pipeline definition, modify an
158
158
159
159

160
160
161
-
#### Task 2: Create an Azure Key vault
161
+
#### Task 2: Create an Azure Key Vault
162
162
163
-
In this task, you will create an Azure Key vault by using the Azure portal.
163
+
In this task, you will create an Azure Key Vault by using the Azure portal.
164
164
165
-
For this lab scenario, we will have a Azure Container Instance (ACI) that pull and runs a container image stored in Azure Container Registry (ACR). We intend to store the password forthe ACR as a secretin the key vault.
165
+
For this lab scenario, we will have a Azure Container Instance (ACI) that pulls and runs a container image stored in Azure Container Registry (ACR). We intend to store the password forthe ACR as a secretin the key vault.
166
166
167
167
1. In the Azure portal, in the **Search resources, services, and docs** text box, type**Key vault** and press the **Enter** key.
168
168
2. Select **Key vault** blade, click on **Create>Key Vault**.
169
-
3. On the **Basics** tab of the **Create key vault** blade, specify the following settings and click on **Next**:
169
+
3. On the **Basics** tab of the **Create a key vault** blade, specify the following settings and click on **Next**:
170
170
171
171
| Setting | Value |
172
172
| --- | --- |
@@ -178,20 +178,20 @@ For this lab scenario, we will have a Azure Container Instance (ACI) that pull a
178
178
| Days to retain deleted vaults |**7**|
179
179
| Purge protection |**Disable purge protection**|
180
180
181
-
4. On the **Access policy** tab of the **Create key vault** blade, on the **Access Policy** section, click on **+ Create** to setup a new policy.
181
+
4. On the **Access configuration** tab of the **Create a key vault** blade, select**Vault access policy** and theninthe **Access policies** section, click on **+ Create** to setup a new policy.
182
182
183
183
>**Note**: You need to secure access to your key vaults by allowing only authorized applications and users. To access the data from the vault, you will need to provide read (Get/List) permissions to the previously created service principal that you will be using forauthenticationin the pipeline.
184
184
185
-
1. On the **Permission** blade, check**Get** and**List**permissions below **Secret Permission**. Click on **Next**.
186
-
2. on the **Principal** blade, search for the **previously created Service Principal**, either using the Id or Name given. Click on **Next** and **Next** again.
185
+
1. On the **Permission** blade, below**Secret permissions**, check**Get**and **List** permissions. Click on **Next**.
186
+
2. On the **Principal** blade, search for the **previously created Service Principal**, either by using the Id or Name given, and selectit from the list. Click on **Next**, **Next**, **Create** (access policy).
187
187
3. On the **Review + create** blade, click on **Create**
188
188
189
-
5. Back on the **Create a Key Vault** blade, click on **Review + Create > Create**
189
+
5. Back on the **Create a key vault** blade, click on **Review + Create > Create**
190
190
191
-
>**Note**: Wait for the Azure Key vault to be provisioned. This should take less than 1 minute.
191
+
>**Note**: Wait for the Azure Key Vault to be provisioned. This should take less than 1 minute.
192
192
193
193
6. On the **Your deployment is complete** blade, click on **Go to resource**.
194
-
7. On the Azure Key vault blade, in the vertical menu on the left side of the blade, in the **Objects** section, click on **Secrets**.
194
+
7. On the Azure Key Vault (ewebshop-kv-NAME) blade, in the vertical menu on the left side of the blade, in the **Objects** section, click on **Secrets**.
195
195
8. On the **Secrets** blade, click on **Generate/Import**.
196
196
9. On the **Create a secret** blade, specify the following settings and click on **Create** (leave others with their default values):
197
197
@@ -203,7 +203,7 @@ For this lab scenario, we will have a Azure Container Instance (ACI) that pull a
203
203
204
204
#### Task 3: Create a Variable Group connected to Azure Key Vault
205
205
206
-
In this task, you will create a Variable Group in Azure DevOps that will retrieve the ACR password secret from Key Vault using the Service Connection (Service Principal)
206
+
In this task, you will create a Variable Group in Azure DevOps that will retrieve the ACR password secret from Key Vault using the Service Connection (Service Principal).
207
207
208
208
1. On your lab computer, start a web browser and navigate to the Azure DevOps project **eShopOnWeb**.
209
209
@@ -214,7 +214,7 @@ In this task, you will create a Variable Group in Azure DevOps that will retriev
214
214
| Setting | Value |
215
215
| --- | --- |
216
216
| Variable Group Name |**eshopweb-vg**|
217
-
| Link secrets from Azure KV ...|**enable**|
217
+
| Link secrets from an Azure Key Vault|**enable**|
218
218
| Azure subscription |**Available Azure service connection > Azure subs**|
219
219
| Key vault name | Your key vault name|
220
220
@@ -223,9 +223,9 @@ In this task, you will create a Variable Group in Azure DevOps that will retriev
223
223
224
224

225
225
226
-
#### Task 4: Setup CD Pipeline to deploy container in Azure Container Instance(ACI)
226
+
#### Task 4: Setup CD Pipeline to deploy container in Azure Container Instance(ACI)
227
227
228
-
In this task, you will import a CD pipeline, customize it and run it fordeploying the container image created beforein a Azure Container Instance.
228
+
In this task, you will import a CD pipeline, customize it, and run it fordeploying the container image created beforein a Azure Container Instance.
229
229
230
230
1. From the lab computer, start a web browser, navigate to the Azure DevOps **eShopOnWeb** project. Go to **Pipelines>Pipelines** and click on **New Pipeline**.
231
231
@@ -265,6 +265,6 @@ In this task, you will use Azure Cloud Shell to remove the Azure resources provi
265
265
266
266
In this lab, you integrated Azure Key Vault with an Azure DevOps pipeline by using the following steps:
267
267
268
-
- Created an Azure service principal to provide access to secrets in the Azure Key vault and authenticate deployment to Azure from Azure DevOps.
269
-
- Run 2 YAML pipelines imported from a Git repository.
270
-
- Configured pipeline to retrieve the password from the Azure Key vault using ADO Variable Group and use it on subsequent tasks.
268
+
- Created an Azure service principal to provide access to an Azure Key Vault secret and authenticate deployment to Azure from Azure DevOps.
269
+
- Ran two YAML pipelines imported from a Git repository.
270
+
- Configured one pipeline to retrieve the password from Azure Key Vault using a Variable Group and use it on subsequent tasks.
0 commit comments