{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
        "slug": "dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/"
        },
        "title": "Plan workload movement separately from scale-set zone expansion",
        "summary": "Does adding zones to an existing scale set move its current instances and their data into those zones?",
        "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-10T00:26:58+00:00",
        "modified_at": "2026-09-10T01:23:49+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 239,
        "potentially_affected": "Owners expanding an eligible Azure scale set into additional availability zones.",
        "dse_recommendation": "Create a workload-transition plan in addition to the scale set's zone-property change.",
        "primary_source": {
            "name": "Customer-selected availability zones for Virtual Machine Scale Sets - Azure Virtual Machine Scale Sets | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones",
            "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>Adding zones to a scale set does not migrate its original instances or data. New instances created during scale-out use the expanded zone selection, and subsequent scale-in removes regional instances first. Added zones cannot later be removed or replaced. Expansion requires API 2023-03-01 or later and fault-domain count 1 or 5; capacity reservations during expansion, Dedicated Host deployments, Service Fabric RP, and AKS scale sets are excluded. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Review the source&#8217;s full eligibility and zone-availability checks before planning this transition. Identify which existing instances hold state and how the application will transfer or replicate it to new instances.</p>\n<h2>DSE recommendation</h2>\n<p>Create a workload-transition plan in addition to the scale set&#8217;s zone-property change. Have the workload owner define when a new zonal instance is ready to serve and when an original instance can be retired. Coordinate capacity increases, data movement, and removals explicitly. Do not describe the property update as an in-place migration or promise to reverse it by removing a zone.</p>\n<h2>Verification</h2>\n<p>Inspect instance locations before and after an authorized staged expansion. Verify that intended new instances are serving the correct data before approving scale-in, and check which original instances remain. Preserve the instance-to-zone inventory with application results. If the control-plane update succeeds but the workload has not moved, report the transition as incomplete and leave the original service path protected.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Customer-selected availability zones for Virtual Machine Scale Sets</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nAdding zones to a scale set does not migrate its original instances or data. New instances created during scale-out use the expanded zone selection, and subsequent scale-in removes regional instances first. Added zones cannot later be removed or replaced. Expansion requires API 2023-03-01 or later and fault-domain count 1 or 5; capacity reservations during expansion, Dedicated Host deployments, Service Fabric RP, and AKS scale sets are excluded. Microsoft Learn.\nApplicability\nReview the source’s full eligibility and zone-availability checks before planning this transition. Identify which existing instances hold state and how the application will transfer or replicate it to new instances.\nDSE recommendation\nCreate a workload-transition plan in addition to the scale set’s zone-property change. Have the workload owner define when a new zonal instance is ready to serve and when an original instance can be retired. Coordinate capacity increases, data movement, and removals explicitly. Do not describe the property update as an in-place migration or promise to reverse it by removing a zone.\nVerification\nInspect instance locations before and after an authorized staged expansion. Verify that intended new instances are serving the correct data before approving scale-in, and check which original instances remain. Preserve the instance-to-zone inventory with application results. If the control-plane update succeeds but the workload has not moved, report the transition as incomplete and leave the original service path protected.\nOfficial references\nMicrosoft Learn: Customer-selected availability zones for Virtual Machine Scale Sets. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nAdding zones to a scale set does not migrate its original instances or data. New instances created during scale-out use the expanded zone selection, and subsequent scale-in removes regional instances first. Added zones cannot later be removed or replaced. Expansion requires API 2023-03-01 or later and fault-domain count 1 or 5; capacity reservations during expansion, Dedicated Host deployments, Service Fabric RP, and AKS scale sets are excluded. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones).\n\n## Applicability\n\nReview the source’s full eligibility and zone-availability checks before planning this transition. Identify which existing instances hold state and how the application will transfer or replicate it to new instances.\n\n## DSE recommendation\n\nCreate a workload-transition plan in addition to the scale set’s zone-property change. Have the workload owner define when a new zonal instance is ready to serve and when an original instance can be retired. Coordinate capacity increases, data movement, and removals explicitly. Do not describe the property update as an in-place migration or promise to reverse it by removing a zone.\n\n## Verification\n\nInspect instance locations before and after an authorized staged expansion. Verify that intended new instances are serving the correct data before approving scale-in, and check which original instances remain. Preserve the instance-to-zone inventory with application results. If the control-plane update succeeds but the workload has not moved, report the transition as incomplete and leave the original service path protected.\n\n## Official references\n\n[Microsoft Learn: Customer-selected availability zones for Virtual Machine Scale Sets](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones). Source reviewed 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-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Plan workload movement separately from scale-set zone expansion",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/",
                "headline": "Plan workload movement separately from scale-set zone expansion",
                "description": "Does adding zones to an existing scale set move its current instances and their data into those zones?",
                "abstract": "Does adding zones to an existing scale set move its current instances and their data into those zones?",
                "articleBody": "Source facts\nAdding zones to a scale set does not migrate its original instances or data. New instances created during scale-out use the expanded zone selection, and subsequent scale-in removes regional instances first. Added zones cannot later be removed or replaced. Expansion requires API 2023-03-01 or later and fault-domain count 1 or 5; capacity reservations during expansion, Dedicated Host deployments, Service Fabric RP, and AKS scale sets are excluded. Microsoft Learn.\nApplicability\nReview the source’s full eligibility and zone-availability checks before planning this transition. Identify which existing instances hold state and how the application will transfer or replicate it to new instances.\nDSE recommendation\nCreate a workload-transition plan in addition to the scale set’s zone-property change. Have the workload owner define when a new zonal instance is ready to serve and when an original instance can be retired. Coordinate capacity increases, data movement, and removals explicitly. Do not describe the property update as an in-place migration or promise to reverse it by removing a zone.\nVerification\nInspect instance locations before and after an authorized staged expansion. Verify that intended new instances are serving the correct data before approving scale-in, and check which original instances remain. Preserve the instance-to-zone inventory with application results. If the control-plane update succeeds but the workload has not moved, report the transition as incomplete and leave the original service path protected.\nOfficial references\nMicrosoft Learn: Customer-selected availability zones for Virtual Machine Scale Sets. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:26:58+00:00",
                "dateModified": "2026-09-10T01:23:49+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-298-plan-workload-movement-separately-from-scale-set-zone-expansion/"
                },
                "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-298-plan-workload-movement-separately-from-scale-set-zone-expansion/#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": "Plan workload movement separately from scale-set zone expansion"
                },
                "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": 239,
                "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": "Customer-selected availability zones for Virtual Machine Scale Sets - Azure Virtual Machine Scale Sets | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-customer-selected-zones"
                }
            }
        ]
    }
}