
Snapshots are fast and cheap to use, but three decisions trip teams up: how snapshots work, how long to keep them, and what they cost. There's also a fourth question: when a snapshot isn't enough and Azure Backup should step in.
This guide covers each decision using Microsoft's current documentation. Verify limits and prices against Azure's own pages before you commit to a design.
Key Takeaways
- Snapshots are share-level, incremental recovery points for restoring files or directories.
- Retention is an operational policy tied to recovery goals, change rates, and compliance.
- Cost follows changed data and share configuration, not snapshot count.
- Pair snapshots with automation, access controls, monitoring, and tested restores.
What Is an Azure Files Snapshot and How Does It Work?
Scope and behavior
A snapshot captures the state of an entire share at one moment and presents it as read-only. Azure Files supports native snapshots for both SMB and NFS shares. You can't snapshot a single file. Instead, you pick a share-level recovery point and copy out the files or directories you need.
Each snapshot carries a timestamp. SMB clients see it as a token in the format @GMT-year.month.day-hour.minutes.seconds, such as @GMT-2023.01.05-00.08.20. During an incident, you match the timestamp to the last known-good moment and recover from there.
Incremental storage
Only data changed since the previous snapshot is saved. Microsoft's snapshot guide describes snapshot capacity as differential from the live share and other snapshots.
That means activity matters more than schedule. Two shares on the same hourly schedule can hold very different amounts of snapshot data: a quiet archive share adds little, while a share rewritten daily by a build pipeline adds a lot.
What snapshots protect, and what they don't
Snapshots cover accidental deletion, overwrites, renames, and application-level corruption. Say a script mistakenly renames 4,000 files. You browse to the snapshot taken before the run and copy the originals back.
The limits are just as important:
- Snapshots stay tied to the share and storage account. They can't outlive permanent deletion of the source share.
- Snapshots inherit the share's redundancy. With geo-redundant storage, they're also stored in the paired region, but they add no independent geographic protection.
- Native snapshots remain associated with the source share, so they aren't a ransomware-proof or rogue-administrator-proof copy.
How snapshots differ from related features
Azure Files share snapshots are not Blob snapshots. The recovery unit here is a file share, not a blob. They're also not Azure File Sync, which syncs on-premises file-server data with an SMB Azure file share.
A snapshot is a recovery mechanism. Redundancy, backup vaults, replication, and disaster-recovery services each address different failure scenarios.

Azure Files Snapshot Retention and Lifecycle Management
Design retention around recovery objectives
Start with your recovery point objective (how much data loss is tolerable) and recovery time objective (how fast you must be back). Then factor in business criticality, change frequency, and compliance rules.
Two patterns show the range:
- Project files that change hourly: frequent snapshots kept for a short operational window, enough to undo yesterday's mistake.
- Regulated or audit-sensitive data: fewer snapshots, kept far longer, with documented ownership.
Microsoft doesn't prescribe a universal schedule. Its guidance is to weigh frequency and retention against unnecessary charges.
Native retention management
You can create, list, and delete snapshots in the Azure portal, Azure CLI, and Azure PowerShell. For scheduling, Microsoft's training material points to Azure Automation, GitHub Actions, or CI schedulers.
The hard ceiling is 200 snapshots per share. At the limit, you must delete older snapshots before creating new ones. Nothing is overwritten automatically; snapshots persist until you delete them or the share is deleted.
Keeping everything forever raises cost and clutter. Deleting too aggressively removes recovery points you'll want later.
Manual scheduling vs. Azure Backup
Azure Backup applies scheduled policies, manages retention tiers, prunes expired recovery points, and provides restore workflows. Its published maximums for the snapshot tier include 200 daily days, 200 weeks, 120 months, and 10 years, with 200 total recovery points per share.
The vault tier goes much higher, though Microsoft's own pages conflict on the vault maximum (99 years in the support matrix, 10 years in the portal article). Treat these as ceilings, not recommended defaults, and confirm before designing around them.

