Last updated: May 2026
Azure Storage Intermediate AZ-104 ⏱ 13 min read

Azure File Storage

Azure File Storage provides fully managed file shares in the cloud — accessible via the industry-standard SMB (Server Message Block) and NFS (Network File System) protocols. Think of it as a network drive in the cloud that multiple VMs and on-premises servers can mount simultaneously, just like a traditional file server — but without the hardware to manage.

What you'll learn What Azure File Storage is · SMB vs NFS protocols · Creating file shares · Mounting on Windows VMs · Mounting on Linux VMs · Azure File Sync — extending to on-premises · Performance tiers · Snapshots and backup · When to use File Storage vs Blob Storage

What is Azure File Storage?

Azure File Storage provides cloud file shares that can be accessed and mounted by multiple machines simultaneously — just like a traditional on-premises file server, but fully managed in Azure. No hardware to provision, no OS to patch, no storage to manage.

ℹ️
Replacing On-Premises File Servers Many organisations still run Windows file servers for shared storage. Azure File Storage can replace these — with the same SMB access that Windows machines already understand — while eliminating the hardware, maintenance, and DR overhead.

Key Features

  • Fully managed — no file servers to maintain
  • Accessible via SMB 3.x and NFS 4.1 protocols
  • Multiple machines can mount the same share simultaneously
  • Accessible from Azure VMs, on-premises servers, and Windows/Mac/Linux machines
  • Up to 100 TB per file share
  • Integrated backup via Azure Backup

SMB vs NFS

SMB (Server Message Block)NFS (Network File System)
Best forWindows workloadsLinux workloads
Supported OSWindows, Linux, macOSLinux only
AuthenticationAzure AD, storage account keyNetwork-based (VNet)
Internet accessYes (over TLS)No — VNet only
Storage tierStandard and PremiumPremium only

Creating a File Share

Azure CLI Create a file share
# Create a file share (100 GB quota)
az storage share create \
  --name myfileshare \
  --account-name mystorageaccount2026 \
  --quota 100 \
  --auth-mode login

# List file shares
az storage share list \
  --account-name mystorageaccount2026 \
  --output table \
  --auth-mode login

Mounting on Windows

The Azure Portal provides a ready-to-use PowerShell script for mounting the file share on Windows. Here's how:

  1. Go to your Storage Account → File shares → select your share
  2. Click Connect
  3. Select Windows
  4. Choose a drive letter (e.g., Z:)
  5. Copy and run the provided PowerShell script on your Windows machine
PowerShell Mount Azure File Share on Windows (example)
# The Portal generates this script automatically
$connectTestResult = Test-NetConnection -ComputerName mystorageaccount2026.file.core.windows.net -Port 445
if ($connectTestResult.TcpTestSucceeded) {
    # Mount the share
    cmd.exe /C "cmdkey /add:`"mystorageaccount2026.file.core.windows.net`" /user:`"localhost\mystorageaccount2026`" /pass:`"[storage-account-key]`""
    New-PSDrive -Name Z -PSProvider FileSystem -Root "\\mystorageaccount2026.file.core.windows.net\myfileshare" -Persist
} else {
    Write-Error "Unable to reach storage account — check port 445 is open"
}
⚠️
Port 445 Must Be Open SMB uses port 445. Many ISPs and corporate firewalls block outbound port 445. If you can't mount the share from on-premises, port 445 is likely blocked. For on-premises connectivity, use Azure VPN Gateway or ExpressRoute.

Mounting on Linux

Bash Mount Azure File Share on Linux (Ubuntu)
# Install CIFS utilities (for SMB)
sudo apt-get install cifs-utils -y

# Create mount point
sudo mkdir /mnt/myfileshare

# Mount the share
sudo mount -t cifs \
  //mystorageaccount2026.file.core.windows.net/myfileshare \
  /mnt/myfileshare \
  -o vers=3.0,username=mystorageaccount2026,password=[storage-account-key],dir_mode=0777,file_mode=0777

# Make it persistent (add to /etc/fstab)
echo "//mystorageaccount2026.file.core.windows.net/myfileshare /mnt/myfileshare cifs nofail,vers=3.0,username=mystorageaccount2026,password=[key],dir_mode=0777,file_mode=0777 0 0" | sudo tee -a /etc/fstab

