Separate File Sync tiering exclusions from immediate local recall

Source facts

Azure File Sync tiering exclusions do not apply to files already tiered; Microsoft directs administrators to Invoke-StorageSyncFileRecall for those files. Matching files changed or created at another endpoint still download as tiered files and are gradually recalled, with the documented interval being three to four days.

File-name or file-type exclusions apply to every server endpoint on that server. A file-type exclusion cannot be restricted to one particular folder. The source also requires restarting the Storage Sync Agent service for changed tiering exclusions to take effect. Microsoft Learn.

Applicability

Identify the server, all its endpoints, matching existing placeholders and the files arriving from other endpoints. Do not equate an exclusion entry with a verified local copy.

DSE recommendation

DSE recommends deciding whether the requirement is future tiering prevention or immediate content availability. Review exclusion scope across the server and plan any required recall with capacity and change owners. Use the documented recall mechanism; do not manipulate reparse points to manufacture a local-looking file state. Schedule the necessary service restart through the approved maintenance process.

Verification

Test a matching locally created file, an existing tiered file and a matching remote-created file separately. Observe actual file state and read availability rather than only the registry setting. Document when each became local and investigate differences from the expected path before promising immediate offline readiness.

Official references

Microsoft Learn: How to manage Azure File Sync tiered files. Source retrieved September 9, 2026.