AzureAzure NetApp FilesStorage

`azurerm_netapp_pool` cost estimation

A provisioned capacity pool for high-performance NFS/SMB file storage. Priced per provisioned TiB by service level, billed on allocated (not used) capacity.

An azurerm_netapp_pool provisions a capacity pool within Azure NetApp Files, the enterprise-grade managed file storage for workloads needing high throughput and low latency (SAP, HPC, large databases, VDI). The defining cost characteristic: you pay for provisioned capacity, not consumed capacity.

The rate is per provisioned TiB by service level. Standard runs roughly $0.000202/GiB-hour, Premium ~$0.000403/GiB-hour (~$0.30/GiB-month), and Ultra ~$0.000538/GiB-hour. The minimum pool size is 4 TiB, so the entry cost is real: a 4 TiB Premium pool is roughly $1,200/month whether you store 4 TiB or 400 GB. Throughput scales with the service level and the volume quota you carve from the pool.

c3x reads size_in_tb and service_level and prices the provisioned capacity at 730 hours/month. Because billing is on allocated capacity, the optimization is matching pool size and service level to real needs rather than over-provisioning headroom. Volumes carved from the pool don't add cost beyond the pool's provisioned capacity.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_netapp_pool" "data" {
  name                = "data-pool"
  account_name        = azurerm_netapp_account.main.name
  resource_group_name = azurerm_resource_group.storage.name
  location            = "eastus"
  service_level       = "Premium"
  size_in_tb          = 4
}

Pricing dimensions

What you actually pay for when you provision azurerm_netapp_pool.

Dimension	Unit	What's being charged
Provisioned capacity	per GiB-month	Allocated pool capacity by service level, billed whether or not it's used. Minimum 4 TiB. c3x assumes 730 hours/month. ~$0.29/GiB-month (Premium), ~$0.15 (Standard)
Service level	Standard / Premium / Ultra	Higher levels raise both the per-GiB rate and the throughput per TiB. Ultra is roughly 2.5x Standard.

Sample C3X output

Example output from c3x estimate (4 TiB Premium pool):

azurerm_netapp_pool.data
└─ Provisioned capacity (4 TiB Premium)   4,096  GiB-month    $1,204.96

OVERALL TOTAL                                                $1,204.96

Optimization tips

Common ways to reduce azurerm_netapp_pool cost without changing the workload.

Match service level to throughput need, not habit

Up to 50% vs Premium

Throughput scales with service level and capacity. If your workload is capacity-bound rather than throughput-bound, Standard at ~half the Premium rate may meet the requirement.

Right-size pool capacity to allocated volumes

Per over-provisioned TiB

You pay for the whole provisioned pool. Don't provision 8 TiB when your volumes total 4 TiB plus modest growth. Grow the pool as real usage approaches the limit.

Use cool access for infrequently-read data

Cold-data tiering

Azure NetApp Files cool access tiers infrequently-accessed blocks to cheaper storage, reducing the effective per-GiB cost for cold data within a volume.

FAQ

How does c3x estimate Azure NetApp Files cost?

It reads size_in_tb and service_level and prices the provisioned capacity at the per-GiB-month rate for that level, at 730 hours/month. Billing is on allocated capacity, so the estimate reflects the pool size regardless of how much is used.

Why is the minimum cost so high?

The minimum capacity pool is 4 TiB, and you pay for provisioned (not used) capacity. A 4 TiB Premium pool is roughly $1,200/month even if you store far less, which is the entry floor for the service.

Do volumes within the pool cost extra?

No. Volumes carved from the pool draw on the pool's provisioned capacity; you don't pay separately per volume. The pool's size and service level determine the cost.

How do the service levels differ in cost?

Standard is cheapest (~$0.15/GiB-month), Premium roughly double, Ultra highest (~$0.54/GiB-month). Each level also provides more throughput per TiB, so the choice trades cost against performance.

Is this cheaper than Azure Files or managed disks?

Not usually, per GB. NetApp Files targets enterprise performance (high throughput, low latency, NFS/SMB at scale). For general file shares, azurerm_storage_share (Azure Files) is cheaper; for block storage, azurerm_managed_disk.