
Introduction
Windows file servers keep growing. Disks fill up, expansions are expensive, and keeping every file fully cached on every server is a risk nobody wants to own at 2 a.m. when a volume hits zero free space.
Azure File Sync cloud tiering offers a way out. The namespace stays visible while less frequently accessed file content lives in Azure Files and comes back when someone opens it. The catch: the wrong settings can swap a disk problem for a recall problem.
This article covers the settings that matter, how to match them to workloads, how to monitor results, and how to keep total cost honest.
Key Takeaways
- Tiering frees local cache space; the full dataset stays in the Azure file share.
- Free space and date policies decide eligibility, so tune them per endpoint.
- Initial download, exclusions, and backup tools can quietly consume local disk.
- Judge savings against Azure Files, transaction, backup, and egress costs.
How Azure File Sync Cloud Tiering Works
The building blocks
Azure File Sync centralizes file shares in Azure Files while keeping the performance and compatibility of Windows file servers. A few resources make that work:
- Storage Sync Service: the root Azure resource managing sync relationships
- Sync group: ties one cloud endpoint to one or more server endpoints
- Cloud endpoint: an Azure file share
- Server endpoint: a path on a registered Windows Server
What tiering does locally
Folder hierarchy and file properties stay on the server. A filter driver replaces tiered content with a reparse point, and the file is flagged offline. Open it, and the requested data is recalled from the Azure share. Partial recall is supported.
Sync, tiering, and backup are different things
- Sync propagates changes between endpoints.
- Tiering decides how much content stays cached on one server.
- Neither is backup. Azure Files access tiers (premium, transaction optimized, hot, cool) are a separate, cloud-side storage and pricing choice.
Treat the three as separate decisions with separate owners.
The Azure File Sync Settings That Control Local Storage
Enable tiering per server endpoint
Cloud tiering is configured on each server endpoint, at creation or later. Evaluate each one on its own disk size, users, and workload.
Check these before touching production:
- The endpoint cannot be on the system volume
- The volume must be directly attached NTFS (not ReFS or FAT)
- Windows Server 2016, 2019, 2022, or 2025
- Only files larger than 64 KiB tier
- Microsoft advises against tiering with NTFS-compressed files, and EFS does not interoperate
Confirm current details in the Microsoft planning guide first.
Configure the volume free space policy
This policy targets free space across the whole volume, not just the endpoint folder. Coldest files tier first. If several endpoints share a volume, the highest percentage wins for all of them.
Microsoft recommends starting at 10-20%, usually 20%, with the date policy disabled. Leave headroom for the OS and applications too.
Microsoft's own example: on a 500 GiB volume, a 20% policy leaves roughly 400 GiB of cache. At 70%, only 150 GiB remains.
That figure is an illustration, not a benchmark, so test with realistic file creation and access patterns. On a sudden disk shortage, the server enters low-disk mode and serves recalled content without persisting it.

Set the date policy around real access patterns
The date policy tiers files not accessed for a set number of days. An aggressive value hammers active project, collaboration, and seasonal data with recalls. Compare any proposed value with access telemetry, business cycles, and project lifecycles.
How the two policies combine matters:
- Free space takes precedence, so a file younger than the date threshold can still tier
- The date policy can tier older files even when plenty of space is free
Per Microsoft, a 60-day date policy does not protect a younger file from tiering when free space runs short.
Review initial download behavior
This is chosen at endpoint creation and cannot be changed later.
| Portal choice | Best for |
|---|---|
| Namespace only | Fast availability, on-demand content, disaster recovery |
| Namespace first (then modified files) | Quick access to recent files |
| Avoid tiered files | Workloads needing all content local |
Match the choice to the server's role. Validate application compatibility and permissions before users hit on-demand recalls.
Protect files that must remain local
Options are narrower than many admins expect:
- A
GhostingExclusionListregistry key excludes names, extensions, or paths from future tiering - Already-tiered files need a separate recall with
Invoke-StorageSyncFileRecall - Files excluded from sync cannot tier, and in-use files wait
- The
Pattribute is sparse, not a persistent pin
Good candidates: latency-sensitive application data and constantly used working sets. Too many exclusions erode your savings, so review them as part of endpoint governance.
Tune gradually, one change at a time
- Inventory the endpoint and record free space and access patterns
- Change one policy
- Watch tiering and recall behavior
- Document the result
Pilot on a representative server before rolling out. Use current Az.StorageSync cmdlets such as Set-AzStorageSyncServerEndpoint (with -VolumeFreeSpacePercent and -TierFilesOlderThanDays), not legacy AzureRM commands.

