What Is Azure Files?
Azure Files provides fully managed file shares in the cloud that are accessible via the industry-standard SMB (Server Message Block) protocol and, for Linux clients, the NFS (Network File System) protocol. Because it speaks standard file-sharing protocols, a share can be mounted concurrently by multiple VMs, on-premises servers, or even developer laptops just like a traditional network drive, without any custom client software, making it a natural replacement for on-premises file servers.
Cricket analogy: Azure Files is like a shared team equipment room accessible by any squad member from any ground, using the standard kit-bag system everyone already knows, rather than each player needing a custom locker key.
SMB vs NFS Shares
SMB shares work across Windows, Linux, and macOS clients and are the most common choice, supporting features like Azure AD Domain Services authentication and standard file/directory permissions. NFS shares, available only on Premium (FileStorage) accounts, require the share to be accessed within a virtual network (no public internet access) and are favored by Linux-based workloads needing POSIX-compliant file semantics, such as certain database or container workloads that expect native Unix file locking behavior.
Cricket analogy: SMB is like the widely used standard bat everyone across all formats can pick up and use; NFS is like a specialized bat only allowed within a specific league's private nets, tuned for a narrower set of players.
# Mount an SMB Azure file share on Linux
sudo mkdir -p /mnt/azurefiles
sudo mount -t cifs //mystorageacct.file.core.windows.net/myshare /mnt/azurefiles \
-o vers=3.0,username=mystorageacct,password=<storage-account-key>,dir_mode=0777,file_mode=0777
# Mount the same share on Windows via PowerShell
New-PSDrive -Name Z -PSProvider FileSystem `
-Root "\\mystorageacct.file.core.windows.net\myshare" `
-Persist `
-Credential (Get-Credential)Azure File Sync
Azure File Sync lets you centralize an organization's file shares in Azure Files while keeping the performance and compatibility of an on-premises Windows Server file server, by installing a sync agent that creates a two-way sync between a local server and a cloud endpoint. Cloud tiering, an optional feature, keeps frequently accessed files cached locally while tiering infrequently used files to the cloud, only leaving a small pointer file on-premises, freeing up local disk space while the file still appears present to users.
Cricket analogy: It's like a franchise keeping frequently used training equipment at the local ground for quick access, while rarely used gear (old kit from past seasons) is stored centrally and shuttled back only when needed for a special event.
Azure File Sync supports multi-site sync, meaning multiple on-premises servers in different offices can sync to the same Azure file share, keeping branch offices consistent — a scenario that was difficult to achieve reliably with traditional DFS Replication alone.
Tiers and Quotas
Standard file shares (on GPv2 accounts) support Transaction Optimized, Hot, and Cool tiers analogous to Blob Storage tiers, letting you balance cost against transaction frequency, while Premium file shares (on FileStorage accounts) are provisioned with guaranteed IOPS and throughput based on the share size, similar to provisioned-IOPS disks. A single file share can scale up to 100 TiB when large file share support is enabled, and individual files within a share can be up to 4 TiB.
Cricket analogy: Transaction Optimized is like a pitch prepped for a high-frequency T20 league with constant matches; Cool tier is like a ground used only for the occasional exhibition game, cheaper to maintain but less battle-ready.
Transaction Optimized, Hot, and Cool tiers are only available on Standard (GPv2) file shares — Premium file shares on FileStorage accounts do not support tiering and are always billed on provisioned capacity, so factor that into cost planning when choosing between Standard and Premium shares.
- Azure Files provides fully managed cloud file shares accessible via standard SMB and NFS protocols.
- SMB shares work across Windows/Linux/macOS clients; NFS shares require Premium accounts and virtual network access only.
- Azure File Sync syncs on-premises Windows Server file shares with an Azure Files cloud endpoint for hybrid scenarios.
- Cloud tiering caches frequently used files locally and tiers infrequently used files to the cloud automatically.
- Multi-site sync lets several on-premises servers stay consistent by syncing to the same Azure file share.
- Standard shares offer Transaction Optimized, Hot, and Cool tiers; Premium shares use provisioned IOPS/throughput instead.
- A single file share can scale up to 100 TiB with large file share support enabled, with files up to 4 TiB each.
Practice what you learned
1. Which protocol requires a Premium FileStorage account and access only within a virtual network?
2. What is the main purpose of Azure File Sync's cloud tiering feature?
3. Which file share tiers are available on Standard (GPv2) accounts?
4. How are Premium file shares typically billed?
Was this page helpful?
You May Also Like
Azure Blob Storage
Azure's massively scalable object storage service for unstructured data, covering blob types, access tiers, and security controls.
Azure Storage Account Types
A guide to choosing between general-purpose and premium Azure storage account kinds, and how performance and redundancy tiers interact.
Azure Storage Redundancy Options
A comparison of Azure Storage's LRS, ZRS, GRS, and GZRS redundancy options and how to choose between them.