Azure File Sync

Azure File Sync transforms your Windows Server into a cache for an Azure file share. It replicates files between on-premises Windows Server and Azure Files — giving you fast local access with cloud-based centralised storage.

How It Works

  1. Install the Azure File Sync agent on your Windows Server
  2. Register the server with a Storage Sync Service in Azure
  3. Create a sync group linking a server endpoint (on-premises folder) to a cloud endpoint (Azure file share)
  4. Files are synchronised bidirectionally
  5. With cloud tiering enabled: rarely accessed files are replaced with pointers on the local server, while the full file stays in Azure. When accessed, it's transparently downloaded.
💡
Use Case A company has branch offices in Chennai, Mumbai, and Delhi, all needing access to the same shared files. Instead of a VPN to a central file server, each office runs Azure File Sync — users get fast local access, and all changes sync to the Azure file share automatically.

Performance Tiers

TierStorageIOPSBest For
Standard (Transaction Optimised)HDD-backedUp to 1,000General file sharing, moderate workloads
Standard (Hot)HDD-backedUp to 1,000Frequently accessed shares
Standard (Cool)HDD-backedUp to 1,000Infrequently accessed archives
PremiumSSD-backedUp to 100,000+Databases, high-performance applications

Share Snapshots

Azure File shares support point-in-time snapshots — read-only copies of the entire file share at a specific moment. Useful for:

  • Recovering accidentally deleted or modified files
  • Backing up before major changes
  • Compliance and audit requirements
Azure CLI Create a share snapshot
# Create a snapshot
az storage share snapshot \
  --name myfileshare \
  --account-name mystorageaccount2026 \
  --auth-mode login

File Storage vs Blob Storage

FactorFile StorageBlob Storage
Access protocolSMB, NFS (mountable)HTTP/REST API
Mount as drive?Yes — like a network driveNo
Best forShared files between VMs/serversStoring files accessed via URL/API
Max file size4 TB per file190.7 TB (block blob)
Access tiersStandard Hot/Cool, PremiumHot, Cool, Cold, Archive
Use caseReplacing file servers, shared configWeb assets, backups, data lakes
💡
AZ-104 Exam Tip Know that File Storage uses SMB (Windows) and NFS (Linux) protocols, that SMB uses port 445, that Azure File Sync allows on-premises Windows Server to cache Azure file shares, and that File Storage can be mounted as a network drive. Key difference from Blob: File Storage is mountable; Blob is not.
📝 Practice Questions
Click an option to check your answer. AZ-104 style questions.
Q1. Which protocol does Azure File Storage use for Windows-based file sharing?
A SMB (Server Message Block)
B FTP
C HTTP/REST
D SSH (SFTP)
Q2. What port does SMB use, and why does this matter for Azure File Storage?
A Port 22 — often blocked by home routers
B Port 445 — often blocked by ISPs and corporate firewalls
C Port 443 — requires certificate installation
D Port 3389 — requires firewall exceptions
Q3. What is Azure File Sync used for?
A Syncing Azure Blob Storage with on-premises object storage
B Caching Azure file shares on Windows Server for fast local access while syncing to Azure
C Replicating Linux servers to Azure file shares
D Synchronising code repositories with Azure DevOps
Q4. What is the key difference between Azure File Storage and Azure Blob Storage?
A File Storage stores larger files than Blob Storage
B Blob Storage is more expensive than File Storage
C File Storage can be mounted as a network drive (SMB/NFS); Blob Storage cannot
D Only File Storage supports geo-replication
Q5. How many machines can mount the same Azure file share simultaneously?
A Only 1 machine at a time
B Up to 10 machines
C Multiple machines simultaneously — from Azure VMs, on-premises servers, and workstations
D Only VMs within the same VNet
Comments
Disclaimer: RedKite Cloud is an independent educational resource and is not affiliated with, endorsed by, or officially connected to Microsoft Corporation. All product names, logos, and trademarks are property of their respective owners. Content is written independently for educational purposes only.