Azure Files

File shares that use the standard SMB 3.0 protocol

Updated on:2025/11/05

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

Prices marked as N/A indicate that the redundancy option is not available in the selected region. Note: File operations that result in data transfer outside of an Azure datacenter will incur additional outbound data transfer charges.

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.

Provisioned v2 file shares are billed hourly at an hourly rate.
Monthly prices shown in the table above are based on a 744-hour month.

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 .

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.

FAQ

Expand All

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.