{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
        "slug": "dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/"
        },
        "title": "Move File Sync and storage resources with their tenant relationship intact",
        "summary": "DSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "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-17T16:32:27+00:00",
        "modified_at": "2026-09-17T16:46:28+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 216,
        "potentially_affected": "This review is for an Azure File Sync resource-group, subscription, or tenant move that could change the administrative relationship between synchronization and storage resources.",
        "dse_recommendation": "DSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move.",
        "primary_source": {
            "name": "Azure File Sync Resource Moves and Topology Changes | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move",
            "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": "<h2>Source facts</h2>\n<p>Microsoft warns that placing the Storage Sync Service and associated storage accounts under different Entra tenants is unsupported, even if synchronization initially appears to work. When moving tenants, the guide requires sync and storage resources to move together. It says relevant RBAC assignments do not migrate with moved storage resources and sync access must be reauthorized. <a href=\"https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a></p>\n<h2>Applicability</h2>\n<p>This review is for an Azure File Sync resource-group, subscription, or tenant move that could change the administrative relationship between synchronization and storage resources.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move. Have the identity and storage owners approve the target relationship and reauthorization plan together. Keep application availability during the transition in the change plan, and define how access will be restored if the move stops synchronization. Do not use a momentary successful sync as approval for an unsupported target arrangement.</p>\n<h2>Verification</h2>\n<p>After the authorized move, inspect the tenant and subscription of every related top-level resource. Verify the required sync authorization and a controlled synchronization operation. Record the final relationship and any missing permission as explicit evidence, and resolve an unsupported split before considering the move complete.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft: Azure File Sync Resource Moves and Topology Changes | Microsoft Learn</a></li>\n</ul>",
        "content_text": "Source facts\nMicrosoft warns that placing the Storage Sync Service and associated storage accounts under different Entra tenants is unsupported, even if synchronization initially appears to work. When moving tenants, the guide requires sync and storage resources to move together. It says relevant RBAC assignments do not migrate with moved storage resources and sync access must be reauthorized. Microsoft Learn\nApplicability\nThis review is for an Azure File Sync resource-group, subscription, or tenant move that could change the administrative relationship between synchronization and storage resources.\nDSE recommendation\nDSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move. Have the identity and storage owners approve the target relationship and reauthorization plan together. Keep application availability during the transition in the change plan, and define how access will be restored if the move stops synchronization. Do not use a momentary successful sync as approval for an unsupported target arrangement.\nVerification\nAfter the authorized move, inspect the tenant and subscription of every related top-level resource. Verify the required sync authorization and a controlled synchronization operation. Record the final relationship and any missing permission as explicit evidence, and resolve an unsupported split before considering the move complete.\nOfficial references\n\nMicrosoft: Azure File Sync Resource Moves and Topology Changes | Microsoft Learn",
        "content_markdown": "## Source facts\n\nMicrosoft warns that placing the Storage Sync Service and associated storage accounts under different Entra tenants is unsupported, even if synchronization initially appears to work. When moving tenants, the guide requires sync and storage resources to move together. It says relevant RBAC assignments do not migrate with moved storage resources and sync access must be reauthorized. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move)\n\n## Applicability\n\nThis review is for an Azure File Sync resource-group, subscription, or tenant move that could change the administrative relationship between synchronization and storage resources.\n\n## DSE recommendation\n\nDSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move. Have the identity and storage owners approve the target relationship and reauthorization plan together. Keep application availability during the transition in the change plan, and define how access will be restored if the move stops synchronization. Do not use a momentary successful sync as approval for an unsupported target arrangement.\n\n## Verification\n\nAfter the authorized move, inspect the tenant and subscription of every related top-level resource. Verify the required sync authorization and a controlled synchronization operation. Record the final relationship and any missing permission as explicit evidence, and resolve an unsupported split before considering the move complete.\n\n## Official references\n\n- [Microsoft: Azure File Sync Resource Moves and Topology Changes | Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move)"
    },
    "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-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Move File Sync and storage resources with their tenant relationship intact",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/",
                "headline": "Move File Sync and storage resources with their tenant relationship intact",
                "description": "DSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move.",
                "abstract": "DSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move.",
                "articleBody": "Source facts\nMicrosoft warns that placing the Storage Sync Service and associated storage accounts under different Entra tenants is unsupported, even if synchronization initially appears to work. When moving tenants, the guide requires sync and storage resources to move together. It says relevant RBAC assignments do not migrate with moved storage resources and sync access must be reauthorized. Microsoft Learn\nApplicability\nThis review is for an Azure File Sync resource-group, subscription, or tenant move that could change the administrative relationship between synchronization and storage resources.\nDSE recommendation\nDSE recommends building one inventory of the Storage Sync Service, associated storage accounts, subscriptions, and governing tenants before the move. Have the identity and storage owners approve the target relationship and reauthorization plan together. Keep application availability during the transition in the change plan, and define how access will be restored if the move stops synchronization. Do not use a momentary successful sync as approval for an unsupported target arrangement.\nVerification\nAfter the authorized move, inspect the tenant and subscription of every related top-level resource. Verify the required sync authorization and a controlled synchronization operation. Record the final relationship and any missing permission as explicit evidence, and resolve an unsupported split before considering the move complete.\nOfficial references\n\nMicrosoft: Azure File Sync Resource Moves and Topology Changes | Microsoft Learn",
                "datePublished": "2026-09-17T16:32:27+00:00",
                "dateModified": "2026-09-17T16:46:28+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/"
                },
                "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-20260917-153-move-file-sync-and-storage-resources-with-their-tenant-relationship-intact/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Move File Sync and storage resources with their tenant relationship intact"
                },
                "articleSection": [
                    "IT"
                ],
                "keywords": [
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 216,
                "timeRequired": "PT1M",
                "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": "Azure File Sync Resource Moves and Topology Changes | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-resource-move"
                }
            }
        ]
    }
}