🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided AZ-104 Domain 2
Domain 2 — Module 5 of 5 100%
11 of 27 overall

AZ-104 Study Guide

Domain 1: Manage Azure Identities and Governance

  • Microsoft Entra ID: Your Identity Foundation Free
  • Users, Groups & Licenses Free
  • RBAC: Who Can Do What in Azure Free
  • Subscriptions, Resource Groups & Management Groups Free
  • Azure Policy & Resource Locks Free
  • Tags, Cost Management & Azure Advisor Free

Domain 2: Implement and Manage Storage

  • Storage Accounts & Redundancy
  • Securing Storage: Keys, SAS & Firewalls
  • Blob Containers & Storage Tiers
  • Blob Lifecycle, Versioning & Soft Delete
  • Azure Files: Shares, Snapshots & Recovery

Domain 3: Deploy and Manage Azure Compute Resources

  • ARM Templates & Bicep: Infrastructure as Code
  • Virtual Machines: Create & Configure Free
  • VM Disks, Encryption & Migration
  • Availability Sets, Zones & Scale Sets
  • Containers: ACR, ACI & Container Apps
  • App Service Plans & Scaling
  • App Service: Slots, Certificates & Networking

Domain 4: Implement and Manage Virtual Networking

  • Virtual Networks & Subnets
  • VNet Peering & User-Defined Routes
  • NSGs & Application Security Groups
  • Azure Bastion, Service & Private Endpoints
  • Azure DNS & Load Balancers

Domain 5: Monitor and Maintain Azure Resources

  • Azure Monitor: Metrics & Logs
  • Alerts, Insights & Network Watcher
  • Azure Backup & Vaults
  • Azure Site Recovery & Disaster Recovery

AZ-104 Study Guide

Domain 1: Manage Azure Identities and Governance

  • Microsoft Entra ID: Your Identity Foundation Free
  • Users, Groups & Licenses Free
  • RBAC: Who Can Do What in Azure Free
  • Subscriptions, Resource Groups & Management Groups Free
  • Azure Policy & Resource Locks Free
  • Tags, Cost Management & Azure Advisor Free

Domain 2: Implement and Manage Storage

  • Storage Accounts & Redundancy
  • Securing Storage: Keys, SAS & Firewalls
  • Blob Containers & Storage Tiers
  • Blob Lifecycle, Versioning & Soft Delete
  • Azure Files: Shares, Snapshots & Recovery

Domain 3: Deploy and Manage Azure Compute Resources

  • ARM Templates & Bicep: Infrastructure as Code
  • Virtual Machines: Create & Configure Free
  • VM Disks, Encryption & Migration
  • Availability Sets, Zones & Scale Sets
  • Containers: ACR, ACI & Container Apps
  • App Service Plans & Scaling
  • App Service: Slots, Certificates & Networking

Domain 4: Implement and Manage Virtual Networking

  • Virtual Networks & Subnets
  • VNet Peering & User-Defined Routes
  • NSGs & Application Security Groups
  • Azure Bastion, Service & Private Endpoints
  • Azure DNS & Load Balancers

Domain 5: Monitor and Maintain Azure Resources

  • Azure Monitor: Metrics & Logs
  • Alerts, Insights & Network Watcher
  • Azure Backup & Vaults
  • Azure Site Recovery & Disaster Recovery
Domain 2: Implement and Manage Storage Premium ⏱ ~11 min read

Azure Files: Shares, Snapshots & Recovery

Azure Files gives you fully managed SMB file shares in the cloud — the Azure equivalent of your on-prem file server. Learn how to create file shares, configure snapshots, set up soft delete, and understand identity-based authentication.

What is Azure Files?

☕ Simple explanation

Azure Files is a file server in the cloud that speaks the same language as your on-prem shares.

If you’ve managed Windows file servers with SMB shares (the kind you map as a network drive like \server\share), Azure Files does exactly the same thing — but without a server to maintain. Users map a drive letter, open files in Explorer, save documents, just like before. The difference? The data lives in Azure, backed by Microsoft’s infrastructure.

It also supports NFS for Linux workloads, making it useful for both Windows and Linux environments.

Azure Files is a fully managed file share service that supports the SMB (Server Message Block) protocol (versions 2.1, 3.0, 3.1.1) and NFS (Network File System) protocol (v4.1). File shares are accessible from Windows, Linux, and macOS clients via standard file system APIs.

Azure Files exists within a storage account and supports two tiers: Standard (HDD-backed, general purpose v2 storage account) and Premium (SSD-backed, FileStorage account, provisioned model with guaranteed IOPS).

