Azure Files and NetApp Files pricing

Azure Files pricing starts with the billing model of the share: provisioned v2 bills provisioned storage, IOPS and throughput per hour, provisioned v1 bills provisioned GiB on SSD with IOPS and throughput in a fixed ratio, and pay-as-you-go bills used GiB plus transactions per 10,000 in the transaction optimized, hot and cool tiers; on top come snapshots, Azure File Sync per registered server, Azure Backup, and for Azure NetApp Files the capacity pool per GiB and hour by service level. On the bill, provisioned shares and NetApp pools are dominated by the size provisioned rather than used, and pay-as-you-go shares with SMB clients often by the transactions.

Pricing dimensions

Provisioned v2 is, in Microsoft's words, the model for every new share: it detaches the price from usage and makes it plannable, but asks someone to set the three values and raise them as the share grows. Pay-as-you-go runs all three tiers on the same hardware; they differ only in the price per GiB (highest in transaction optimized, lowest in cool) and in the price per transaction (the reverse). Microsoft advises starting a migration in transaction optimized and choosing the tier from measured usage once the move is complete; a tier change bills one write or read transaction of the cooler tier per file, plus retrieval per GiB when leaving cool, and is allowed five times in 30 days. On NetApp Files the service level fixes the throughput per TiB, 16 MiB/s on Standard, 64 on Premium, 128 on Ultra; Flexible decouples throughput from capacity and gives every pool 128 MiB/s as a baseline, and because the pool is metered hourly, every size or level change takes effect from the next full hour. The three providers' models sit side by side under block, object and file storage.

How it appears in your billing data

Every share of a storage account appears in the cost export with MeterCategory Storage and the storage account as ResourceId; the billing model sits in MeterSubCategory: Azure Files Provisioned v2 with the meters Provisioned Storage, Provisioned IOPS, Provisioned Throughput MiBPS, Overflow Snapshot Usage and Soft-Deleted Usage, each prefixed with media and redundancy (SSD LRS Provisioned Storage, HDD ZRS Provisioned IOPS); Premium Files for provisioned v1 with Premium LRS Provisioned, Premium LRS Snapshots, Premium LRS Burst Transactions and Premium LRS Burst Bandwidth; Files v2 for pay-as-you-go with Data Stored, Metadata, Write Operations, List Operations, Read Operations, Other Operations or Protocol Operations, Data Retrieval and Geo-Replication Data Transfer, each prefixed with tier and redundancy (Hot LRS Data Stored, Cool GRS Write Operations, Standard LRS Data Stored for transaction optimized). The units give the model away: provisioned v2 emits GiB-hours every hour (1,024 units per hour for 1,024 GiB), provisioned v1 and pay-as-you-go emit monthly fractions every hour (1.3763 units per hour in a 31-day month for 1,024 GiB), and transactions arrive as fractions of 10,000.

Azure File Sync carries the product File Sync with the meter Standard Server per registered server and Standard Server - Free for the first; the sync transactions, snapshots and recalls land on the share's meters, not on the sync service. Azure Backup for shares puts its protected instance lines under the Backup service while the snapshot storage stays under Storage. Azure NetApp Files is a service of its own: MeterCategory Azure NetApp Files with the meters Standard Capacity, Premium Capacity, Ultra Capacity, Flexible Service Level Capacity and Flexible Service Level Throughput MiBps per hour, Backup Capacity per GiB-month, Volume Restore Capacity per GiB, Cross Region Replication per GiB transferred with source and destination region in the product name, and Standard Storage with Cool Access Capacity and Standard Storage with Cool Access Data Transfer for the cool tier. Microsoft Defender for Storage bills its transaction fee under the Defender service, also on provisioned shares where transactions otherwise cost nothing (Sentinel, Defender and Key Vault pricing).

In the FOCUS export the same values sit in x_SkuMeterCategory, x_SkuMeterSubcategory and SkuMeter; ServiceName names the service, ChargeCategory is Usage for consumption and Purchase for buying reserved capacity, whose hours carry a CommitmentDiscountId. A single share is invisible in the export because the resource is the storage account; to attribute shares to teams, separate them by account or use the new file share resources (Microsoft.FileShares), which appear as resources of their own without a storage account, currently for SSD with NFS and provisioned v2 only.

Levers

Configuration. On provisioned v2, IOPS and throughput are lines of their own: the portal's recommendation follows the size, the need follows the workload, and both can be lowered separately. On provisioned v1 the size alone sets performance; whoever needs IOPS buys GiB. Pay-as-you-go shares belong in the tier that fits their transaction pattern: cool is dearer than transaction optimized under heavy access, because the transaction prices outweigh the storage saving. Snapshot retention costs capacity in every model, on v2 only above the provisioned size. On NetApp Files the pool size and service level follow the hour; a pool raised to Ultra for a batch run returns to Standard afterwards, and Flexible takes the overprovisioned dimension off the bill for large, slow volumes (rightsizing).

