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
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-configure-customer-managed-keys.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ You have to set the **Soft Delete** and **Purge Protection** properties on your
48
48
49
49
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.
50
50
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.":::
52
52
53
53
To enable purge protection on an existing key vault, follow these steps:
54
54
@@ -123,13 +123,13 @@ The user-assigned managed identity that you will use to configure customer-manag
123
123
124
124
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:
125
125
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.":::
127
127
128
128
1. Select **+ Add Access Policy**.
129
129
130
130
1. Under the **Key permissions** drop-down menu, select **Get**, **Unwrap Key**, and **Wrap Key** permissions:
131
131
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.":::
133
133
134
134
1. Under **Select principal**, select **None selected**.
135
135
@@ -159,7 +159,7 @@ To configure customer-managed keys for a new Azure Load Testing resource, follow
159
159
160
160
1. Select **Review + create** to validate and create the new resource.
161
161
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.":::
163
163
164
164
# [PowerShell](#tab/powershell)
165
165
@@ -275,7 +275,7 @@ You can change the managed identity for customer-managed keys for an existing Az
275
275
276
276
1. Save your changes.
277
277
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.":::
279
279
280
280
> [!NOTE]
281
281
> The selected managed identity should have access granted on the Azure Key Vault.
0 commit comments