Skip to content

Commit 251c0f2

Browse files
committed
remove afec
1 parent 74f9ae4 commit 251c0f2

File tree

2 files changed

+3
-23
lines changed

2 files changed

+3
-23
lines changed

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

Lines changed: 1 addition & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: azure-netapp-files
77
ms.workload: storage
88
ms.topic: how-to
99
ms.custom: references_regions
10-
ms.date: 05/09/2025
10+
ms.date: 05/15/2025
1111
ms.author: anfdocs
1212
---
1313
# Configure customer-managed keys with managed Hardware Security Module for Azure NetApp Files volume encryption
@@ -72,26 +72,6 @@ Azure NetApp Files volume encryption with customer-managed keys with the managed
7272
* West US 2
7373
* West US 3
7474

75-
## Register the feature
76-
77-
You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background. No UI control is required.
78-
79-
1. Register the feature:
80-
81-
```azurepowershell-interactive
82-
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFManagedHsmEncryption
83-
```
84-
85-
2. Check the status of the feature registration:
86-
87-
> [!NOTE]
88-
> 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.
89-
90-
```azurepowershell-interactive
91-
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFManagedHsmEncryption
92-
```
93-
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.
94-
9575
## Configure customer-managed keys with managed HSM for system-assigned identity
9676

9777
When you configure customer-managed keys with a system-assigned identity, Azure configures the NetApp account automatically by adding a system-assigned identity. The access policy is created on your Azure Key Vault with key permissions of Get, Encrypt, and Decrypt.

articles/azure-netapp-files/whats-new.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,13 @@ ms.author: anfdocs
1414

1515
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
1616

17+
## May 2025
18+
1719
* [Volume encryption with customer-managed keys with managed Hardware Security Module (HSM)](configure-customer-managed-keys-hardware.md) is now generally available (GA)
1820

1921
Azure NetApp Files volume encryption choices have expanded to offer support for customer-managed keys for Azure NetApp Files volume encryption with Azure Key Vault Managed HSM.
2022

2123
This feature offers increased security from FIPS 140-2 Level 2 to FIPS 140-2 Level 3 for critical deployments. Various applications that leverage HSM security include payment processing, application-level encryption, and authentication. Industry verticals that use HSMs include financial services, public sector, IT/Telco (secure communications), and energy (securing critical infrastructure).
22-
23-
## May 2025
2424

2525
* [Cross-zone-region replication](cross-zone-region-replication-configure.md) (preview)
2626

0 commit comments

Comments
 (0)