Key use cases: lift-and-shift of on-prem file servers, shared application configuration, diagnostic log storage, and hybrid scenarios with Azure File Sync.

Creating and configuring file shares

Key settings when creating a file share:

SettingOptionsNotes
NameLowercase letters, numbers, hyphensMust be 3-63 characters
ProtocolSMB or NFSNFS requires Premium tier
Quota1 GB to 100 TiBSets maximum size; can be increased later
TierHot, Cool, Transaction Optimised (Standard) or PremiumAffects cost model
Access tierTransaction Optimised (default), Hot, CoolStandard tier only

Premium vs Standard file shares:

Standard vs Premium file shares
FeatureStandard File SharesPremium File Shares
Storage typeHDD (hard disk)SSD (solid state)
Account kindStorageV2 (general-purpose v2)FileStorage
Billing modelPay for what you useProvisioned (pay for capacity, get guaranteed IOPS)
Max share size100 TiB (with large file share enabled)100 TiB
IOPSUp to 20,000 (burst)Up to 100,000 (provisioned)
ProtocolsSMB onlySMB and NFS
RedundancyLRS, ZRS, GRS, GZRSLRS, ZRS
Real-world: TechCorp's file server migration

TechCorp Solutions migrated their on-prem file servers to Azure Files:

  • Before: 4 Windows Servers running SMB shares, backed up to tape weekly
  • After: 2 Azure File shares (one for active documents, one for archives)
  • Users map the same drive letters (Z: and Y:) but they point to Azure Files
  • Authentication via on-prem AD DS (hybrid identity with Entra Connect)
  • Azure File Sync keeps a hot cache on a local server for fast access

Result: no more patching file servers, no more tape backups, and users didn’t notice the change.

File share snapshots

Azure Files supports share snapshots — read-only, point-in-time copies of the entire file share.

Key facts:

  • Snapshots are taken at the share level (entire share, not individual files)
  • They’re incremental — only changes since the last snapshot are stored
  • Maximum 200 snapshots per file share
  • Snapshots can be browsed and individual files restored via Windows “Previous Versions” tab
  • Deleting a share with snapshots requires deleting all snapshots first (or using “Delete share including snapshots”)

Soft delete for file shares

Soft delete retains deleted file shares for a configurable period (1-365 days), allowing recovery.

How it works:

  1. Enable soft delete on the storage account (applies to all file shares)
  2. Set retention period (e.g., 14 days)
  3. When a file share is deleted, it moves to a “soft deleted” state
  4. During retention, the share can be undeleted (restored)
  5. After retention expires, the share is permanently deleted

Important: Soft delete protects the file share (the container), not individual files within it. If a user deletes a file from a share, soft delete won’t help — you need snapshots for that.

💡 Exam tip: Snapshots vs Soft Delete

This distinction is commonly tested. Soft delete protects against share-level deletion (someone deletes the entire file share). Snapshots protect against file-level changes (someone overwrites or deletes a specific file within the share). For maximum protection, enable both.

Question

What is the difference between soft delete and snapshots in Azure Files?

Click or press Enter to reveal answer

Answer

Soft delete protects against accidental deletion of the entire file share (retains deleted shares for N days). Snapshots protect against file-level changes by creating point-in-time copies that allow restoring individual files. They serve different purposes and both should be enabled.

Click to flip back

Question

What protocol does Azure Files support, and which tier is required for NFS?

Click or press Enter to reveal answer

Answer

Azure Files supports SMB (2.1, 3.0, 3.1.1) and NFS (4.1). NFS requires Premium file shares (FileStorage account type with SSD storage). Standard file shares support SMB only.

Click to flip back

Question

How many snapshots can a single Azure file share have?

Click or press Enter to reveal answer

Answer

A maximum of 200 share snapshots per file share. Snapshots are incremental — they only store data that changed since the last snapshot, making them space-efficient.

Click to flip back

Knowledge check

Knowledge Check

A user at TechCorp Solutions accidentally deleted an important spreadsheet from an Azure File share yesterday. Soft delete is enabled on the storage account. Can Alex recover the file?

Knowledge Check

Meridian Financial needs a high-performance file share for their database log files. The share must support both Windows (SMB) and Linux (NFS) clients with guaranteed IOPS. What should Alex provision?

🎬 Video coming soon

← Previous

Blob Lifecycle, Versioning & Soft Delete

Next →

ARM Templates & Bicep: Infrastructure as Code

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.