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

Commit 9ffb33d

Browse files
authored
Merge pull request #311 from v-asamim/lab13-fixes-sam
LAB13: Instructions updates (Exercise 1, Task 2, Steps 4,5,7,10)
2 parents 10ed910 + cd2e4d8 commit 9ffb33d

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

Instructions/Labs/AZ400_M05_L13_Integrating_Azure_Key_Vault_with_Azure_DevOps.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -124,22 +124,22 @@ For this lab scenario, we have an app that connects to a MySQL database. We inte
124124
| Days to retain deleted vaults | **7** |
125125
| Purge protection | **Disable purge protection** |
126126
127-
1. On the **Access policy** tab of the **Create key vault** blade, click **+ Add Access Policy** to setup a new policy.
127+
1. On the **Access policy** tab of the **Create key vault** blade, click **+ Create** to setup a new policy.
128128
129129
> **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) permissions to the service principal that you will be using for authentication in the pipeline.
130130
131-
1. On the **Add access policy** blade, click the **None selected** link directly under the **Select principal** label.
131+
1. On the **Create an access policy** blade, click the **None selected** link directly under the **Select principal** label.
132132
1. On the **Principal** blade, search for the security principal that you created in the previous exercise, select it, and then click **Select**.
133133
134134
> **Note**: You can search by name or ID of the principal.
135135
136-
1. Back on the **Add access policy** blade, in the **Secret permissions** drop down list, select checkboxes next to the **Get** and **List** permissions and then click **Add**.
136+
1. Back on the **Create an access policy** blade, in the **Secret permissions** drop down list, select checkboxes next to the **Get** and **List** permissions and then click **Add**.
137137
1. Back on the **Access policy** tab of the **Create key vault** blade, click **Review + create** and, on the **Review + create** blade, click **Create**.
138138
139139
> **Note**: Wait for the Azure Key vault to be provisioned. This should take less than 1 minute.
140140
141141
1. On the **Your deployment is complete** blade, click **Go to resource**.
142-
1. On the Azure Key vault blade, in the vertical menu on the left side of the blade, in the **Settings** section, click **Secrets**.
142+
1. On the Azure Key vault blade, in the vertical menu on the left side of the blade, in the **Objects** section, click **Secrets**.
143143
1. On the **Secrets** blade, click **Generate/Import**.
144144
1. On the **Create a secret** blade, specify the following settings and click **Create** (leave others with their default values):
145145

0 commit comments

Comments
 (0)