resolve build issues

Author: b-ahibbard

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

@@ -25,12 +25,10 @@ Azure NetApp Files supports four service levels: *Standard*, *Premium*, *Ultra*,
     The Ultra service level provides up to 128 MiB/s of throughput per 1 TiB of capacity provisioned. 
 
 * <a name="Flexible"></a>Flexible storage:
-    The Flexible service level enables you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. It can also be used to create high-capacity volumes with (relatively) low throughput requirements. The minimum throughput to be assigned to a Flexible capacity pool is 128 MiB/s regardless of the pool quota. The maximum throughput is 5 x 128 x the size of the capacity pool in TiB. For example, if your capacity pool is 1 TiB, the maximum is 640 MiB/second (5 x 128 x 1); f your capacity pool is 100 TiB, the maximum is 64,000 MiB/second (5 x 128 x 100). You can assign throughput and capacity to volumes that are part of a Flexible capacity pool in the same way you do volumes that are part of a manual QoS capacity pool of any service level.
-
-    Flexible storage capacity pools enforce single encryption. They do not support double encryption. 
+    The Flexible service level enables you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. It can also be used to create high-capacity volumes with (relatively) low throughput requirements. The minimum throughput to be assigned to a Flexible capacity pool is 128 MiB/s regardless of the pool quota. The maximum throughput is 5 x 128 x the size of the capacity pool in TiB. For examples, see [Flexible service level throughput examples](#flexible-examples). You can assign throughput and capacity to volumes that are part of a Flexible capacity pool in the same way you do volumes that are part of a manual QoS capacity pool of any service level.
 
     >[!IMPORTANT]
-    >The Flexible service level is only supported for _manual QoS_ capacity pools. 
+    >The Flexible service level is only supported for new _manual QoS_ capacity pools. 
 
 * Storage with cool access:      
     Cool access storage is available with the Standard, Premium, and Ultra 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. It may 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). 
@@ -54,7 +52,7 @@ The following diagram shows throughput limit examples of volumes in an auto QoS
 
 ### Throughput limit examples of volumes in a manual QoS capacity pool 
 
