Skip to content

Commit dc4bd89

Browse files
Update customer-managed-keys-configure-key-vault.md
1 parent 52fd546 commit dc4bd89

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,8 @@ This article shows how to configure encryption with customer-managed keys stored
2424
> Azure Key Vault and Azure Key Vault Managed HSM support the same APIs and management interfaces for configuration.
2525
2626
## Configure a key vault
27-
> [!NOTE]
28-
> There's no longer a restriction for the storage account and key vault to be in the same region or subscription.
2927

30-
You can use a new or existing key vault to store customer-managed keys. 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. 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).
3129

3230
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.
3331

0 commit comments

Comments
 (0)