Update transition volumes note for customer-managed keys

Added note about updating Terraform-managed resources when transitioning volumes to customer-managed keys.

Author: netapp-manishc

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. However, if the volumes are managed through Terraform, you should update the [Terraform-managed Azure resources](terraform-manage-volume.md).
 
 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)