
Introduction
Azure Files Premium gives you managed SMB or NFS file shares backed by SSD, built for workloads that need low latency and predictable performance. Microsoft describes single-digit-millisecond latency for most I/O operations. The pricing works very differently from standard shares.
Many teams assume the bill tracks the data they store. It doesn't. You pay for what you provision, whether or not you use it. Region, redundancy, snapshots, backup, and network services pile on top.
This guide covers current East US pricing in USD, the two Premium billing models, the cost components beyond the base rate, and a budgeting process. Rates reflect East US pricing as of November 18, 2026. Microsoft's pricing page shows no publication date, and the figures are estimates, not quotes.
Key Takeaways
- Premium shares bill on provisioned resources, not just data stored.
- Provisioned v2 prices capacity, IOPS, and throughput separately; v1 bundles them.
- Snapshots, backup, redundancy, and networking raise the bill past the base rate.
- The best configuration is the cheapest one that meets your performance and recovery needs.
How Much Does Azure Files Premium Cost?
There is no single monthly price. Your cost depends on region, redundancy (LRS or ZRS), and billing model. Microsoft bills provisioned resources regardless of actual use, so an empty 10 TiB share costs the same as a full one.
Typical Premium Pricing Model
East US SSD rates, per month (Microsoft bases monthly prices on 730 hours):
| SSD resource | LRS | ZRS | Unit |
|---|---|---|---|
| v1 provisioned capacity | $0.16 | $0.20 | Per GiB |
| v2 provisioned capacity | $0.1001 | $0.1249 | Per GiB |
| v2 IOPS above first 3,000 | $0.0271 | $0.0336 | Per IOPS |
| v2 throughput above first 100 MiB/s | $0.0395 | $0.0497 | Per MiB/s |
v1 has no separate performance meter. Baseline IOPS is min(3000 + S, 102400) and throughput is 100 + ceil(0.04*S) + ceil(0.06*S) MiB/s, where S is provisioned GiB. More performance means buying more capacity.
v2 is billed hourly, and you choose capacity, IOPS, and throughput independently. Subtract the free allowances (3,000 IOPS, 100 MiB/s) before multiplying.
The framework:
- v1: provisioned GiB × capacity rate
- v2: GiB × capacity rate + (IOPS − 3,000) × IOPS rate + (MiB/s − 100) × throughput rate
- Then add: snapshots, backup, network, and monitoring charges
Illustrative Cost Scenarios
These are calculations from the rates above, not benchmarks. Assumptions: East US, one share, 730 hours, no reservations, snapshots, bursting, backup, or networking. For v1, capacity is sized to hit the stated baseline.
| Scenario | v1 LRS / ZRS | v2 LRS / ZRS |
|---|---|---|
| Small AKS app: 100 GiB, 3,000 IOPS, 100 MiB/s | $16.00 / $20.00 | $10.01 / $12.49 |
| Medium database: 1,024 GiB, 8,000 IOPS, 500 MiB/s | $800.00 / $1,000.00 (5,000 GiB provisioned) | $253.80 / $315.78 |
| Large enterprise: 10,240 GiB, 40,000 IOPS, 2,000 MiB/s | $5,920.00 / $7,400.00 (37,000 GiB provisioned) | $2,102.77 / $2,616.61 |
The medium and large v1 figures include extra capacity bought purely to reach the IOPS target. These are calculated costs for specific targets, not universal savings.

Key Factors That Affect Azure Files Premium Pricing
Cost follows technical configuration, workload behavior, resilience needs, and contract choices. Data volume is only one input.
Billing Model and Premium Configuration
The two models differ in how they tie performance to capacity:
| Spec | Provisioned v1 | Provisioned v2 |
|---|---|---|
| Share size | 100 GiB to 100 TiB | 32 GiB to 256 TiB |
| Baseline | 3,100 IOPS, 110 MiB/s | 3,000 IOPS, 100 MiB/s |
| Performance | Fixed formulas tied to capacity | Independent, with guardrails |
| Reservations | Available | Not available |
v2 fits workloads that need high IOPS or throughput without matching storage. v1 fits stable, capacity-heavy shares where a reservation applies. Confirm regional availability before committing.
Capacity, IOPS, and Throughput
Measure before you size. Pull peak and sustained IOPS, throughput, and used capacity from Azure Monitor. Overprovisioning wastes money every hour. Underprovisioning causes latency problems and emergency resizing.
Microsoft's recommended v2 values are min(max(3000 + ceil(S), 3000), 102400) IOPS and min(max(100 + ceil(0.1*S), 100), 10340) MiB/s, where S is provisioned share size in GiB. You can set performance up to five times those recommendations.
Redundancy, Region, and Commitments
SSD shares support only LRS and ZRS, not GRS or GZRS. ZRS costs about 25% more per GiB in East US. ZRS is also limited to a subset of regions.
Region matters too. In West US, v1 LRS runs $0.176/GiB-month, versus $0.16/GiB-month in East US.
Reservations apply to v1 only, in 10 TiB or 100 TiB blocks for one or three years. Microsoft publishes savings up to 36% for three years. Reserve your stable baseline, not temporary peaks. Reservations exclude snapshot and data-transfer charges.
Related Services and Usage
- Transactions are included in provisioned shares
- Optional v1 paid bursting is billed separately
- Snapshots, backup, private endpoints, and data transfer all carry their own meters (covered below)
Check the Azure Pricing Calculator against your actual Azure Cost Management bill before you lock a budget.

