Skip to content

Commit 66ea616

Browse files
authored
Update information about key vault requirements
1 parent b6fb31c commit 66ea616

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

articles/ai-services/openai/encrypt-data-at-rest.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: mrbullwinkle
66
manager: nitinme
77
ms.service: azure-ai-openai
88
ms.topic: conceptual
9-
ms.date: 11/14/2022
9+
ms.date: 2/14/2024
1010
ms.author: mbullwin
1111
---
1212

@@ -22,17 +22,22 @@ Azure OpenAI is part of Azure AI services. Azure AI services data is encrypted a
2222

2323
By default, your subscription uses Microsoft-managed encryption keys. There's also the option to manage your subscription with your own keys called customer-managed keys (CMK). CMK offers greater flexibility to create, rotate, disable, and revoke access controls. You can also audit the encryption keys used to protect your data.
2424

25-
## Customer-managed keys with Azure Key Vault
25+
## Use customer-managed keys with Azure Key Vault
2626

2727
Customer-managed keys (CMK), also known as Bring your own key (BYOK), offer greater flexibility to create, rotate, disable, and revoke access controls. You can also audit the encryption keys used to protect your data.
2828

2929
You must use Azure Key Vault to store your customer-managed keys. You can either create your own keys and store them in a key vault, or you can use the Azure Key Vault APIs to generate keys. The Azure AI services resource and the key vault must be in the same region and in the same Microsoft Entra tenant, but they can be in different subscriptions. For more information about Azure Key Vault, see [What is Azure Key Vault?](../../key-vault/general/overview.md).
3030

31-
To enable customer-managed keys, you must also enable both the **Soft Delete** and **Do Not Purge** properties on the key vault.
31+
To enable customer-managed keys, the key vault containing your keys must meet these requirements:
3232

33-
Only RSA keys of size 2048 are supported with Azure AI services encryption. For more information about keys, see **Key Vault keys** in [About Azure Key Vault keys, secrets and certificates](../../key-vault/general/about-keys-secrets-certificates.md).
33+
- You must enable both the **Soft Delete** and **Do Not Purge** properties on the key vault.
34+
- If you use the [Key Vault firewall](/azure/key-vault/general/access-behind-firewall), you must allow trusted Microsoft services to access the key vault.
35+
- The key vault must use [legacy access policies](/azure/key-vault/general/assign-access-policy).
36+
- You must grant the Azure OpenAI resource's system-assigned managed identity the following permissions to keys: get key, wrap key, unwrap key.
3437

35-
## Enable customer-managed keys for your resource
38+
Only RSA and RSA-HSM keys of size 2048 are supported with Azure AI services encryption. For more information about keys, see **Key Vault keys** in [About Azure Key Vault keys, secrets and certificates](../../key-vault/general/about-keys-secrets-certificates.md).
39+
40+
## Enable customer-managed keys on your Azure OpenAI resource
3641

3742
To enable customer-managed keys in the Azure portal, follow these steps:
3843

@@ -67,9 +72,9 @@ To specify a key as a URI, follow these steps:
6772
1. Under **Subscription**, select the subscription that contains the key vault.
6873
1. Save your changes.
6974

70-
### Specify a key from a key vault
75+
### Select a key from a key vault
7176

72-
To specify a key from a key vault, first make sure that you have a key vault that contains a key. Then follow these steps:
77+
To select a key from a key vault, first make sure that you have a key vault that contains a key. Then follow these steps:
7378

7479
1. Go to your Azure AI services resource, and then select **Encryption**.
7580
1. Under **Encryption key**, select **Select from Key Vault**.

0 commit comments

Comments
 (0)