{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "slug": "dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall", "url": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/" }, "title": "Separate File Sync tiering exclusions from immediate local recall", "summary": "An exclusion does not instantly recall already-tiered content or prevent every remote file from arriving as a placeholder.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:26:27+00:00", "modified_at": "2026-09-10T01:40:03+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 237, "potentially_affected": "Windows Server Azure File Sync endpoints with cloud tiering enabled.", "dse_recommendation": "Plan local-content readiness separately from configuring a tiering exclusion.", "primary_source": { "name": "How to manage Azure File Sync tiered files | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-how-to-manage-tiered-files", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nAzure 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.\nFile-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.\nApplicability\nIdentify 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.\nDSE recommendation\nDSE 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.\nVerification\nTest 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.\nOfficial references\nMicrosoft Learn: How to manage Azure File Sync tiered files. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nAzure 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.\n\nFile-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](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-how-to-manage-tiered-files).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nTest 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.\n\n## Official references\n\n[Microsoft Learn: How to manage Azure File Sync tiered files](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-how-to-manage-tiered-files). Source retrieved September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "url": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate File Sync tiering exclusions from immediate local recall", "item": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "url": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/", "headline": "Separate File Sync tiering exclusions from immediate local recall", "description": "An exclusion does not instantly recall already-tiered content or prevent every remote file from arriving as a placeholder.", "abstract": "An exclusion does not instantly recall already-tiered content or prevent every remote file from arriving as a placeholder.", "articleBody": "Source facts\nAzure 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.\nFile-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.\nApplicability\nIdentify 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.\nDSE recommendation\nDSE 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.\nVerification\nTest 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.\nOfficial references\nMicrosoft Learn: How to manage Azure File Sync tiered files. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:26:27+00:00", "dateModified": "2026-09-10T01:40:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-329-separate-file-sync-tiering-exclusions-from-immediate-local-recall/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Separate File Sync tiering exclusions from immediate local recall" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 237, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "How to manage Azure File Sync tiered files | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-how-to-manage-tiered-files" } } ] } }