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
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,6 +104,7 @@ Before creating your first customer-managed key volume, you must set up:
104
104
* The key must be of type RSA.
105
105
* The key vault must have an [Azure Private Endpoint](../private-link/private-endpoint-overview.md).
106
106
* The private endpoint must reside in a different subnet than the one delegated to Azure NetApp Files. The subnet must be in the same VNet as the one delegated to Azure NetApp.
107
+
* You must register the feature before you can use customer-managed keys.
107
108
108
109
For more information about Azure Key Vault and Azure Private Endpoint, refer to:
109
110
*[Quickstart: Create a key vault ](../key-vault/general/quick-create-portal.md)
@@ -113,6 +114,26 @@ For more information about Azure Key Vault and Azure Private Endpoint, refer to:
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
136
+
116
137
## Configure a NetApp account to use customer-managed keys
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/create-cross-zone-replication.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Cross-zone replication is currently in preview. You need to register the feature
40
40
2. Check the status of the feature registration:
41
41
42
42
> [!NOTE]
43
-
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to`Registered`. Wait until the status is **Registered** before continuing.
43
+
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to`Registered`. Wait until the status is **Registered** before continuing.
0 commit comments