Your share contains 300 GiB of files, yet Azure bills 1,024 GiB of capacity. That need not be an error: provisioned models charge for allocated resources. The next surprise can arrive when you reduce capacity and a new snapshot charge appears. Both effects can be explained before changing the configuration.
Content reviewed on 18 November 2026. We distinguish provisioned v2, provisioned v1 and pay-as-you-go. All calculations are hypothetical; none of the figures is a price quotation or measured saving.
Identify the billing model first
The name Azure Files, or the use of SMB, does not establish how a share is billed. Microsoft's current billing guide describes three models. V2 provisions capacity, IOPS and throughput separately. V1 links performance to provisioned capacity. Pay-as-you-go charges for consumed resources and billable operations.
| Model | Basis for checking costs | Common estimation mistake |
|---|---|---|
| Provisioned v2 | Provisioned capacity, IOPS and MiB/s; additional usage components | Counting only the current file volume |
| Provisioned v1 | Provisioned capacity with linked performance; assess snapshots separately | Applying the v2 snapshot overflow rule |
| Pay-as-you-go | Used capacity, transaction categories and other applicable rates | Treating one user action as one transaction |
Record the resource ID, region, redundancy, SSD/HDD medium, model and protocol. Only then compare the Azure Files price list. The same number of GiB in a different configuration is not an equivalent offer. Also distinguish Azure Files from Azure NetApp Files: they are different services.
For new deployments, Microsoft generally recommends provisioned v2 unless there is a specific reason to choose otherwise. This recommendation is not a savings calculation for an existing share. Assess a model change together with migration, downtime and functional requirements, rather than merely changing a label in the calculator.
V2: spare capacity can accommodate snapshots
Snapshots are not complete new copies of the share every time. Azure tracks differential data against live files and between snapshots; multiplying the number of snapshots by the whole share size is wrong. The snapshot documentation explains the mechanism.
With provisioned v2, differential snapshot data that fits inside unused provisioned capacity incurs no additional snapshot storage charge. Only the amount by which live data plus snapshot differentials exceeds provisioned capacity enters the Overflow Snapshot Usage meter. Microsoft's formula is max(live data GiB + differential snapshot data GiB − provisioned capacity GiB, 0).
This does not mean “free backups”. Azure Backup can have other billed components and its own rules. Nor should the v2 rule be transferred to v1 or pay-as-you-go. Confusing the models can lead to the mistaken conclusion that every snapshot charge duplicates storage already paid for.

Model: reducing capacity creates a new line item
Assume a constant 300 GiB of live data and 400 GiB of differential snapshot data. The share has 1,024 GiB provisioned. An administrator wants to reduce this to 512 GiB while leaving IOPS and throughput unchanged for simplicity. This is our explanatory model, not a recommended production size.
| Option | Provisioned capacity | Live data + snapshots | Snapshot overflow |
|---|---|---|---|
| Original state | 1,024 GiB | 300 + 400 = 700 GiB | max(700 − 1,024, 0) = 0 GiB |
| After reduction | 512 GiB | 700 GiB | max(700 − 512, 0) = 188 GiB |
| Reduction in provisioned capacity | 512 GiB | Data has not changed | A new 188 GiB overflow charge appears |
The actual price change depends on two rates. For the same hour, call the provisioned capacity rate p and the snapshot overflow rate s, both per GiB per hour. The original sum of those two components is 1,024 × p. The new sum is 512 × p + 188 × s. The saving from reducing capacity is 512 × p − 188 × s.
Without the actual rates, a percentage saving cannot be announced. Even subtracting 512 − 188 GiB does not calculate the price when the components have different unit rates. Add any changes to IOPS, throughput and other services. The calculation is exact for the stated point in time; an invoice accumulates changing usage over the period.

