Skip to content

Commit 33ef7e1

Browse files
Merge pull request #228065 from b-ahibbard/anf-cmk-preview
Anf cmk preview
2 parents 1359fa0 + 7724b56 commit 33ef7e1

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

articles/azure-netapp-files/configure-customer-managed-keys.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,7 @@ Customer-managed keys in Azure NetApp Files volume encryption enable you to use
2424
## Considerations
2525

2626
> [!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+
> Customer-managed keys for Azure NetApp Files volume encryption is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Customer-managed keys for Azure NetApp Files volume encryption](https://aka.ms/anfcmkpreviewsignup)** page. Wait for an official confirmation email from the Azure NetApp Files team before using customer-managed keys.
3028
3129
* Customer-managed keys can only be configured on new volumes. You can't migrate existing volumes to customer-managed key encryption.
3230
* 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 +49,16 @@ Customer-managed keys in Azure NetApp Files volume encryption enable you to use
5149
* 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.
5250
* 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.
5351

52+
## Supported regions
53+
54+
Azure NetApp Files customer-managed keys is supported for the following regions:
55+
56+
* East Asia
57+
* East US 2
58+
* West Europe
59+
5460
## Requirements
61+
5562
Before creating your first customer-managed key volume, you must have set up:
5663
* An [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
5764
* The key vault must have soft delete and purge protection enabled.

0 commit comments

Comments
 (0)