Azure Files Premium Cost Breakdown
The base share rate is one slice of the total. Separate recurring provisioned charges from usage-based and periodic ones.
Base capacity and performance
Recurring. You pay for provisioned capacity and, on v2, provisioned IOPS and throughput. Charges follow what you allocate, not what you use.
Redundancy and resilience
Recurring. ZRS raises the per-GiB rate. Backup and replication sit outside the share price.
Snapshots, backup, and data protection
Recurring or periodic. Snapshots are differential and bill on used GiB:
| Component | LRS | ZRS |
|---|---|---|
| v1 snapshot storage | $0.1360/GiB | $0.17/GiB |
| v2 overflow snapshot storage | $0.1001/GiB | $0.1249/GiB |
v1 bills all differential snapshot usage. v2 bills only usage that exceeds provisioned capacity: max(live used + snapshot GiB − provisioned GiB, 0).
Azure Backup adds its own fees. East US rates include:
- Snapshot management: $5/month for instances over 250 GB
- Vaulted protected instance (1 TB or more): $10/month
- Standard vault storage: $0.041/GB-month (LRS) or $0.048/GB-month (ZRS)
Backup-created snapshots also incur share snapshot storage charges. NFS shares have limits: snapshot backup is in private preview, and vaulted backup isn't available.
Network and operational charges
Usage-based or recurring.
- Internet egress: first 100 GB/month free, then $0.087/GB for the next 10 TB
- Cross-region transfer in North America: $0.02/GB
- Private endpoint: $0.01/hour, plus $0.01/GB processed for the first 1 PB
- Azure Monitor: platform metrics are free; logs incur ingestion charges

Low-Cost vs High-Cost Premium Configurations
"Low cost" should mean right-sized, not the smallest share. A 100 GiB v2 LRS share at about $10/month suits a light app. It would choke a database.
A high-cost setup, such as 10 TiB, 40,000 IOPS, and ZRS at roughly $2,617/month, is justified for production databases, AI workloads, or strict recovery objectives.
To cut cost without hurting performance:
- Evaluate v2 when IOPS needs outrun capacity needs
- Right-size from measured metrics
- Reserve stable v1 baselines
- Monitor continuously
How to Estimate the Right Azure Files Premium Budget
Start with fit, not headline price. Define these inputs before you price anything:
- Capacity and expected growth
- Protocol (SMB or NFS)
- Performance targets (IOPS and throughput)
- Availability and redundancy needs
- Retention policy for snapshots and backup
Estimation Workflow
- Measure current usage with the
UsedCapacitymetric. - Find peak and sustained IOPS and throughput using
Transactions by Max IOPSandBandwidth by Max MiB/s. - Select the billing model by comparing v1 and v2 for your numbers.
- Add redundancy and protection: LRS or ZRS, snapshots, backup, and networking.
- Validate in the Azure Pricing Calculator, then compare against Cost Management.
Run a sensitivity check next. Model growth, traffic spikes, performance changes, and rate changes instead of budgeting only today's baseline.
Resizing has its own constraint: you can reduce a provisioned quantity only after 24 hours since its last increase.

What Most Estimates Miss
- Lightly used shares still bill in full.
- Underestimated peaks lead to performance incidents and rushed resizing.
- Snapshots, backup retention, redundancy, and transfer charges often get left out of estimates.
Enterprise FinOps teams also run block storage next to their file shares. Lucidity is an intelligence layer for cloud block storage that gives those teams visibility and autonomous right-sizing across AWS, Azure, and Google Cloud. It does not manage Azure Files shares, but it can cover the block volumes sitting beside them.
Conclusion
Azure Files Premium pricing reflects the billing model, provisioned capacity and performance, redundancy, region, protection services, and workload usage. An accurate budget combines Microsoft's current regional rates with measured requirements and the full lifecycle cost.
Skip the lowest headline rate. Pick the configuration that balances performance, availability, simplicity, and long-term value.
Frequently Asked Questions
How much does Azure file share cost?
It depends on the tier, billing model, provisioned capacity and performance, region, redundancy, and related services. In East US, Premium LRS starts at $0.16/GiB-month (v1) or $0.1001/GiB-month (v2). Use the Azure Pricing Calculator for current rates.
What is the difference between Azure file share and Blob storage?
Azure Files offers managed shared file access over SMB or NFS, plus REST. Blob Storage is object storage for unstructured data, accessed through REST or client libraries. Your access pattern decides the better fit.
Is Azure file share SMB?
Yes. Azure Files supports SMB, and Premium shares also support NFS 4.1, but not both on one share. REST is supported with resource-type limits. Verify protocol availability for your deployment.
How is Azure Files Premium billed?
You pay for provisioned capacity, plus provisioned IOPS and throughput on v2. Region, redundancy, snapshots, backup, and networking change the final bill. Reservations can lower v1 costs.
What is the difference between Azure Files Premium provisioned v1 and provisioned v2?
v1 ties IOPS and throughput to capacity (100 GiB to 100 TiB). v2 lets you set capacity, IOPS, and throughput independently (32 GiB to 256 TiB). Only v1 supports reservations.
How can I reduce Azure Files Premium costs?
Measure your workload, rightsize, and compare v2 against v1. Remove unneeded snapshots and redundancy, reserve stable v1 baselines, and review Azure Cost Management regularly.