Skip to content

Commit e325345

Browse files
authored
Merge pull request #190355 from JamesTran-MSFT/patch-93
Added KV note
2 parents 3d66c59 + f7e0522 commit e325345

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This article shows how to configure encryption with customer-managed keys stored
2525
2626
## Configure a key vault
2727

28-
You can use a new or existing key vault to store customer-managed keys. The storage account and the key vault must be in the same region, but they can be in different subscriptions. To learn more about Azure Key Vault, see [Azure Key Vault Overview](../../key-vault/general/overview.md) and [What is Azure Key Vault?](../../key-vault/general/basic-concepts.md).
28+
You can use a new or existing key vault to store customer-managed keys. The Storage Account and Key Vault can be in different regions or subscriptions in the same tenant. To learn more about Azure Key Vault, see [Azure Key Vault Overview](../../key-vault/general/overview.md) and [What is Azure Key Vault?](../../key-vault/general/basic-concepts.md).
2929

3030
Using customer-managed keys with Azure Storage encryption requires that both soft delete and purge protection be enabled for the key vault. Soft delete is enabled by default when you create a new key vault and cannot be disabled. You can enable purge protection either when you create the key vault or after it is created.
3131

0 commit comments

Comments
 (0)