Skip to content

Commit ccd5264

Browse files
authored
Update how-to-configure-customer-managed-keys.md
1 parent ed9a753 commit ccd5264

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/load-testing/how-to-configure-customer-managed-keys.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ You have to set the **Soft Delete** and **Purge Protection** properties on your
4848

4949
To learn how to create a key vault with the Azure portal, see [Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). When you create the key vault, select **Enable purge protection**, as shown in the following image.
5050

51-
:::image type="content" source="media/how-to-configure-customer-managed-keys/purge-protection-on-akv.png" alt-text="Screenshot that shows how to enable purge protection on a new key vault.":::
51+
:::image type="content" source="media/how-to-configure-customer-managed-keys/purge-protection-on-azure-key-vault.png" alt-text="Screenshot that shows how to enable purge protection on a new key vault.":::
5252

5353
To enable purge protection on an existing key vault, follow these steps:
5454

@@ -123,13 +123,13 @@ The user-assigned managed identity that you will use to configure customer-manag
123123

124124
1. From the Azure portal, go to the Azure Key Vault instance that you plan to use to host your encryption keys. Select **Access Policies** from the left menu:
125125

126-
:::image type="content" source="media/how-to-configure-customer-managed-keys/access-policies-akv.png" alt-text="Screenshot that shows access policies option in Azure Key Vault.":::
126+
:::image type="content" source="media/how-to-configure-customer-managed-keys/access-policies-azure-key-vault.png" alt-text="Screenshot that shows access policies option in Azure Key Vault.":::
127127

128128
1. Select **+ Add Access Policy**.
129129

130130
1. Under the **Key permissions** drop-down menu, select **Get**, **Unwrap Key**, and **Wrap Key** permissions:
131131

132-
:::image type="content" source="media/how-to-configure-customer-managed-keys/akv-permissions.png" alt-text="Screenshot that shows Azure Key Vault permissions.":::
132+
:::image type="content" source="media/how-to-configure-customer-managed-keys/azure-key-vault-permissions.png" alt-text="Screenshot that shows Azure Key Vault permissions.":::
133133

134134
1. Under **Select principal**, select **None selected**.
135135

@@ -159,7 +159,7 @@ To configure customer-managed keys for a new Azure Load Testing resource, follow
159159

160160
1. Select **Review + create** to validate and create the new resource.
161161

162-
:::image type="content" source="media/how-to-configure-customer-managed-keys/encryption-new-alt-resource.png" alt-text="Screenshot that shows how to enable customer managed key encryption while creating an Azure Load Testing resource.":::
162+
:::image type="content" source="media/how-to-configure-customer-managed-keys/encryption-new-azure-load-testing-resource.png" alt-text="Screenshot that shows how to enable customer managed key encryption while creating an Azure Load Testing resource.":::
163163

164164
# [PowerShell](#tab/powershell)
165165

@@ -275,7 +275,7 @@ You can change the managed identity for customer-managed keys for an existing Az
275275

276276
1. Save your changes.
277277

278-
:::image type="content" source="media/how-to-configure-customer-managed-keys/change-identity-existing-alt-resource.png" alt-text="Screenshot that shows how to change the managed identity for customer managed keys on an existing Azure Load Testing resource.":::
278+
:::image type="content" source="media/how-to-configure-customer-managed-keys/change-identity-existing-azure-load-testing-resource.png" alt-text="Screenshot that shows how to change the managed identity for customer managed keys on an existing Azure Load Testing resource.":::
279279

280280
> [!NOTE]
281281
> The selected managed identity should have access granted on the Azure Key Vault.

0 commit comments

Comments
 (0)