Merge pull request #311314 from netapp-manishc/patch-811517

Patch 811517

Author: prmerger-automator[bot]

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

@@ -322,7 +322,7 @@ Azure NetApp Files supports the ability to move existing volumes using platform-
 ### Transition volumes
 
 >[!NOTE]
->When you transition volumes to use customer-managed keys, you must perform the transition for every virtual network where your Azure NetApp Files account has volumes. 
+>When you transition volumes to use customer-managed keys, you must perform the transition for every virtual network where your Azure NetApp Files account has volumes. If you manage your Azure resources using Terraform, you should update all [Terraform-managed Azure resources](terraform-manage-volume.md) for all volumes that were modified out-of-band. 
 
 1. Ensure you [configured your Azure NetApp Files account to use customer-managed keys](#configure-a-netapp-account-to-use-customer-managed-keys).
 1. In the Azure portal, navigate to **Encryption**. 
@@ -416,4 +416,4 @@ Making changes to the Azure Private Endpoint after creating a customer-managed k
 * [Azure NetApp Files API](https://github.com/Azure/azure-rest-api-specs/tree/master/specification/netapp/resource-manager/Microsoft.NetApp/stable/2019-11-01)
 * [Configure customer-managed keys with managed Hardware Security Module](configure-customer-managed-keys-hardware.md)
 * [Configure cross-tenant customer-managed keys](customer-managed-keys-cross-tenant.md)
-* [Understand data encryption in Azure NetApp Files](understand-data-encryption.md)
+* [Understand data encryption in Azure NetApp Files](understand-data-encryption.md)

articles/azure-netapp-files/terraform-manage-volume.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: devx-track-terraform
 ms.topic: how-to
-ms.date: 08/10/2025
+ms.date: 02/04/2026
 ms.author: anfdocs
 # Customer intent: As a cloud engineer, I want to update Terraform-managed Azure resources safely, so that I can prevent data loss while modifying essential features outside of Terraform.
 ---
@@ -44,7 +44,11 @@ The following instructions are a high-level overview of the steps required to up
 1. Run `terraform plan` to confirm that no changes will be made to your volume. The CLI output should display: `No changes. Your infrastructure matches the configuration.`
     >[!NOTE]
     > The `terraform plan` command creates a plan file with the changes to the remote resource, allowing you to ensure the safety of your resource before applying any changes. 
-1. Run `terraform apply` to apply the changes. You should see the same CLI output as in the previous step. 
+1. Run `terraform apply` to apply the changes. You should see the same CLI output as in the previous step.
+
+   >[!NOTE]
+   > To re-establish the state, you should update the Terraform module's configuration file to reflect the changes made outside of Terraform. This change should be made to all Terraform-managed ANF resource that were modified out-of-band.
+   
 
 ## Next steps