Skip to content

Commit 29a3aaf

Browse files
Merge pull request #293259 from b-ahibbard/cmk-transition-ga
cmk transition: ga
2 parents 2236b63 + 0c15f06 commit 29a3aaf

File tree

2 files changed

+10
-24
lines changed

2 files changed

+10
-24
lines changed

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

Lines changed: 3 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Configure customer-managed keys for Azure NetApp Files volume encryption | Microsoft Docs
2+
title: Configure customer-managed keys for Azure NetApp Files volume encryption
33
description: Describes how to configure customer-managed keys for Azure NetApp Files volume encryption.
44
services: azure-netapp-files
55
author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.topic: how-to
88
ms.custom: devx-track-azurecli, devx-track-azurepowershell
9-
ms.date: 04/25/2025
9+
ms.date: 06/20/2025
1010
ms.author: anfdocs
1111
---
1212

@@ -313,30 +313,10 @@ You can use an Azure Key Vault that is configured to use Azure role-based access
313313
* [Create an SMB volume](azure-netapp-files-create-volumes-smb.md)
314314
* [Create a dual-protocol volume](create-volumes-dual-protocol.md)
315315
316-
## <a name="transition"></a> Transition an Azure NetApp Files volume to customer-managed keys (preview)
316+
## <a name="transition"></a> Transition an Azure NetApp Files volume to customer-managed keys
317317
318318
Azure NetApp Files supports the ability to move existing volumes using platform-managed keys to customer-managed keys. Once you complete the migration, you can't revert to platform-managed keys.
319319
320-
### Register the feature
321-
322-
Encryption key transition for Azure NetApp Files is currently in preview. Before using this feature for the first time, you need to register it.
323-
324-
1. Register the feature:
325-
326-
```azurepowershell-interactive
327-
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFMigratePmkToCmk
328-
```
329-
330-
2. Check the status of the feature registration:
331-
332-
```azurepowershell-interactive
333-
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFMigratePmkToCmk
334-
```
335-
> [!NOTE]
336-
> The **RegistrationState** can remain in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
337-
338-
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.
339-
340320
### Transition volumes
341321
342322
>[!NOTE]

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,20 @@ ms.custom:
88
- linux-related-content
99
- build-2025
1010
ms.topic: overview
11-
ms.date: 05/20/2025
11+
ms.date: 06/20/2025
1212
ms.author: anfdocs
1313
---
1414

1515
# What's new in Azure NetApp Files
1616

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

19+
## June 2025
20+
21+
* The ability to [transition an existing volume to customer-managed keys](configure-customer-managed-keys.md#transition) is now generally available (GA)
22+
23+
You can transition existing volumes from platform-managed keys to customer-managed keys seamlessly. This provides you flexibility of encryption key lifecycle (renewals, rotations) and additional security for regulated industry requirements.
24+
1925
## May 2025
2026

2127
* [Volume encryption with customer-managed keys with managed Hardware Security Module (HSM)](configure-customer-managed-keys-hardware.md) is now generally available (GA)

0 commit comments

Comments
 (0)