-If you use a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. When you create a volume in a manual QoS capacity pool, you can specify the throughput (MiB/S) value. The total throughput assigned to volumes in a manual QoS capacity pool depends on the size of the pool and the service level. Throughput limits are capped by a formula: capacity pool size in TiB x service level throughput/TiB. For instance, a 10-TiB capacity pool with the Ultra service level has a total throughput capacity of 1280 MiB/s (10 TiB x 128 MiB/s/TiB) available for the volumes.
+If you use a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. When you create a volume in a manual QoS capacity pool, you can specify the throughput (MiB/S) value. The total throughput assigned to volumes in a manual QoS capacity pool depends on the size of the pool and the service level. Throughput limits for the Standard, Premium, and Ultra service levels are capped by a formula: capacity pool size in TiB x service level throughput/TiB. For instance, a 10-TiB capacity pool with the Ultra service level has a total throughput capacity of 1,280 MiB/s (10 TiB x 128 MiB/s/TiB) available for the volumes. For the Flexible service level, the formula is 5 x capacity pool size in TiB x minimum service level throughput (128 MiB/s/TiB). For examples, see [Flexible service level throughput examples](#flexible-examples). 
 
 For example, for an SAP HANA system, this capacity pool can be used to create the following volumes. Each volume provides the individual size and throughput to meet your application requirements:
 
@@ -67,9 +65,9 @@ The following diagram illustrates the scenarios for the SAP HANA volumes:
 
 ![QoS SAP HANA volume scenarios](./media/azure-netapp-files-service-levels/qos-sap-hana-volume-scenarios.png) 
 
-Flexible service level throughput examples:
+<a name="flexible-examples">Flexible service level throughput examples:</a>
 
-| Flexible pool size (TiB) | Allowable throughput min (MiB/s) | Allowable throughput max (MiB/s) |
+| Flexible pool size (TiB) | Allowable throughput minimum (MiB/s) | Allowable throughput maximum (MiB/s) |
 | - | - | -- |
 | 1 | 128 | 5 * 128 * 1 = 640 |
 | 2 | 128 | 5 * 128 * 2 = 1,280 |
@@ -79,7 +77,7 @@ Flexible service level throughput examples:
 | 100 | 128 | 5 * 128 * 100 = 64,000 |
 
 >[!NOTE]
->A flexible capacity pool with 128 MiB/s throughput assigned to it is only charged for the allocated capacity.
+>A Flexible capacity pool with 128 MiB/s throughput assigned to it is only charged for the allocated capacity.
 
 ## Next steps
 

articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md

@@ -20,6 +20,7 @@ Creating a capacity pool enables you to create volumes within it.
 * If you're using the Azure REST API, ensure that you specify the latest version.
     >[!IMPORTANT]
     >To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from `2024-01-01`.
+* The Standard, Premium, and Ultra service levels are generally available (GA). No registration is required. 
 * The **Flexible** service level is currently in preview. Before creating a Flexible service level capacity pool, you must first register the feature:  
 
     1. Register the feature: 
@@ -42,6 +43,7 @@ Creating a capacity pool enables you to create volumes within it.
     * The minimum throughput for Flexible service level capacity pools is 128 MiB/second. Maximum throughput is calculated based on the size of the capacity pool using the formula 5 x 128 x capacity pool size in TiB. If your capacity pool is 1 TiB, the maximum is 640 MiB/second (5 x 128 x 1). If your capacity pool is 100 TiB, the maximum is 64,000 (5 x 128 x 100). 
     * Cool access isn't currently supported with the Flexible service level. 
     * Only single encryption is currently supported for Flexible service level capacity pools. 
+    * Volumes in Flexible service level capacity pools can't be moved to capacity pools of a different service level. Similarly, you can't move volumes from capacity pools with different service levels into a Flexible service level capacity pool.
     
 ## Steps 
 

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: overview
-ms.date: 01/2/2025
+ms.date: 01/25/2025
 ms.author: anfdocs
 ---
 # Storage hierarchy of Azure NetApp Files
@@ -41,7 +41,7 @@ Understanding how capacity pools work helps you select the right capacity pool t
 - You can't move a capacity pool across NetApp accounts.   
   For example, in the [Conceptual diagram of storage hierarchy](#conceptual_diagram_of_storage_hierarchy), you can't move Capacity Pool 1 US East NetApp account to US West 2 NetApp account.  
 - You can't delete a capacity pool until you delete all volumes within the capacity pool. 
-- You can configure a Standard, Premium, or Ultra service-level capacity pool with the cool access option. For more information about cool access, see [Azure NetApp Files storage with cool access](cool-access-introduction.md). 
+- [Azure NetApp Files storage with cool access](cool-access-introduction.md) is supported on Standard, Premium, and Ultra service-level capacity pool. For more information about service levels, including the Flexible service level, see [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md).
 
 ### <a name="qos_types"></a>Quality of Service (QoS) types for capacity pools
 
@@ -63,7 +63,8 @@ When you [create a capacity pool](azure-netapp-files-set-up-capacity-pool.md), y
 
 In a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. For minimum and maximum throughput levels, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits). The total throughput of all volumes created with a manual QoS capacity pool is limited by the total throughput of the pool. It's determined by the combination of the pool size and the service-level throughput.  For instance, a 4-TiB capacity pool with the Ultra service level has a total throughput capacity of 512 MiB/s (4 TiB x 128 MiB/s/TiB) available for the volumes.
 
-Manual QoS capacity pools also support the [**Flexible** service level](azure-netapp-files-sce-levels.md#Flexible), enabling you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. For throughput information, see [Service levels for Azure NetApp Files](azure-netapp-files-sce-levels.md#Flexible).
+Manual QoS capacity pools also support the [**Flexible** service level](azure-netapp-files-service-levels.md#Flexible), enabling you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. For throughput information, see [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md#Flexible).
+
 ##### Example of using manual QoS
 
 When you use a manual QoS capacity pool with, for example, an SAP HANA system, an Oracle database, or other workloads requiring multiple volumes, the capacity pool can be used to create these application volumes.  Each volume can provide the individual size and throughput to meet the application requirements. See [Throughput limit examples of volumes in a manual QoS capacity pool](azure-netapp-files-service-levels.md#throughput-limit-examples-of-volumes-in-a-manual-qos-capacity-pool) for details about the benefits.  

articles/azure-netapp-files/reservations.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 09/17/2024
+ms.date: 01/25/2025
 ms.author: anfdocs
 ---
 # Reserved capacity for Azure NetApp Files
@@ -30,6 +30,9 @@ This section describes the terms of an Azure NetApp Files reservation.
 >[!NOTE]
 >Azure NetApp Files reservations cover matching capacity pools in the selected service level and region. When using capacity pools configured with [cool access](manage-cool-access.md), only "hot" tier consumption is covered by the reservation benefit.
 
+>[!NOTE]
+>Azure NetApp Files reservations aren't currently supported on the [Flexible service level](azure-netapp-files-service-levels.md).
+
 ### Reservation quantity
 
 You can purchase a reservation in 100-TiB and 1-PiB units per month for a one- or three-year term for a particular service level within a region.

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

@@ -14,7 +14,7 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
-# February 2025
+## February 2025
 
 * [Flexible service level](azure-netapp-files-set-up-capacity-pool.md) (preview)