Skip to content

Commit 6b742d5

Browse files
committed
fix typo
1 parent 8e1396e commit 6b742d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,7 @@ The following diagram demonstrates how customer-managed keys work with Azure Net
4040
4141
* Customer-managed keys can only be configured on new volumes. You can't migrate existing volumes to customer-managed key encryption.
4242
* 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.
43+
* Customer-managed keys private endpoints do not support the **Disable public access** option. You must choose one of the **Allow public access** options.
4344
* Switching from user-assigned identity to the system-assigned identity isn't currently supported.
4445
* MSI Automatic certificate renewal isn't currently supported.
4546
* The MSI certificate has a lifetime of 90 days. It becomes eligible for renewal after 46 days. **After 90 days, the certificate is no longer be valid and the customer-managed key volumes under the NetApp account will go offline.**
@@ -53,7 +54,6 @@ The following diagram demonstrates how customer-managed keys work with Azure Net
5354
* 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.
5455
* 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.
5556
* Currently, customer-managed keys can't be configured while creating data replication volumes to establish an Azure NetApp Files cross-region replication or cross-zone replication relationship.
56-
* Customer-managed keys do not support the **Disable public access** option with firewalls and virtue networks. You must choose one of the **Allow public access** options.
5757

5858
## Supported regions
5959

0 commit comments

Comments
 (0)