Merge pull request #314749 from netapp-manishc/patch-118421

Remove cool access registration instructions

Author: prmerger-automator[bot]

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -50,7 +50,7 @@ The Flexible, Standard, Premium, and Ultra service levels deliver in‑Azure bar
 
 ### Storage with cool access
 
-[Cool access storage](manage-cool-access.md#register-the-feature) is available with the Standard, Premium, Ultra, and Flexible service levels. The throughput experience for any of these service levels with cool access is the same for cool access as it is for data in the hot tier. Throughput experiences differ when data that resides in the cool tier is accessed. For more information, see [Azure NetApp Files storage with cool access](cool-access-introduction.md) and [Performance considerations for storage with cool access](performance-considerations-cool-access.md).  For additional information about the Premium and Ultra service levels, see [Throughput in the Premium and Ultra service levels](cool-access-introduction.md#throughput-for-premium-and-ultra-service-levels). 
+Cool access storage is available with the Standard, Premium, Ultra, and Flexible service levels. The throughput experience for any of these service levels with cool access is the same for cool access as it is for data in the hot tier. Throughput experiences differ when data that resides in the cool tier is accessed. For more information, see [Azure NetApp Files storage with cool access](cool-access-introduction.md) and [Performance considerations for storage with cool access](performance-considerations-cool-access.md).  For additional information about the Premium and Ultra service levels, see [Throughput in the Premium and Ultra service levels](cool-access-introduction.md#throughput-for-premium-and-ultra-service-levels). 
 
 >[!NOTE]
 >Cool access pricing is calculated in the same manner for all service levels (Standard, Premium, Ultra, and Flexible).

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -70,7 +70,7 @@ The following requirements and considerations apply to large volumes. For perfor
 
     For the latest performance benchmark numbers conducted on Azure NetApp Files Large volumes, see [Azure NetApp Files large volume performance benchmarks for Linux](performance-large-volumes-linux.md) and [Benefits of using Azure NetApp Files for Electronic Design Automation (EDA)](solutions-benefits-azure-netapp-files-electronic-design-automation.md).
 
-* Cool access is supported with large volumes. You must be [registered to use cool access](manage-cool-access.md#register-the-feature) before creating a cool access-enabled large volume. 
+* Cool access is supported with large volumes. 
 
 ### Requirements and considerations for breakthrough mode (preview)
 
@@ -84,8 +84,7 @@ Large volumes breakthrough mode is currently in preview. You must [request the f
 
 #### Requirements and considerations for large volumes up to 7.2 PiB (preview)
 
-* In some cases, you can create large volume with cool access enabled at sizes between 2,400 GiB and 7.2 PiB.
-  * If you're using the Flexible, Premium, or Ultra service levels, you must also [register to use those service levels with cool access](manage-cool-access.md#register-the-feature).
+* In some cases, you can create large volume with cool access enabled at sizes between 2,400 GiB and 7.2 PiB.  
 * With these large volumes, more than 80% of the data should reside in the cool tier.  
 * If you plan to use cross-region replication for a large volume up to 7.2 PiB, you need to ensure there is sufficient capacity in both regions and that the stamp for large volumes up to 7.2 PiB is on volumes in _both_ the source and destination regions. 
 
@@ -176,9 +175,6 @@ You can also use [Azure CLI command](/cli/azure/feature) `az feature show` to re
 
 ### Register for large volumes up to 7.2 PiB
 
->[!NOTE]
->You must be registered to use [large volumes](#register-the-feature) and, if you're using the Flexible, Premium, or Ultra service level, [cool access](manage-cool-access.md#register-the-feature) before registering for the large volumes up to 7.2 PiB. 
-
 Large volumes up to 7.2 PiB are currently in preview. [Submit a waitlist request](https://forms.office.com/r/WfBqxqayzM) for access to the feature. 
 
 After submitting the waitlist request, you can check the status of your feature registration with the command:

articles/azure-netapp-files/manage-cool-access.md

@@ -88,31 +88,6 @@ There are several considerations to be aware of when using cool access.
 * When you [restore a snapshot of a cool access-enabled volume to a new volume](snapshots-restore-new-volume.md), the new volume inherits the cool access configuration from the parent volume. After the new volume is created, you can modify the cool access settings.  
 * You can't restore from a snapshot of a non-cool-access volume to a cool access volume. Likewise, you can't restore from a snapshot of a cool access volume to a non-cool-access volume.
 
-## Enable cool access 
-
-You must register for cool access with the Flexible service level before you can enable it at the capacity pool and volume levels. No registration is required for the Standard, Premium and Ultra service levels. 
-
-### Register the feature
-
-You must register cool access with the Flexible service level before using it. 
-
-1. Register the feature: 
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessFlexible
-    ```
-
-2. Check the status of the feature registration: 
-    > [!NOTE]
-    > 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.
-
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessFlexible
-    ```
-
-    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. 
-    
-
 ### Configure the capacity pool for cool access
 
 Before you create or enable a cool-access volume, configure a capacity pool with cool access. You can do so in one of the following ways: 

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

@@ -144,7 +144,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     Enterprises upgrading their domain infrastructure can maintain high-performance, enterprise-grade file services with Azure NetApp Files SMB and dual-protocol volumes. This compatibility means you can confidently adopt the latest Windows Server capabilities while continuing to leverage the scalability and reliability of Azure NetApp Files.
 
-* [Flexible service level](manage-cool-access.md?tabs=flexible#register-the-feature) with cool access is now generally available (GA)
+* [Flexible service level](manage-cool-access.md) with cool access is now generally available (GA)
 
     Azure NetApp Files supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. This feature is now generally available (GA).
 
@@ -188,9 +188,9 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     File access logs provide enterprise-grade visibility into file-level operations across SMB3, NFSv4.1, and dual-protocol volumes. This capability enhances security, reliability, and operational insight by capturing detailed access activity—including user identity, operation type, and timestamps. Organizations can use file access logs to monitor access patterns, detect unauthorized activity, support compliance investigations, and optimize data usage. By integrating this feature, you strengthen your security posture and align with the Well-Architected Framework's best practices for operational excellence.
 
-* [Flexible service level](manage-cool-access.md?tabs=flexible#register-the-feature) now supports storage with cool access (preview)
+* [Flexible service level](manage-cool-access.md) now supports storage with cool access (preview)
 
-    Azure NetApp Files now supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. You must be registered for the [Flexible service level](azure-netapp-files-set-up-capacity-pool.md) before enrolling in [the preview for the Flexible service level with cool access](manage-cool-access.md#register-the-feature). 
+    Azure NetApp Files now supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. 
 
 ## June 2025
 
@@ -361,8 +361,6 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     In a cross-region or cross-zone replication setting, cool access can now be configured for destination only volumes to ensure data protection. This capability provides cost savings without any latency impact on source volumes.
 
-    You still must [register the feature](manage-cool-access.md#register-the-feature) before enabling cool access. 
-
 * [Volume encryption with customer-managed keys with managed Hardware Security Module (HSM)](configure-customer-managed-keys-hardware.md) (preview)
 
     Volume encryption with customer-managed keys with managed HSM extends the [customer-managed keys](configure-customer-managed-keys.md), enabling you to store your keys in a more secure FIPS 140-2 Level 3 HSM service instead of the FIPS 140-2 Level 1 or 2 encryption offered with Azure Key Vault.