{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "slug": "dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service", "url": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/" }, "title": "Assign source, destination, and orchestrator roles for Storage Migration Service", "summary": "Which migration roles and inventory decisions should be established before data transfer?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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-08T18:16:30+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 216, "potentially_affected": "Use this review when planning a Storage Migration Service project.", "dse_recommendation": "Create a role map that names the machine responsible for orchestration separately from the data endpoints.", "primary_source": { "name": "Storage Migration Service overview", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview", "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

Storage Migration Service inventories supported Windows, Linux, and NetApp CIFS sources and transfers data to newer servers or Azure virtual machines. Microsoft distinguishes source, destination, orchestrator, and management-interface roles. For one migrating server, the destination can also orchestrate; for several, the source recommends a separate orchestrator. Identity cutover is optional and occurs after the data-transfer stage. Microsoft documentation.

\n

Applicability

\n

Use this review when planning a Storage Migration Service project. Identify the source types, destination versions, number of servers, and management tools. Verify the complete current support requirements before including a source in the inventory.

\n

DSE recommendation

\n

Create a role map that names the machine responsible for orchestration separately from the data endpoints. Have data owners review the inventory and proposed destinations before approving transfer. Record which servers need an eventual identity handoff and which need only copied data. Keep transfer acceptance and the optional cutover decision as separate milestones.

\n

Verification

\n

Compare the discovered inventory with the approved source list and reconcile missing or unexpected data before copying. After an authorized transfer, inspect the recorded results and sample destination files with their owners. Preserve the role map and transfer evidence. Proceed to identity cutover only under its separately reviewed plan for the accepted endpoints.

\n

Official references

\n

Microsoft Learn: Storage Migration Service overview. Source reviewed September 8, 2026.

", "content_text": "Source facts\nStorage Migration Service inventories supported Windows, Linux, and NetApp CIFS sources and transfers data to newer servers or Azure virtual machines. Microsoft distinguishes source, destination, orchestrator, and management-interface roles. For one migrating server, the destination can also orchestrate; for several, the source recommends a separate orchestrator. Identity cutover is optional and occurs after the data-transfer stage. Microsoft documentation.\nApplicability\nUse this review when planning a Storage Migration Service project. Identify the source types, destination versions, number of servers, and management tools. Verify the complete current support requirements before including a source in the inventory.\nDSE recommendation\nCreate a role map that names the machine responsible for orchestration separately from the data endpoints. Have data owners review the inventory and proposed destinations before approving transfer. Record which servers need an eventual identity handoff and which need only copied data. Keep transfer acceptance and the optional cutover decision as separate milestones.\nVerification\nCompare the discovered inventory with the approved source list and reconcile missing or unexpected data before copying. After an authorized transfer, inspect the recorded results and sample destination files with their owners. Preserve the role map and transfer evidence. Proceed to identity cutover only under its separately reviewed plan for the accepted endpoints.\nOfficial references\nMicrosoft Learn: Storage Migration Service overview. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nStorage Migration Service inventories supported Windows, Linux, and NetApp CIFS sources and transfers data to newer servers or Azure virtual machines. Microsoft distinguishes source, destination, orchestrator, and management-interface roles. For one migrating server, the destination can also orchestrate; for several, the source recommends a separate orchestrator. Identity cutover is optional and occurs after the data-transfer stage. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview).\n\n## Applicability\n\nUse this review when planning a Storage Migration Service project. Identify the source types, destination versions, number of servers, and management tools. Verify the complete current support requirements before including a source in the inventory.\n\n## DSE recommendation\n\nCreate a role map that names the machine responsible for orchestration separately from the data endpoints. Have data owners review the inventory and proposed destinations before approving transfer. Record which servers need an eventual identity handoff and which need only copied data. Keep transfer acceptance and the optional cutover decision as separate milestones.\n\n## Verification\n\nCompare the discovered inventory with the approved source list and reconcile missing or unexpected data before copying. After an authorized transfer, inspect the recorded results and sample destination files with their owners. Preserve the role map and transfer evidence. Proceed to identity cutover only under its separately reviewed plan for the accepted endpoints.\n\n## Official references\n\n[Microsoft Learn: Storage Migration Service overview](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview). Source reviewed September 8, 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-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "url": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Assign source, destination, and orchestrator roles for Storage Migration Service", "item": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "url": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/", "headline": "Assign source, destination, and orchestrator roles for Storage Migration Service", "description": "Which migration roles and inventory decisions should be established before data transfer?", "abstract": "Which migration roles and inventory decisions should be established before data transfer?", "articleBody": "Source facts\nStorage Migration Service inventories supported Windows, Linux, and NetApp CIFS sources and transfers data to newer servers or Azure virtual machines. Microsoft distinguishes source, destination, orchestrator, and management-interface roles. For one migrating server, the destination can also orchestrate; for several, the source recommends a separate orchestrator. Identity cutover is optional and occurs after the data-transfer stage. Microsoft documentation.\nApplicability\nUse this review when planning a Storage Migration Service project. Identify the source types, destination versions, number of servers, and management tools. Verify the complete current support requirements before including a source in the inventory.\nDSE recommendation\nCreate a role map that names the machine responsible for orchestration separately from the data endpoints. Have data owners review the inventory and proposed destinations before approving transfer. Record which servers need an eventual identity handoff and which need only copied data. Keep transfer acceptance and the optional cutover decision as separate milestones.\nVerification\nCompare the discovered inventory with the approved source list and reconcile missing or unexpected data before copying. After an authorized transfer, inspect the recorded results and sample destination files with their owners. Preserve the role map and transfer evidence. Proceed to identity cutover only under its separately reviewed plan for the accepted endpoints.\nOfficial references\nMicrosoft Learn: Storage Migration Service overview. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:30+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/" }, "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-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Assign source, destination, and orchestrator roles for Storage Migration Service" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@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": "Storage Migration Service overview", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview" } } ] } }