Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Commit a8f56b8

Browse files
authored
Merge pull request #468 from mkennten/patch-3
Changed instructions to reflect latest UI changes for Key vault creation
2 parents a91b059 + 16d5ec5 commit a8f56b8

1 file changed

Lines changed: 19 additions & 19 deletions

File tree

Instructions/Labs/AZ400_M05_L10_Integrating_Azure_Key_Vault_with_Azure_DevOps.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Azure Key Vault provides secure storage and management of sensitive data, such a
2222

2323
In this lab, you will see how you can integrate Azure Key Vault with an Azure Pipelines by using the following steps:
2424

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.
2626
- Create an Azure Service Principal to provide access to secrets in the Azure Key Vault.
2727
- Configure permissions to allow the Service Principal to read the secret.
2828
- 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
120120

121121
9. Fill in the empty fields using the information gathered during previous steps:
122122
- 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).
124124
- 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.
125125

126126
![Azure Service Connection](images/azure-service-connection.png)
@@ -158,15 +158,15 @@ In this task, you will import an existing CI YAML pipeline definition, modify an
158158

159159
![ACR password](images/acr-password.png)
160160

161-
#### Task 2: Create an Azure Key vault
161+
#### Task 2: Create an Azure Key Vault
162162

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.
164164

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 for the ACR as a secret in 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 for the ACR as a secret in the key vault.
166166

167167
1. In the Azure portal, in the **Search resources, services, and docs** text box, type **Key vault** and press the **Enter** key.
168168
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**:
170170

171171
| Setting | Value |
172172
| --- | --- |
@@ -178,20 +178,20 @@ For this lab scenario, we will have a Azure Container Instance (ACI) that pull a
178178
| Days to retain deleted vaults | **7** |
179179
| Purge protection | **Disable purge protection** |
180180

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 then in the **Access policies** section, click on **+ Create** to setup a new policy.
182182

183183
> **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 for authentication in the pipeline.
184184

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 select it from the list. Click on **Next**, **Next**, **Create** (access policy).
187187
3. On the **Review + create** blade, click on **Create**
188188

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**
190190

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.
192192

193193
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**.
195195
8. On the **Secrets** blade, click on **Generate/Import**.
196196
9. On the **Create a secret** blade, specify the following settings and click on **Create** (leave others with their default values):
197197

@@ -203,7 +203,7 @@ For this lab scenario, we will have a Azure Container Instance (ACI) that pull a
203203

204204
#### Task 3: Create a Variable Group connected to Azure Key Vault
205205

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).
207207

208208
1. On your lab computer, start a web browser and navigate to the Azure DevOps project **eShopOnWeb**.
209209

@@ -214,7 +214,7 @@ In this task, you will create a Variable Group in Azure DevOps that will retriev
214214
| Setting | Value |
215215
| --- | --- |
216216
| Variable Group Name | **eshopweb-vg** |
217-
| Link secrets from Azure KV ... | **enable** |
217+
| Link secrets from an Azure Key Vault | **enable** |
218218
| Azure subscription | **Available Azure service connection > Azure subs** |
219219
| Key vault name | Your key vault name|
220220

@@ -223,9 +223,9 @@ In this task, you will create a Variable Group in Azure DevOps that will retriev
223223

224224
![Variable Group create](images/vg-create.png)
225225

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)
227227

228-
In this task, you will import a CD pipeline, customize it and run it for deploying the container image created before in a Azure Container Instance.
228+
In this task, you will import a CD pipeline, customize it, and run it for deploying the container image created before in a Azure Container Instance.
229229

230230
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**.
231231

@@ -265,6 +265,6 @@ In this task, you will use Azure Cloud Shell to remove the Azure resources provi
265265

266266
In this lab, you integrated Azure Key Vault with an Azure DevOps pipeline by using the following steps:
267267

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

Comments
 (0)