Review Azure Files utilization, quota, and snapshots
On this page
Use Percentage File Share Utilization for a same-share capacity view where it is available. Treat quota, snapshot count, and account-level totals as separate signals rather than comparing one share's quota with an account-wide UsedCapacity value.
Why this is worth a look
Azure Files has provisioned v2, provisioned v1, and pay-as-you-go billing models. Provisioned v2 charges for provisioned storage, IOPS, and throughput regardless of actual use. Provisioned v1 provisions storage, with IOPS and throughput determined by provisioned storage. Pay-as-you-go is based on used storage, transactions, and data transfer. Azure Monitor defines Percentage File Share Utilization as used storage divided by provisioned share capacity. It separately defines File Share Capacity Quota as the upper limit in bytes and File Share Snapshot Count as the number of snapshots. Share snapshots are read-only and incremental, and changed content is stored in them, so snapshot activity belongs in the capacity review even though this view does not reconstruct the bill.
Run this check
CHECKLISTRead-only Azure Monitor procedure that keeps share utilization, quota, snapshot count, and account-level capacity in their documented scopes.
1. Open Azure Monitor Metrics Explorer from the Azure portal and select the Azure Files resource at the documented Microsoft.Storage/storageAccounts/fileServices scope.
2. Select Percentage File Share Utilization. Record the percentage for the target File Share dimension, where that dimension is available. The metric is calculated as used storage divided by provisioned share capacity.
3. Separately select File Share Capacity Quota and record its byte value for the same share and selected time window. Do not treat this quota metric as a usage metric.
4. Select File Share Snapshot Count for the same share and time window. Record the count and review snapshots as read-only, incremental copies whose changed content is stored.
5. If you also inspect UsedCapacity, label it account-level. For standard storage accounts it can include blob, table, file, and queue capacity, so do not compare it directly with one share's quota.
6. Interpret the result by billing model: provisioned v2 follows provisioned resources, provisioned v1 derives IOPS and throughput from provisioned storage, and pay-as-you-go includes used storage, transactions, and data transfer.
7. Review the invoice separately for charges outside this capacity view.
How to confirm it
- 01
Open the documented scope
Open Azure Monitor Metrics Explorer from the Azure portal. Select the Azure Files resource at the Microsoft.Storage/storageAccounts/fileServices scope, then choose the time window you want to review.
- 02
Read share utilization
Select Percentage File Share Utilization and record the percentage for the target File Share dimension where available. This metric represents used storage divided by the provisioned capacity of the file share.
- 03
Separate quota and snapshots
Select File Share Capacity Quota separately and record its value in bytes. Also record File Share Snapshot Count. Snapshots are read-only and incremental, and changed content is stored in them.
- 04
Check scope before interpreting cost
If you inspect UsedCapacity, label it account-level. In standard storage accounts it can include blob, table, file, and queue capacity. Interpret the result against the Azure Files billing model, then review the invoice separately for other charges.
Before making changes
This is a read-only Azure Monitor review, not invoice reconstruction. Assumptions: you can view the selected resource and metrics, and selected the correct subscription, storage account, file service, share dimension, and time window. The target is a classic share because the reference does not apply to Microsoft.FileShares resources. Share scope requires the File Share dimension; HDD pay-as-you-go metrics cover all shares in the account. Quota is bytes, utilization is percent, and snapshot count is a count.