Skip to content

Commit 90f3dd3

Browse files
committed
regions move to h2
1 parent cee877d commit 90f3dd3

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

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

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ 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+
> 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.
3030

3131
* Customer-managed keys can only be configured on new volumes. You can't migrate existing volumes to customer-managed key encryption.
3232
* 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
5151
* 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.
5252
* 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.
5353

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+
5462
## Requirements
63+
5564
Before creating your first customer-managed key volume, you must have set up:
5665
* An [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
5766
* The key vault must have soft delete and purge protection enabled.

0 commit comments

Comments
 (0)