Azure Files offers serverless file shares, accessible via SMB, NFS and FileREST protocols. Azure file shares can be mounted concurrently by clients in Azure VMs or from on-premises workstations running Windows, macOS, and Linux. Additionally, Azure File Sync allows caching and synchronization of Azure File shares on Windows Servers for local access.
Pricing Details
Azure Files supports two different media tiers of storage, SSD and HDD, which allow you to tailor your file shares to the performance and price requirements of your scenario:
- SSD (“premium”): File shares hosted on solid-state drives (SSDs) provide consistent high performance and low latency, within single-digit milliseconds for most IO operations.
- HDD (“standard”): File shares hosted on hard disk drives (HDDs) provide cost-effective storage for general purpose use.
Azure Files has multiple pricing models including provisioned and pay-as-you-go options. The following sections detail the specifics of each model to help you make a choice about which model works best for your scenario.
Provisioned v2
In a provisioned model, the primary costs of the Azure file share are based on the amount of storage, IOPS, and throughput you provision when you create or update your file share, regardless of how much you use. With the provisioned v2 billing model, you have the ability to separately provision storage, IOPS, and throughput, although we will recommend IOPS and throughput provisioning to you based on the amount of provisioned storage you select. We recommend provisioned v2 file shares for all new Azure Files deployments. For more information on the provisioned v2 billing model, see the provisioned v2 billing model.
| SSD | HDD | ||
|---|---|---|---|
| Quantity | LRS Price | LRS Price | GRS Price |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
￥0.001392 per provisioned GiB per hour | ￥0.000102 per provisioned GiB per hour | ￥0.000204 per provisioned GiB per hour |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
￥0.000378 per provisioned IO per sec per hour
First 3000 IOPS at no additional cost |
￥0.000558 per provisioned IO per sec per hour | ￥0.001122 per provisioned IO per sec per hour |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
￥0.000546 per provisioned MiB per sec per hour
First 3000 IOPS at no additional cost |
￥0.000834 per provisioned MiB per sec per hour | ￥0.001668 per provisioned MiB per sec per hour |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
￥0.001392 per used GiB per hour | ￥0.000102 per used GiB per hour | ￥0.000204 per used GiB per hour |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥0.001392 per used GiB per hour | ￥0.000102 per used GiB per hour | ￥0.000204 per used GiB per hour |
| SSD | HDD | |||||
|---|---|---|---|---|---|---|
| Quantity | LRS Price | ZRS Price | LRS Price | GRS Price | ZRS Price | GZRS Price |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
￥0.001392 per provisioned GiB per hour | ￥0.00174 per provisioned GiB per hour | ￥0.000102 per provisioned GiB per hour | ￥0.000234 per provisioned GiB per hour | ￥0.000126 per provisioned GiB per hour | ￥0.00027 per provisioned GiB per hour |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
￥0.000378 per provisioned IO per sec per hour
First 3000 IOPS at no additional cost |
￥0.000468 per provisioned IO per sec per hour First 3000 IOPS at no additional cost | ￥0.000558 per provisioned IO per sec per hour | ￥0.001284 per provisioned IO per sec per hour | ￥0.000702 per provisioned IO per sec per hour | ￥0.001422 per provisioned IO per sec per hour |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
￥0.000546 per provisioned MiB per sec per hour
First 3000 IOPS at no additional cost |
￥0.000696 per provisioned MiB per sec per hour First 3000 IOPS at no additional cost | ￥0.000834 per provisioned MiB per sec per hour | ￥0.00192 per provisioned MiB per sec per hour | ￥0.001044 per provisioned MiB per sec per hour | ￥0.002124 per provisioned MiB per sec per hour |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
￥0.001392 per used GiB per hour | ￥0.00174 per used GiB per hour | ￥0.000102 per used GiB per hour | ￥0.000234 per used GiB per hour | ￥0.000126 per used GiB per hour | ￥0.00027 per used GiB per hour |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥0.001392 per used GiB per hour | ￥0.00174 per used GiB per hour | ￥0.000102 per used GiB per hour | ￥0.000234 per used GiB per hour | ￥0.000126 per used GiB per hour | ￥0.00027 per used GiB per hour |
Provisioned v1
In a provisioned model, the primary costs of the Azure file share are based on the amount of storage, IOPS, and throughput you provision when you create or update your file share, regardless of how much you use. In the provisioned v1 billing model, there is one provisioned quantity for which you will pay for your file share: provisioned storage. When you create your file share, the provisioned IOPS and throughput available on your share are determined based on the amount of storage you provision. If you need more IOPS or throughput, you’ll need to provision additional storage. The provisioned v1 model is only available for SSD file shares. We recommend using the provisioned v2 billing model for new SSD file share deployments. For more information on the provisioned v1 billing model, see understanding the provisioned v1 billing model .
| SSD | ||
|---|---|---|
| Quantity | LRS Price | |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
￥1.626 per provisioned GiB per month | |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
￥1.386 per used GiB per month | |
|
Paid bursting transactions
Paid bursting is an advanced feature of the provisioned v1 model that can optionally be enabled to support usage-based billing whenever the IOPS go over the provisioned amount. Provisioned v1 also supports credit-based bursting for IOPS based on the amount of storage provisioned. |
￥5.088 per 1M transactions per month | |
| SSD | ||
|---|---|---|
| Quantity | LRS Price | ZRS Price |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
￥1.626 per provisioned GiB per month | ￥2.034 per provisioned GiB per month |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
￥1.386 per used GiB per month | ￥1.728 per used GiB per month |
|
Paid bursting transactions
Paid bursting is an advanced feature of the provisioned v1 model that can optionally be enabled to support usage-based billing whenever the IOPS go over the provisioned amount. Provisioned v1 also supports credit-based bursting for IOPS based on the amount of storage provisioned. |
￥5.088 per 1M transactions per month | ￥6.36 per 1M transactions per month |
Pay-as-you-go
In a pay-as-you-go model, the cost of the Azure file share is based on how much you use the file share, in the form of used storage, transaction, and data transfer costs. The pay-as-you-go model offers three “access tiers” on HDD storage which provide a way to balance the used storage versus used transaction prices:
- The transaction optimized access tier offers the lowest cost transaction pricing for transaction heavy workloads that don’t need the low latency offered by SSD file shares. The transaction optimized access tier is recommended for migrating data into file shares using the pay-as-you-go billing model.
- The hot access tier offers balanced storage and transaction pricing for workloads that have a good measure of both.
- The cool access tier offers the most cost-efficient storage pricing for storage-intensive workloads.
Pay-as-you-go is only available for HDD file shares. We recommend using the provisioned v2 billing model for new HDD file share deployments. For more information on the pay-as-you-go billing model, see understanding the pay-as-you-go billing model.
LRS
| TRANSACTION OPTIMIZED | HOT | COOL | |
|---|---|---|---|
|
Used storage
The logical storage size of the files stored on the Azure file share. |
￥ 0.612 per used GiB per month | ￥ 0.193 per used GiB per month | ￥ 0.114 per used GiB per month |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
￥ 0.612 per used GiB per month | ￥ 0.193 per used GiB per month | ￥ 0.114 per used GiB per month |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥ 0.612 per used GiB per month | ￥ 0.193 per used GiB per month | ￥ 0.114 per used GiB per month |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Included | ￥ 0.306 | ￥ 0.306 |
|
Write transactions (per 10,000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
¥0.10 | ¥0.055809 | ¥0.675895 |
|
List transactions (per 10,000)
List transactions are any operations which enumerate parts of the file share, such as listing files and directories within a share. |
¥0.10 | ¥0.055809 | ¥0.055809 |
|
Read transactions (per 10,000)
Read transactions are any operations which read from a file’s data stream. |
¥0.01 | ¥0.018603 | ¥0.067522 |
|
All other operations (per 10,000)
Any other operations associated with Azure Files (share, snapshot, directory, etc.), except for delete operations which are free. |
¥0.01 | ¥0.018603 | ¥0.018603 |
|
Data retrieval (per GiB)
Data retrieval is a special charge which applies only to retrieving data from cool storage. |
N/A | N/A | ¥0.087779 |
|
Early deletion (per GiB)
Early deletion charge is a special charge which applies only to deleting data from cool storage within 30 days of initial creation. There is no charge for deleting files older than 30 days. |
N/A | N/A | ¥0.165 |
GRS
| TRANSACTION OPTIMIZED | HOT | COOL | |
|---|---|---|---|
|
Used storage
The logical storage size of the files stored on the Azure file share. |
￥ 1.75 per used GiB per month | ￥ 0.4437 per used GiB per month | ￥ 0.261 per used GiB per month |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
￥ 1.75 per used GiB per month | ￥ 0.4437 per used GiB per month | ￥ 0.261 per used GiB per month |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥ 1.75 per used GiB per month | ￥ 0.4437 per used GiB per month | ￥ 0.261 per used GiB per month |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Included | ￥ 0.7038 | ￥ 0.7038 |
|
Write transactions (per 10,000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
¥0.20 | ¥0.128361 | ¥1.554559 |
|
List transactions (per 10,000)
List transactions are any operations which enumerate parts of the file share, such as listing files and directories within a share. |
¥0.10 | ¥0.128361 | ¥0.128361 |
|
Read transactions (per 10,000)
Read transactions are any operations which read from a file’s data stream. |
¥0.01 | ¥0.018603 | ¥0.067522 |
|
All other operations (per 10,000)
Any other operations associated with Azure Files (share, snapshot, directory, etc.), except for delete operations which are free. |
¥0.01 | ¥0.018603 | ¥0.018603 |
|
Data retrieval (per GiB)
Data retrieval is a special charge which applies only to retrieving data from cool storage. |
N/A | N/A | ¥0.087779 |
|
Early deletion (per GiB)
Early deletion charge is a special charge which applies only to deleting data from cool storage within 30 days of initial creation. There is no charge for deleting files older than 30 days. |
N/A | N/A | ¥0.33 |
ZRS
| TRANSACTION OPTIMIZED | HOT | COOL | |
|---|---|---|---|
|
Used storage
The logical storage size of the files stored on the Azure file share. |
￥ 0.76 per used GiB per month | ￥ 0.24 per used GiB per month | ￥ 0.14 per used GiB per month |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
￥ 0.76 per used GiB per month | ￥ 0.24 per used GiB per month | ￥ 0.14 per used GiB per month |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥ 0.76 per used GiB per month | ￥ 0.24 per used GiB per month | ￥ 0.14 per used GiB per month |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Included | ￥ 0.377 | ￥ 0.377 |
|
Write transactions (per 10,000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
¥0.19 | ¥0.07 | ¥0.84 |
|
List transactions (per 10,000)
List transactions are any operations which enumerate parts of the file share, such as listing files and directories within a share. |
¥0.15 | ¥0.07 | ¥0.07 |
|
Read transactions (per 10,000)
Read transactions are any operations which read from a file’s data stream. |
¥0.015 | ¥0.0186 | ¥0.068 |
|
All other operations (per 10,000)
Any other operations associated with Azure Files (share, snapshot, directory, etc.), except for delete operations which are free. |
N/A | ¥0.0186 | ¥0.0186 |
|
Data retrieval (per GiB)
Data retrieval is a special charge which applies only to retrieving data from cool storage. |
N/A | N/A | ¥0.088 |
|
Early deletion (per GiB)
Early deletion charge is a special charge which applies only to deleting data from cool storage within 30 days of initial creation. There is no charge for deleting files older than 30 days. |
N/A | N/A | N/A |
GZRS
| TRANSACTION OPTIMIZED | HOT | COOL | |
|---|---|---|---|
|
Used storage
The logical storage size of the files stored on the Azure file share. |
￥ 1.37 per used GiB per month | ￥ 0.66 per used GiB per month | ￥ 0.52 per used GiB per month |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
￥ 1.37 per used GiB per month | ￥ 0.66 per used GiB per month | ￥ 0.52 per used GiB per month |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
￥ 1.37 per used GiB per month | ￥ 0.66 per used GiB per month | ￥ 0.52 per used GiB per month |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Included | ￥ 0.68 | ￥ 0.68 |
|
Write transactions (per 10,000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
¥0.34 | ¥1.55 | ¥2.64 |
|
List transactions (per 10,000)
List transactions are any operations which enumerate parts of the file share, such as listing files and directories within a share. |
¥0.3 | ¥1.55 | ¥1.55 |
|
Read transactions (per 10,000)
Read transactions are any operations which read from a file’s data stream. |
¥0.015 | ¥0.0186 | ¥0.068 |
|
All other operations (per 10,000)
Any other operations associated with Azure Files (share, snapshot, directory, etc.), except for delete operations which are free.。 |
N/A | ¥0.11 | ¥0.11 |
|
Data retrieval (per GiB)
Data retrieval is a special charge which applies only to retrieving data from cool storage. |
N/A | N/A | ¥0.2 |
|
Early deletion (per GiB)
Early deletion charge is a special charge which applies only to deleting data from cool storage within 30 days of initial creation. There is no charge for deleting files older than 30 days. |
N/A | N/A | N/A |
File Sync Prices
These are the costs of syncing your files from Windows servers to Azure file shares in the cloud. Learn more about Azure File Sync.
The total cost of Azure File Sync services is determined by the number of servers that connect to the cloud endpoint (Azure file share) plus the underlying costs of Azure Files (including storage and access costs) and outbound data transfer.
Below is the fixed monthly fee per server.
| PRICE PER MONTH | |
|---|---|
| Sync Server* | ¥50.86 |
FAQ
Expand All-
If I create sharing with a 5 TB limit, will I be charged for the entire 5 TB or just the cost of the storage space used?
Only the storage space used is charged for standard file shares, rather than the allocated limit. Pricing for premium files shares is based on provisioned GiB and includes all transaction costs. You can configure your premium shares based on your storage size, IOPS, and throughput requirements.
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
We guarantee that we can successfully process data reading requests from an offsite redundant storage (RA-GRS) account at least 99.99% of the time (99.9% for the Cold Access Layer), provided that we will retry in the secondary zone from the data writing failure from the primary zone.
We guarantee that we can successfully process data reading from local redundant storage (LRS) and offsite redundant storage (GRS) accounts at least 99.9% of the time (99% for the Cold Access Layer)
We guarantee that we can successfully process data writing requests into onsite redundant storage (LRS) and geo-redundant storage (GRS) accounts and read and access geo-redundant storage (RA-GRS) accounts at least 99.9% of the time (99% for the Cold Access Layer).
To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.
The Managed Disk itself doesn’t provide a Service Level Agreement with financial support. The availability of a Managed Disk depends on the Service Level Agreement governing the basic storage used and the Virtual Machine it’s attached to. To learn more about the details of the Service Level Agreement of the Managed Disk, please visit the Managed Disk Service Level Agreements page.