Azure Files (SMB, NFS, File Sync)
Azure Files provides fully managed file shares in the cloud that can be accessed using standard protocols. It’s Microsoft’s solution for replacing on-premises file servers.
Key Features
- SMB protocol: Access from Windows, Linux, and macOS just like a network drive (\\mystorage.file.core.windows.net\share).
- NFS protocol: Supports Linux-based workloads that need file shares.
- Azure File Sync: Synchronizes on-premises file servers with Azure Files, allowing local caching while storing everything in Azure.
- Supports snapshots for point-in-time recovery.
When to Use Azure Files
- Lift-and-shift of traditional file shares to the cloud.
- Applications that expect file system APIs (SMB/NFS) instead of object storage APIs (Blob).
- Hybrid environments where you want to keep local performance but sync to the cloud for scale and backup.
Confusion Buster 🚨
Azure Files vs Blob Storage
– Azure Files = file system protocols (SMB/NFS), mounts like a shared drive.
– Blob Storage = object storage, accessed via REST APIs, not directly mountable.
Exam trick: If the requirement is “mount like a drive,” always pick Azure Files.
Simple Example
Your company has an on-premises file server that stores 10 TB of department data. Instead of buying new hardware, you migrate it to Azure Files. Users continue accessing it via \\server\share, while Azure File Sync keeps on-prem and cloud in sync.
Exam Tip
If the scenario mentions “SMB”, “NFS”, or “lift-and-shift file shares”, the answer is almost always Azure Files. If it says “global access via REST API”, that’s Blob Storage.
What to Expect in the Exam
- Direct Q: “Which storage service provides SMB access?” → Azure Files.
- Scenario: “Company needs to sync on-premises file server with Azure.” → Azure File Sync.
- Trick Q: “Blob storage can be mounted directly as a Windows drive.” (False — only Azure Files can).