Merge pull request #311209 from netapp-manishc/cool-access-throughput

v-dirichards · web-flow · commit 2690392b4ead · 2026-04-02T10:23:25.000-05:00
ANF-57014 - Cool access throughput
diff --git a/articles/azure-netapp-files/azure-netapp-files-service-levels.md b/articles/azure-netapp-files/azure-netapp-files-service-levels.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 01/29/2026
+ms.date: 02/02/2026
 ms.author: anfdocs
 # Customer intent: "As a cloud storage administrator, I want to understand the throughput capabilities of different service levels in Azure NetApp Files, so that I can choose the right configuration to meet my application's performance requirements."
 ---
@@ -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). 
+[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). 
 
 >[!NOTE]
 >Cool access pricing is calculated in the same manner for all service levels (Standard, Premium, Ultra, and Flexible).
diff --git a/articles/azure-netapp-files/cool-access-introduction.md b/articles/azure-netapp-files/cool-access-introduction.md
@@ -47,6 +47,59 @@ Cool access offers [performance metrics](azure-netapp-files-metrics.md#cool-acce
 * Volume cool tier data read size
 * Volume cool tier data write size
 
+## Throughput for Premium and Ultra service levels 
+
+When cool access is enabled on the Premium and Ultra service levels, throughput is adjusted at regular intervals based on the size of the data in the cool tier.  
+
+If a volume is within the Premium or Ultra service levels with auto QoS enabled and has more than 100 GiB of cool access data, the throughput QoS limit is different for the data on hot and cool tier respectively.
+
+Review the table to understand how throughput limit is calculated. 
+
+| Service level | Formula without cool access | Formula with cool access | 
+| - | -- | --- |
+| Premium | Maximum throughput in MiB/s = Quota in TiB * 64 MiB/s | Maximum throughput in MiB/s = (Hot tier data in TiB * 64 MiB/s) + (Cool tier data in TiB * 16 MiB/s per TiB of data in the cool tier)
+| Ultra | Maximum throughput in MiB/s = Quota in TiB * 128 MiB/s | Maximum throughput in MiB/s = (Hot tier data in TiB * 128 MiB/s) + (Cool tier data in TiB * 16 MiB/s per TiB of data in the cool tier) |
+
+For example, if a volume in the Premium service level has 10 TiB of data in the hot tier, its maximum throughput is 640 MiB/s (10 TiB * 64 MiB/s). For a Premium service level deployment with 2 TiB in the cool tier and 8 TiB in the hot tier, the maximum throughput is 544 MiB/s ([8 TiB * 64 MiB/s] + [2 TiB * 16 MiB/s]).
+
+For existing volumes in capacity pools where cool access was enabled prior to this update, the prior throughput QoS limit continues to apply as per the following table.
+
+| Service level | Throughput with cool access | Baseline throughput (cool access never enabled) | 
+| - | -- | -- |
+| Premium | Quota in TiB * 36 MiB/s |  Quota in TiB * 64 MiB/s 
+| Ultra | Quota in TiB * 68 MiB/s |  Quota in TiB * 128 MiB/s 
+
+For example, a 10-TiB volume on the Premium service regularly delivers throughput of 640 MiB/s (10 TiB * 64 MiB/s). With cool access enabled regardless of the amount of data tiered, throughput is 360 MiB/s (10 TiB * 36 MiB/s).
+
+> [!NOTE]
+> You should create a new capacity pool and move the old volumes to the new capacity pools to use the updated QoS limit. 
+
+With either throughput calculation, increasing the volume quota increases the throughput limit because throughput scales linearly with the provisioned capacity.
+
+### Supported regions for cool access throughput for premium and ultra service levels feature
+
+* Australia Southeast
+* Brazil South
+* Brazil Southeast
+* Canada Central
+* Canada East
+* Central US
+* East Asia
+* Germany North 
+* Germany West Central
+* Israel Central 
+* Japan East
+* Korea South
+* North Central US
+* Norway East
+* Qatar Central
+* Southeast Asia
+* Sweden Central
+* Switzerland West
+* UAE Central
+* UK West
+* West US
+
 ## Billing 
 
 You can enable cool access for each volume in a [cool-access enabled capacity pool](manage-cool-access.md). How you're billed is based on:
diff --git a/articles/azure-netapp-files/manage-cool-access.md b/articles/azure-netapp-files/manage-cool-access.md
@@ -27,7 +27,7 @@ There are several considerations to be aware of when using cool access.
 ### General considerations for cool access
 
 * No guarantee is provided for any maximum latency for client workload for any of the service tiers.
-* Although cool access is available for the Standard, Premium, and Ultra service levels, how you're billed for using the feature differs from the hot tier service-level charges. For details and examples, see the [Billing section](cool-access-introduction.md#billing).
+* Although cool access is available for the Standard, Premium, Ultra, and Flexible service levels, how you're billed for using the feature differs from the hot tier service-level charges. For details and examples, see the [Billing section](cool-access-introduction.md#billing).
 * Cool access supports two tiering policies: `Auto` and `SnapshotOnly`. The `SnapshotOnly` policy limits data tiering to data in snapshots, while all data blocks associated with files in the active file system remain in the hot tier. The `Auto` policy encompasses both snapshot copy data and data in the active file system.
     Throughput is based on the [the service level](azure-netapp-files-service-levels.md#supported-service-levels) for both the `Auto` and `SnapshotOnly` tiering policies.
 * To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to **Default** or **Never**. For more information about the retrieval policy, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
@@ -61,11 +61,9 @@ There are several considerations to be aware of when using cool access.
 
 ### Considerations for throughput in Premium and Ultra service level volumes with cool access
 
-- Enabling cool access on volumes in Premium and Ultra capacity pools results in reduced throughput: 
-    - For the Premium service level, throughput is 36 MiB/s per 1 TiB (compared to 64 MiB/s per 1 TiB without cool access) 
-    - For the Ultra service level, throughput is 68 MiB/second per 1 TiB (compared to 128 MiB/second per 1 TiB without cool access) 
-    - Reduced throughput limits are applicable to the `Auto` and `SnapshotOnly` tiering policies.
-- This reduced throughput remains in effect even if the cool access feature is subsequently turned off for the volume.  
+>[!IMPORTANT]
+>Throughput calculations for cool access with the Premium and Ultra service levels depends on the QoS of the capacity pool and the amount of data in the cool tier. To learn more, see [Throughput in the Premium and Ultra service levels](cool-access-introduction.md#throughput-for-premium-and-ultra-service-levels).
+
 - When cool access is enabled on a volume, you benefit from a reduced price. You don't receive additional discounts specifically for the reduced bandwidth. Instead, you pay the cool access price, which inherently includes the reduced throughput. 
 
 ### Considerations for deleting data on a cool access enabled volume
@@ -92,55 +90,9 @@ There are several considerations to be aware of when using cool access.
 
 ## Enable cool access 
 
-You must register for cool access with the Flexible, Premium, or Ultra service levels before you can enable it at the capacity pool and volume levels. No registration is required for the Standard service level. 
-
-### <a name="register-the-feature"></a> Register for cool access
-
-# [Ultra](#tab/ultra)
-
-Before using cool access at the Ultra service level for the first time, you need to register the feature. 
-
-1. Register the feature: 
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessUltra 
-    ```
-
-2. Check the status of the feature registration: 
-
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessUltra
-    ```
-    > [!NOTE]
-    > 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.
-
-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. 
-
-# [Premium](#tab/premium)
+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. 
 
-Before using cool access at the Premium service level for the first time, you need to register the feature. 
-
-1. Register the feature: 
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessPremium 
-    ```
-
-2. Check the status of the feature registration: 
-
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCoolAccessPremium
-    ```
-    > [!NOTE]
-    > 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.
-
-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. 
-
-# [Standard](#tab/standard)
-
-No registration is required to use cool access at the Standard service level.
-
-# [Flexible](#tab/flexible)
+### Register the feature
 
 You must register cool access with the Flexible service level before using it. 
 
@@ -160,7 +112,6 @@ You must register cool access with the Flexible service level before using it.
 
     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
 
diff --git a/articles/azure-netapp-files/whats-new.md b/articles/azure-netapp-files/whats-new.md
@@ -20,6 +20,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## March 2026
 
+* [Storage with cool access enhancement](cool-access-introduction.md#throughput-for-premium-and-ultra-service-levels) for Premium and Ultra service levels (preview)
+
+    Azure NetApp Files introduces an enhancement to storage with cool access for Premium and Ultra service levels that more precisely aligns throughput with data tiering. When cool access is enabled, maximum throughput is dynamically calculated based on the amount of data tiered to cool access storage, rather than applying a fixed reduction. Hot data retains its configured performance, and throughput is adjusted only when data is tiered to the cool tier. This enhancement delivers more predictable QoS behavior while optimizing performance and cost as data access patterns evolve, without requiring manual tuning or reconfiguration.
+
 * [Large volumes improvement:](large-volumes-requirements-considerations.md#requirements-and-considerations) removed 30% default limit imposed on large volumes
 
     Large volumes operational improvement no longer requires a support ticket to increase a large volume past the 30% imposed limit. This allows customer to automate their large volume size increases without waiting for approval and human intervention.