Purchase option. Reserved capacity exists for provisioned v1 and pay-as-you-go (hot and cool), not for provisioned v2, and for NetApp pools per service level, excluding the cool access tier (reserved capacity for managed services).

Architecture. Large, quiet data does not belong on file shares: anything without a need for SMB or NFS semantics is cheaper per GiB in Blob Storage, and anything that serves one server on a managed disk. With Azure File Sync every additional server costs the monthly fee and every daily enumeration one list transaction per directory; cloud tiering shrinks local storage but generates recalls and egress. NetApp cool access moves cold blocks into cheaper storage, snapshots and short-term clones replace full copies, and a replication destination on Flexible at baseline throughput keeps the disaster recovery copy cheap (storage optimisation, backup and disaster recovery). Shares and pools nobody mounts any more keep billing at the full provisioned price (idle and orphaned resources).

Where it goes wrong

• The share is half empty, the bill is full. Provisioned v1, provisioned v2 and NetApp pools bill the provisioned size; usage plays no part. Compare provisioned GiB with used GiB and shrink, on v2 no earlier than 24 hours after the last increase.
• Transactions exceed storage. A pay-as-you-go share in cool serves an active workload, or a scanner, antivirus or backup agent reads every file daily. Read the operation meters per account, change the tier, or migrate to provisioned v2 where transactions are included in the IOPS.
• A tier change produced a one-day spike. The change billed one transaction of the cooler tier per file, and retrieval per GiB when leaving cool. Choose tiers from measured usage and stop switching back and forth.
• Snapshots grow unnoticed. Azure Backup or Azure File Sync creates snapshots, and at a high change rate the differential grows; on v2 it only appears as Overflow Snapshot Usage once the provisioned size is exceeded. Shorten retention in the backup policy or plan the size for it.
• Defender for Storage costs on provisioned shares. Defender's transaction price applies even where Azure Files does not bill transactions. Check transaction-heavy accounts and exclude them where appropriate.
• The NetApp pool is larger than its volumes. A pool was created at 4 TiB, the volumes occupy 2 TiB, and 4 are billed. Shrink the pool in 1 TiB steps down to the volume quotas.
• File Sync servers count twice. Servers were re-registered without removing the old registration, and each counts monthly. Clean up the registered servers in the Storage Sync Service.

Example

List prices from the Azure Retail Prices API in EUR for Germany West Central, read on 2026-10-21: pay-as-you-go with LRS costs per GB and month EUR 0.0508 in transaction optimized, EUR 0.0238 in hot and EUR 0.0132 in cool (GRS EUR 0.0847, 0.0476 and 0.0264; ZRS EUR 0.066, 0.0291 and 0.0165), metadata with LRS EUR 0.0246 per GB and month; write transactions per 10,000 cost EUR 0.0132 in transaction optimized, EUR 0.0618 in hot and EUR 0.1144 in cool, read transactions EUR 0.0013, 0.0049 and 0.0114, list transactions EUR 0.0132, 0.0618 and 0.0618, retrieval from cool EUR 0.0088 per GB. Provisioned v1 costs EUR 0.169 per provisioned GB and month with LRS, snapshots EUR 0.1434 per GB and month, EUR 0.2112 with ZRS; provisioned v2 on SSD with LRS is listed by the API at EUR 0.0002 per GiB and hour for storage and EUR 0.0001 per MiB/s and hour for throughput, while the HDD meters fall below the fourth decimal the API rounds to in EUR and are left out here. Azure File Sync costs EUR 4.3999 per registered server and month, the first server is free. For Azure NetApp Files the API lists EUR 0.0002 per GiB and hour for Standard, EUR 0.0004 for Premium, EUR 0.0005 for Ultra, EUR 0.0002 for Flexible plus EUR 0.0035 per MiB/s and hour, backup at EUR 0.0572 per GiB and month, and cool access at EUR 0.0001 per GiB and hour plus EUR 0.0187 per GiB retrieved. A GB in hot pay-as-you-go therefore costs about a seventh of a provisioned premium GB per month, but 10,000 hot write transactions cost more than two and a half GB of hot storage: pay-as-you-go pays off for quiet data, provisioned for active data.

Sources

Read on 2026-10-21. Microsoft Learn: Understand Azure Files billing, Plan an Azure File Sync deployment, Azure NetApp Files cost model, Azure NetApp Files service levels, About Azure Files backup, Azure Storage redundancy, Cost details fields, FOCUS cost and usage details schema. Prices: Azure Retail Prices API in EUR, Azure Files in Germany West Central, Azure File Sync, Azure NetApp Files.