You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/configure-customer-managed-keys.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,9 @@ Customer-managed keys in Azure NetApp Files volume encryption enable you to use
24
24
## Considerations
25
25
26
26
> [!IMPORTANT]
27
-
> The customer-manged keys feature is currently in preview. The program is controlled via Azure Feature Exposure Control (AFEC). To access this preview program, contact your account team.
28
-
>
29
-
> During preview, customer-managed keys are available only in the **East Asia**, **East US 2**, and **West Europe**regions.
27
+
> The Azure NetApp Files customer-manged keys feature is currently in preview. To access this preview program, contact your account team. Wait for an official confirmation email from the Azure NetApp Files team before using customer-managed keys.
28
+
29
+
The Azure NetApp Files backup feature is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files Backup Public Preview](https://aka.ms/anfbackuppreviewsignup)**page.
30
30
31
31
* Customer-managed keys can only be configured on new volumes. You can't migrate existing volumes to customer-managed key encryption.
32
32
* To create a volume using customer-managed keys, you must select the *Standard* network features. You can't use customer-managed key volumes with volume configured using Basic network features. Follow instructions in to [Set the Network Features option](configure-network-features.md#set-the-network-features-option) in the volume creation page.
@@ -51,7 +51,16 @@ Customer-managed keys in Azure NetApp Files volume encryption enable you to use
51
51
* Applying Azure network security groups on the private link subnet to Azure Key Vault isn't supported for Azure NetApp Files customer-managed keys. Network security groups don't affect connectivity to Private Link unless `Private endpoint network policy` is enabled on the subnet. It's recommended to keep this option disabled.
52
52
* If Azure NetApp Files fails to create a customer-managed key volume, error messages are displayed. Refer to the [Error messages and troubleshooting](#error-messages-and-troubleshooting) section for more information.
53
53
54
+
## Supported regions
55
+
56
+
Azure NetApp Files customer-managed keys is supported for the following regions:
57
+
58
+
* East Asia
59
+
* East US 2
60
+
* West Europe
61
+
54
62
## Requirements
63
+
55
64
Before creating your first customer-managed key volume, you must have set up:
56
65
* An [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
57
66
* The key vault must have soft delete and purge protection enabled.
0 commit comments