Choose Cloud-Tiering Settings by Workload
Hot and latency-sensitive shares
Keep a larger local working set and a gentler date policy. Squeezing out maximum savings means hot files get tiered and rehydrated repeatedly, adding latency and user frustration.
Cold or archive-like shares
Completed projects, departmental records, and reference data tolerate aggressive tiering. But tiering isn't archival storage. Verify retention, compliance, and retrieval requirements separately.
Bursty, seasonal, or project-based workloads
Review policies before predictable spikes such as quarter-end reporting or an engineering release. Last year's access pattern may not predict the next cycle, so check recall activity after each shift.
Multi-site deployments
Changes propagate through the central share, yet each server sees different slices of the namespace. Set policies per endpoint using local access patterns, disk capacity, and connectivity. Note that sync bandwidth limits exclude tiered-file access, so recalls at a remote site can exceed the cap you set.
Backup, security, and compliance workloads
Antivirus, backup, and indexing can trigger recalls. Microsoft notes antivirus can recall files and raise egress charges, and Windows Search skips tiered files. Key points:
- Protect the cloud endpoint, which holds the full dataset
- Don't back up a tiered server or its VM as a substitute
- Bare-metal, VM, and tiered-file-level restores are unsupported with tiering on
- Document exceptions for regulated files and test recovery of both cached and tiered content
Monitor and Validate Tiering
Check health and status
In the Azure portal, use Storage Sync Service > Registered servers for server health, and Sync groups > your group > endpoint for errors and cloud tiering status. Endpoint fields include space savings, cached size, effective free space policy, and cache hit rate.
For scripting, use Get-AzStorageSyncServerEndpoint. On the server, use Get-StorageSyncFileTieringResult, Get-StorageSyncFileRecallResult, and Debug-StorageSyncServer -Diagnose.
Track the signals that matter
Watch local free space, tiered bytes, recall volume, sync errors, latency, and Azure Files transactions. Azure Monitor metrics include StorageSyncTieredDataSizeBytes, StorageSyncRecalledTotalNetworkBytes, and StorageSyncLowDiskModeCount.

A falling cache hit rate with rising recalls of the same files means the policy is churning, not saving.
Test before and after changes
- Record a baseline first
- Define rollback conditions before making any policy more aggressive
- Check file types, permissions, namespace visibility, and application behavior
- Time recalls for typical files
- Confirm backup behavior and test a recovery
Cost Controls and Operational Guardrails
Model total cost, not disk savings alone
Official pricing lists $5 per server per month for registered sync servers, but that's only one line. The full dataset stays in Azure, so you also pay for:
- Share capacity (provisioned or used)
- Transactions, including one ListFiles call per directory per day
- Snapshots and backup
- Outbound transfer and recall egress
A smaller cache isn't a lower bill if users keep recalling the same content.
Establish governance
- Assign an owner to every server endpoint
- Document policy values and exceptions
- Review access and recall patterns regularly
- Alert on low free space, sync failures, and excessive daily recalls
- Test new values, tell users what to expect, and revert when workloads change
A note on block storage
Teams running Azure VM disks alongside Azure Files may look at Lucidity for visibility and autonomous optimization of cloud block storage. It does not replace Azure File Sync or configure file-share tiering, and block storage controls and pricing differ from Azure Files.
Frequently Asked Questions
How much does Azure File Sync cost?
Pricing combines a per-server fee (listed at $5 per month) with Azure Files capacity, transactions, snapshots, backup, and outbound transfer. Check Microsoft's current pricing page for your region.
What happens to data when cloud tiering is disabled?
Already tiered files stay as placeholders until accessed. Run Invoke-StorageSyncFileRecall to hydrate them, and make sure the disk has room first. Nothing is deleted.
What are the different tiers of Azure file storage access?
Azure Files offers premium (SSD) and standard transaction optimized, hot, and cool tiers. These are cloud-share choices, separate from local cloud-tiering policies.
What is File Sync in Azure?
Azure File Sync synchronizes Azure file shares with Windows Server endpoints. Optional cloud tiering keeps hot content local and moves infrequently accessed content to Azure Files.
How do I check Azure File Sync status?
Use the portal's Registered servers, endpoint errors, and Cloud tiering status views. Add Azure Monitor, Get-AzStorageSyncServerEndpoint, Debug-StorageSyncServer, and agent event logs.