Skip to content
Calcrivo

Azure Files Calculator

Size an Azure file share and derive premium baseline IOPS, burst IOPS and throughput from the provisioned GiB.

Inputs

GiB
USD/GiB-month
GiB
USD/GiB-month
millions/month
USD
GiB

Monthly Cost

$195.84

Baseline IOPS

1,424IOPS

Burst IOPS

4,272IOPS

Total Throughput

202MiB/s

Capacity Charge

$163.84

Transaction Charge

$0.00

Step by step

  1. Values used

    Share type = Premium (provisioned SSD); Provisioned size (premium) = 1,024 GiB; Premium price per provisioned GiB = 0.1600 USD/GiB-month; Data stored (standard) = 800 GiB; Standard price per GiB used = 0.0255 USD/GiB-month; Transactions (standard) = 40 millions/month; Price per 10,000 transactions = 0.0150 USD; Snapshot data stored = 200 GiB

  2. Azure Files

    Premium baseline IOPS = 400 + 1 per provisioned GiB (capped at 102,400); burst = max(4,000, 3 × baseline); throughput MiB/s = (40 + 0.04 × GiB) ingress + (60 + 0.06 × GiB) egress.

  3. Monthly Cost

    = 195.84

  4. Baseline IOPS

    = 1,424 IOPS

  5. Burst IOPS

    = 4,272 IOPS

  6. Total Throughput

    = 202 MiB/s

  7. Capacity Charge

    = 163.84

  8. Transaction Charge

    = 0.00

How it works

A premium file share is provisioned, not consumed: you pay for the size you declare and Azure grants performance from that same number, which is why growing the share is also the way to buy IOPS and throughput. Standard shares invert the model — you pay for what you store plus every transaction, but performance is fixed and much lower. Teams hit the IOPS ceiling of a premium share long before they fill it, and the fix is counter-intuitive: provision more GiB. Confirm the per-GiB and per-transaction prices for your region in the Azure pricing calculator, since standard shares also differ by access tier.

Formula

Azure Files

Premium baseline IOPS = 400 + 1 per provisioned GiB (capped at 102,400); burst = max(4,000, 3 × baseline); throughput MiB/s = (40 + 0.04 × GiB) ingress + (60 + 0.06 × GiB) egress.

provisioned GiB
Share size you commit to and pay for, whether used or not
baseline IOPS
Sustained IOPS entitlement scaling linearly with provisioned size
burst IOPS
Credit-backed short-term ceiling, three times baseline

Frequently Asked Questions

How is Azure Files calculated?

Premium baseline IOPS = 400 + 1 per provisioned GiB (capped at 102,400); burst = max(4,000, 3 × baseline); throughput MiB/s = (40 + 0.04 × GiB) ingress + (60 + 0.06 × GiB) egress. A premium file share is provisioned, not consumed: you pay for the size you declare and Azure grants performance from that same number, which is why growing the share is also the way to buy IOPS and throughput. Standard shares invert the model — you pay for what you store plus every transaction, but performance is fixed and much lower.

Why does Azure Files matter?

Teams hit the IOPS ceiling of a premium share long before they fill it, and the fix is counter-intuitive: provision more GiB. Confirm the per-GiB and per-transaction prices for your region in the Azure pricing calculator, since standard shares also differ by access tier.

What values do I need to enter?

This calculator takes 8 inputs: Share type, Provisioned size (premium), Premium price per provisioned GiB, Data stored (standard), Standard price per GiB used, Transactions (standard), Price per 10,000 transactions, Snapshot data stored. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

You might also need