A script or Azure Automation job may be enough for a few non-critical shares. For enterprise governance with many shares, audit needs, and central monitoring, a managed backup policy is the better fit.
Deletion safeguards
- Deleting a share that has snapshots fails with 409 Share Has Snapshots unless the request includes
x-ms-delete-snapshots=include. - Share soft delete defaults to 7 days (configurable from 1 to 365). Undeleting restores the share, contents, and snapshots.
- Azure Backup enables soft delete with 14-day retention and leases its snapshots.
- A CanNotDelete lock protects against Azure Resource Manager deletion, not file-data changes.
Separate roles, require change approval, alert on unexpected snapshot deletions, and name an owner for every retention policy.
Monthly retention review
- Check snapshot age and recovery-point coverage
- Look at storage growth
- Find failed automation runs
- Review the latest restore-test results
- Record legal-hold, audit, or regulatory exceptions so unmanaged snapshots do not pile up
Azure Files Snapshot Cost: What You Pay For
The main cost model
Snapshot cost depends on how much incremental data snapshots retain, the share's media and access tier, and redundancy. Snapshot count alone is a poor predictor. Fifty snapshots of a static share can cost less than ten of a churning one.
Billing also differs by model, according to Azure Files pricing:
| Billing model | Snapshot treatment |
|---|---|
| HDD pay-as-you-go | Used storage includes live data, differential snapshots, and soft-deleted shares |
| SSD provisioned v1 | Differential snapshot usage billed separately |
| Provisioned v2 | No extra snapshot charge while live data plus snapshots fit within provisioned capacity; excess is billed as Overflow Snapshot Usage |
Related charges
- Pay-as-you-go shares add transaction charges; the cool tier adds a data-retrieval meter that affects restore reads.
- Outbound data transfer is separate from snapshot capacity, and GRS replication has its own transfer meter.
- Azure Backup's snapshot tier adds a protected-instance fee plus Azure Files snapshot storage. Vaulted backup adds protected-instance and vault storage charges.
- Running both operational and vaulted protection can incur two protected-instance fees.
Prices vary by region and configuration, so use the Azure Backup pricing page and the Azure Files page rather than static numbers.
A practical estimation method
Estimate snapshot-held data like this:
- Take share size and estimate daily change volume.
- Multiply by retention days (a share with unique daily changes keeps roughly that much extra data).
- Apply your tier's rate and redundancy.
- Add expected restore reads and transfer.
Illustrative scenario (variables only): a 5 TB share with 2% daily change and 30 days of retention. Change volume is about 100 GB per day, so snapshot-held data could approach 3 TB if changes are all unique.

Overwrites of the same blocks lower that figure. Multiply by your region's rate for your tier, then validate in the Azure Pricing Calculator and compare against actual billing after deployment.
Cost trade-offs
- Frequent, short-retention snapshots: fine recovery granularity, modest storage if retention is short.
- Infrequent, long-retention snapshots: fewer recovery points, but older changes accumulate.
Delete expired snapshots, avoid duplicate protection policies, and watch high-churn shares.
If your estate also includes Azure managed disks or other block storage, Lucidity provides multi-cloud block-storage visibility and optimization. That is separate from Azure Files: snapshot pricing must still be evaluated through Azure's own configuration and billing model.
FinOps governance
- Tag or document shares by owner, environment, data classification, retention policy, and business purpose.
- Review costs by workload in Cost Analysis, which supports tags as a dimension.
- Alert on unexpected growth and assign owners to policy exceptions.
Note that Microsoft's independent per-share billing and tagging applies to top-level Microsoft.FileShares resources, currently NFS-only, so don't assume snapshot-level SMB cost attribution.
Restoring Files and Designing Protection Around Snapshots
Main restore paths
- Browse the snapshot and identify the right timestamp.
- Restore a file or directory by copying it back. A portal directory restore copies contents recursively to the original location.
- For a broader loss, copy files individually or rebuild the share.
Microsoft documents the portal, SMB/NFS, REST, client libraries, PowerShell, and CLI as recovery surfaces. Check current command syntax in the docs before scripting.
On Windows, Previous Versions in File Explorer works for SMB shares; Microsoft's client matrix lists SMB 3.1.1 on Windows 11 24H2 and Windows Server 2022. Previous Versions is SMB-only.
When Azure Backup protects the share, restore options change. Snapshot-tier recovery supports full-share and item-level restore, while vaulted recovery currently supports full-share only and needs target space at least 20% greater than the restored data.

