You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: overview
8
-
ms.date: 1/29/2026
8
+
ms.date: 02/04/2026
9
9
ms.author: anfdocs
10
10
# Customer intent: "As a cloud architect, I want to understand the storage hierarchy of Azure NetApp Files, so that I can effectively set up and manage capacity pools and volumes to meet our storage needs."
11
11
---
@@ -36,7 +36,7 @@ Understanding how capacity pools work helps you select the right capacity pool t
36
36
### General rules of regular capacity pools
37
37
38
38
- A capacity pool is measured by its provisioned capacity.
39
-
For more information, see [QoS types](#qos_types).
39
+
For more information, see [QoS types](#qos_types).
40
40
- The capacity is provisioned by the fixed SKUs that you purchased (for example, a 4-TiB capacity).
41
41
- A capacity pool can have only one service level.
42
42
- Each capacity pool can belong to only one NetApp account. However, you can have multiple capacity pools within a NetApp account.
@@ -45,7 +45,6 @@ Understanding how capacity pools work helps you select the right capacity pool t
45
45
- You can't delete a capacity pool until you delete all volumes within the capacity pool.
46
46
-[Azure NetApp Files storage with cool access](cool-access-introduction.md) is supported in Flexible, Standard, Premium, and Ultra service-level capacity pools. For more information about service levels, including the Flexible service level, see [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md).
47
47
48
-
49
48
### General rules of Elastic capacity pools
50
49
51
50
- You must have a NetApp account designated for use with Elastic zone-redundant storage.
@@ -54,12 +53,10 @@ Understanding how capacity pools work helps you select the right capacity pool t
54
53
- A capacity pool can have only one service level.
55
54
- Each capacity pool can belong to only one NetApp Elastic account. You can have multiple capacity pools within a NetApp Elastic account.
56
55
- You can't move a capacity pool across NetApp Elastic accounts.
57
-
58
56
For example, in the storage hierarchy diagram, you can't move Capacity Pool 1 in the US East 2 NetApp Elastic account to the US West 2 NetApp Elastic account.
59
57
- You can't delete a capacity pool until you delete all volumes within the capacity pool.
60
58
- If you're using customer-managed keys, [ensure you've configured encryption before creating the capacity pool.](elastic-customer-managed-keys.md).
61
59
- Elastic capacity pools enable you to create a failover preference order of availability zones. Some regions that support the Elastic service level only offer two availability zones. Query the region for availability zone with the REST API before creating the capacity pool:
62
-
63
60
```
64
61
GET https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/elasticRegionInfo?api-version=2025-09-01-preview.
0 commit comments