Skip to content

Commit eb6347b

Browse files
committed
tweaks
1 parent 796102f commit eb6347b

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

articles/storage/common/customer-managed-keys-configure-key-vault.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,9 @@ If you want to use an existing key vault, you'll need to enable purge protection
4545

4646
1. Navigate to your key vault in the Azure portal.
4747

48-
2. Under **Settings**, choose **Properties**.
48+
1. Under **Settings**, choose **Properties**.
4949

50-
3. In the **Purge protection** section, choose **Enable purge protection**.
50+
1. In the **Purge protection** section, choose **Enable purge protection**.
5151

5252
### [PowerShell](#tab/powershell)
5353

articles/storage/common/customer-managed-keys-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: storage
66
author: tamram
77

88
ms.service: storage
9-
ms.date: 08/26/2021
9+
ms.date: 01/13/2022
1010
ms.topic: conceptual
1111
ms.author: tamram
1212
ms.reviewer: ozgun
@@ -29,17 +29,17 @@ You can either create your own keys and store them in the key vault or managed H
2929
3030
## About customer-managed keys
3131

32-
The following diagram shows how Azure Storage uses Azure Active Directory and a key vault or managed HSM to make requests using the customer-managed key:
32+
The following diagram shows how Azure Storage uses Azure AD and a key vault or managed HSM to make requests using the customer-managed key:
3333

3434
![Diagram showing how customer-managed keys work in Azure Storage](media/customer-managed-keys-overview/encryption-customer-managed-keys-diagram.png)
3535

3636
The following list explains the numbered steps in the diagram:
3737

3838
1. An Azure Key Vault admin grants permissions to encryption keys to either a user-assigned managed identity, or the system-assigned managed identity that's associated with the storage account.
39-
2. An Azure Storage admin configures encryption with a customer-managed key for the storage account.
40-
3. Azure Storage uses the managed identity that was used by the Azure Key Vault admin in step one to authenticate access to Azure Key Vault via Azure Active Directory.
41-
4. Azure Storage wraps the account encryption key with the customer-managed key in Azure Key Vault.
42-
5. For read/write operations, Azure Storage sends requests to Azure Key Vault to unwrap the account encryption key to perform encryption and decryption operations.
39+
1. An Azure Storage admin configures encryption with a customer-managed key for the storage account.
40+
1. Azure Storage uses the managed identity to which the Azure Key Vault admin granted permissions in step 1 to authenticate access to Azure Key Vault via Azure AD.
41+
1. Azure Storage wraps the account encryption key with the customer-managed key in Azure Key Vault.
42+
1. For read/write operations, Azure Storage sends requests to Azure Key Vault to unwrap the account encryption key to perform encryption and decryption operations.
4343

4444
The managed identity that's associated with the storage account must have these permissions at a minimum to access a customer-managed key in Azure Key Vault:
4545

@@ -65,7 +65,7 @@ When you configure a customer-managed key, Azure Storage wraps the root data enc
6565

6666
When you enable or disable customer managed keys, or when you modify the key or the key version, the protection of the root encryption key changes, but the data in your Azure Storage account does not need to be re-encrypted.
6767

68-
Customer-managed keys can enabled on both existing storage accounts or new accounts as you create them. If you plan to enable customer-managed keys while creating an account, only user-assigned managed identities will be available. To use a system-assigned managed identity, you'll have to create the account first, and then enable customer-managed keys. That's because the system-assigned managed identity can exist only after the account is created.
68+
You can enable customer-managed keys on existing storage accounts or on new accounts when you create them. When you enable customer-managed keys while creating an account, only user-assigned managed identities are available. To use a system-assigned managed identity, you must first create the account and then enable customer-managed keys, because the system-assigned managed identity can exist only after the account is created.
6969

7070
You can switch between customer-managed keys and Microsoft-managed keys at any time. For more information about Microsoft-managed keys, see [About encryption key management](storage-service-encryption.md#about-encryption-key-management).
7171

0 commit comments

Comments
 (0)