Snapshots are not backups
A snapshot alone rarely meets backup requirements. It depends on the same storage environment, lacks isolation, and doesn't give alternate-location recovery. Microsoft identifies vaulted backup as protection against ransomware, rogue administrators, and source-data loss.
Choose Azure Backup or another approved design when you need policy-based retention, central monitoring, alternate-location recovery, or stronger protection against resource deletion.
Security and access controls
- Use least-privilege Azure RBAC; share-level permissions and Windows ACLs are both enforced.
- Prefer identity-based SMB access (AD DS, Microsoft Entra Domain Services, or Entra Kerberos) over storage keys.
- If you use keys, restrict retrieval, store them in Key Vault, and rotate them.
- Add private endpoints or firewall rules. Creating a private endpoint does not disable public access automatically.
- Data is encrypted at rest by default; require encrypted SMB 3.x.
Test your restores
Build periodic recovery drills around these checks:
- Test file-level and larger restores
- Validate permissions and metadata after restore
- Record recovery time against your RTO
- Confirm applications and SMB clients can use the data
Microsoft's cloud security benchmark calls for periodic recovery tests against RTO and RPO, though it sets no Files-specific interval.
Implementation Checklist and Best Practices
Setup sequence
- Identify critical shares that need point-in-time recovery.
- Choose a snapshot schedule that matches change frequency and RPO.
- Define retention so you stay under the 200-snapshot limit.
- Pick native automation or Azure Backup based on recovery and compliance needs.
- Configure access controls so only approved roles can create or delete snapshots.
- Document owners for schedule changes, restores, and cost review.

Take extra snapshots before migrations, bulk edits, releases, and content changes. Remove those temporary snapshots on schedule.
Monitor these signals
- Snapshot creation and retention-job failures
- Storage growth and approaching the 200-snapshot limit
- Unexpected deletions
- Restore-test outcomes
Decision checklist
- Fast operational recovery: native snapshots.
- Managed, policy-based protection: Azure Backup.
- Regional, compliance, or ransomware requirements: a broader backup and disaster-recovery architecture.
Limits, supported configurations, portal labels, and charges change. Verify current Azure documentation and pricing before you finalize.
Frequently Asked Questions
Is an Azure Files snapshot a backup?
Not by itself. A snapshot is a fast point-in-time recovery mechanism, but it may lack the isolation, retention governance, alternate-location recovery, and disaster protection of a full backup strategy.
How do I secure an Azure file share?
Use least-privilege RBAC and identity-based access, keep storage keys in Key Vault, restrict networks with private endpoints or firewalls, keep encryption on, and monitor activity.
Does Azure File Share support SMB?
Yes. Azure Files supports SMB 3.1.1, 3.0, and 2.1, and SMB needs TCP 445. SMB 2.1 is disallowed when encryption in transit is required, so check current Microsoft documentation for prerequisites.
How much does an Azure Files snapshot cost?
It depends on incremental changed data, the share's tier and redundancy, related transactions or transfers, and whether Azure Backup is used. Check current regional pricing.
How long should I retain Azure Files snapshots?
Base it on recovery objectives, change frequency, compliance, and restore testing. Keep short-term operational snapshots separate from long-term backup retention.