Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 8d4e1f6

Browse files
committedDec 3, 2020
add portal steps
1 parent 7add4c8 commit 8d4e1f6

File tree

3 files changed

+15
-13
lines changed

3 files changed

+15
-13
lines changed
 

‎articles/container-registry/container-registry-customer-managed-keys.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Encrypt registry with a customer-managed key
33
description: Learn about encryption-at-rest of your Azure container registry, and how to encrypt your Premium registry with a customer-managed key stored in Azure Key Vault
44
ms.topic: article
5-
ms.date: 11/17/2020
5+
ms.date: 12/03/2020
66
ms.custom:
77
---
88

@@ -41,9 +41,6 @@ When you configure registry encryption with a customer-managed key, you have two
4141

4242
* **Manually update the key version** - To use a specific version of a key for registry encryption, specify that key version when you enable registry encryption with a customer-managed key. When a registry is encrypted with a specific key version, Azure Container Registry uses that version for encryption until you manually rotate the customer-managed key.
4343

44-
> [!NOTE]
45-
> Currently you can only use the Azure CLI to configure the registry to automatically update the customer-managed key version. When using the portal to enable encryption, you must manually update the key version.
46-
4744
For details, see [Choose key ID with or without key version](#choose-key-id-with-or-without-key-version) and [Update key version](#update-key-version), later in this article.
4845

4946
## Prerequisites
@@ -247,7 +244,7 @@ You use the identity's name in later steps.
247244

248245
### Create a key vault
249246

250-
For steps to create a key vault, see [Quickstart: Create an Azure Key Vault with the Azure portal](../key-vault/general/quick-create-portal.md).
247+
For steps to create a key vault, see [Quickstart: Set and retrieve a secret from Azure Key Vault using the Azure portal](../key-vault/secrets/quick-create-portal.md).
251248

252249
When creating a key vault for a customer-managed key, in the **Basics** tab, enable the **Purge protection** setting. This setting helps prevent data loss caused by accidental key or key vault deletions.
253250

@@ -274,24 +271,28 @@ Alternatively, use [Azure RBAC for Key Vault](../key-vault/general/rbac-guide.md
274271
1. Assign access to **User assigned managed identity**.
275272
1. Select the resource name of your user-assigned managed identity, and select **Save**.
276273

277-
### Create key
274+
### Create key (optional)
275+
276+
Optionally create a key in the key vault for use to encrypt the registry. Follow these steps if you want to select a specific key version as a customer-managed key.
278277

279278
1. Navigate to your key vault.
280279
1. Select **Settings** > **Keys**.
281280
1. Select **+Generate/Import** and enter a unique name for the key.
282281
1. Accept the remaining default values and select **Create**.
283-
1. After creation, select the key and take note of the current key version.
282+
1. After creation, select the key and then select the current version. Copy the **Key identifier** for the key version.
284283

285284
### Create Azure container registry
286285

287286
1. Select **Create a resource** > **Containers** > **Container Registry**.
288287
1. In the **Basics** tab, select or create a resource group, and enter a registry name. In **SKU**, select **Premium**.
289288
1. In the **Encryption** tab, in **Customer-managed key**, select **Enabled**.
290289
1. In **Identity**, select the managed identity you created.
291-
1. In **Encryption**, select **Select from Key Vault**.
292-
1. In the **Select key from Azure Key Vault** window, select the key vault, key, and version you created in the preceding section.
290+
1. In **Encryption**, do one of the following:
291+
1. To provide a non-versioned key that enables automatic updates of key versions, select **Select from Key Vault**, and then select a new key.
292+
In the **Select key from Azure Key Vault** window, select an existing key vault and key, or **Create new**.
293+
1. To provide a versioned key, which doesn't support automatic updates of key values, select **Enter key URI**. Provide the key identifier of a versioned key.
293294
1. In the **Encryption** tab, select **Review + create**.
294-
1. Select **Create** to create the registry instance.
295+
1. Select **Create** to deploy the registry instance.
295296

296297
:::image type="content" source="media/container-registry-customer-managed-keys/create-encrypted-registry.png" alt-text="Create encrypted registry in the Azure portal":::
297298

@@ -493,11 +494,12 @@ For example, to configure a new key:
493494

494495
1. In the portal, navigate to your registry.
495496
1. Under **Settings**, select **Encryption** > **Change key**.
496-
1. Select **Select key**.
497497

498498
:::image type="content" source="media/container-registry-customer-managed-keys/rotate-key.png" alt-text="Rotate key in the Azure portal":::
499-
1. In the **Select key from Azure Key Vault** window, select the key vault and key you configured previously, and in **Version**, select **Create new**.
500-
1. In the **Create a key** window, select **Generate**, and then **Create**.
499+
1. In **Encryption**, do one of the following:
500+
1. To provide a non-versioned key that enables automatic updates of key versions, select **Select from Key Vault**, and then select a new key.
501+
In the **Select key from Azure Key Vault** window, select an existing key vault and key, or **Create new**.
502+
1. To provide a versioned key, which doesn't support automatic updates of key values, select **Enter key URI**. Provide the key identifier of a versioned key.
501503
1. Complete the key selection and select **Save**.
502504

503505
## Revoke key
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.