Why invoice quantities can look enormous
Provisioned v2 emits consumption units every hour. If 1,024 GiB remains provisioned throughout November's 30 days, the result is 1,024 × 24 × 30 = 737,280 hourly capacity consumption units. This does not mean 737,280 GiB of unique files was stored. It is capacity accumulated over 720 hours.
When checking an export, first read the meter's unit and how your contract expresses its price. Do not combine an hourly quantity with a per-GiB-month price without conversion. Nor should every calendar month automatically be treated as 730 hours. If capacity changes partway through the period, total the individual intervals.
| Line item or metric | What to check | What it does not establish alone |
|---|---|---|
| Provisioned Storage | Allocated GiB and duration of each interval | Current live file size |
| Provisioned IOPS / Throughput | Purchased performance and throughput units | That all purchased performance was consumed |
| Overflow Snapshot Usage | Snapshot differentials and spare v2 capacity | The price of other backup components |
| Soft-Deleted Usage | Deleted shares still within retention | That deletion immediately ended every charge |
| Pay-as-you-go transactions | Operation categories and quantities | The number of clicks in File Explorer |
Transactions, File Sync and deleted shares
The Azure Files FAQ explains that one user action can generate multiple protocol transactions. Pay-as-you-go transaction categories can carry different rates. For provisioned shares, transaction counts do not increase billing in that way. Interpret a high operation count only after identifying the model.
Azure File Sync adds another layer: it changes cloud share data, uses snapshots and consumes performance. On pay-as-you-go, its operations can also affect transaction charges. Check synchronization and endpoint behaviour using Azure File Sync monitoring guidance. The cost of an on-premises server or a server in another cloud may not appear in the Azure Files line item at all.
A deleted share protected by soft delete has a different lifecycle from permanently removed data. For v2, Microsoft bills used capacity during retention. The deleted share's provisioned capacity, IOPS and throughput are not billed, although they still count against account limits until purging. Check recovery rules in the soft delete documentation.
Reservations are not an automatic v2 discount
The current Azure Files Reservations rules exclude provisioned v2. Reservations are available for SSD provisioned v1 and selected HDD pay-as-you-go hot/cool tiers; they do not cover every transaction and transfer. Older advice to “buy a capacity reservation” cannot be applied to any share indiscriminately.
When comparing a reserved model with v2, hold data volume, performance, redundancy, snapshots and expected duration constant. For a different service and commitment type, see our article on Azure reservations and Savings Plan; product-specific rules are not interchangeable.
Build the evidence for a budget change
- Export costs for the same period, separating resource ID, meter, quantity, unit and actual price.
- Reconstruct provisioned capacity, IOPS and throughput changes, then compare them with the hours in the export.
- For v2, separate live data, snapshot differentials and overflow. Check soft-deleted shares as well.
- For pay-as-you-go, distinguish transaction categories and operation sources, particularly with File Sync.
- Calculate the proposed configuration using consistent rates and intervals; add operational headroom and any migration costs.
For v2, also account for restrictions on reducing provisioned resources: the documentation allows a decrease only 24 hours after the last increase. A trial increase just before month-end is therefore not a cost-free experiment. Calculate the change first and assess its effect on performance and recoverability.
Frequently asked questions
Why am I paying for 1 TiB when I have only 300 GiB of data?
Provisioned models charge for allocated capacity. In v2, unused allocation can also accommodate differential snapshot data. Identify the model first; folder size alone does not explain the bill.
Are provisioned v2 snapshots always free?
No. They avoid an additional snapshot storage charge only to the extent that they fit within spare provisioned capacity. The excess is billed as Overflow Snapshot Usage. Other backup services can have their own charges.
Can reducing capacity create a new charge?
Yes. In our model, reducing 1,024 GiB to 512 GiB creates 188 GiB of snapshot overflow. The total price effect depends on real rates and other components, not merely live data size.
Does an Azure Files Reservation discount provisioned v2?
Not under the current documentation. Provisioned v2 is excluded from Azure Files Reservations. Verify the precise model and current offer before committing.
Does a million transactions increase every share's price?
No. Transaction billing depends on the model. Distinguish operation categories for pay-as-you-go; transaction counts do not increase provisioned share billing in the same way. Assess File Sync, backup and other services separately.








