{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "slug": "dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration", "url": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/" }, "title": "Plan a new node type for nonmanaged Service Fabric zone migration", "summary": "Can an existing nonmanaged Service Fabric node type be switched to multiple availability zones in place?", "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:22:43+00:00", "modified_at": "2026-09-10T02:14:30+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 239, "potentially_affected": "Nonmanaged Service Fabric clusters adopting a node type that spans multiple availability zones.", "dse_recommendation": "DSE recommends treating this migration as a new-node-type design and service transition, not a property toggle.", "primary_source": { "name": "Migrate an Azure Service Fabric cluster to availability zone support - Azure Service Fabric | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-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": "

Source facts

\n

An existing nonmanaged Service Fabric node type cannot be migrated to support multiple availability zones; the documented path adds a new node type. Its multipleAvailabilityZones property is set only at creation. For a node type already using that property, increasing the durability level also requires a new node type rather than an in-place upgrade. Microsoft Learn.

\n

Applicability

\n

Scope this review to the nonmanaged cluster migration path, not the separate managed-cluster procedure. Identify the current node types, desired zone layout and required durability before preparing a deployment. Use the source’s full prerequisites for the chosen topology; this brief is not a cutover command sequence.

\n

DSE recommendation

\n

DSE recommends treating this migration as a new-node-type design and service transition, not a property toggle. Have the cluster owner select the target durability before creation and plan how services move onto the new capacity. Keep the original node type available until the documented transition and acceptance checks are complete. Separate that plan from decisions about application upgrade-domain ordering.

\n

Verification

\n

In a representative migration rehearsal, inspect the new node type’s declared zone capability and intended durability. Verify that services reach the target placement and remain usable before approving retirement of old capacity. Record both configuration and workload observations. If the proposed plan depends on modifying the existing node type’s zone flag or raising its zonal durability in place, return it for redesign before production execution.

\n

Official references

\n

Microsoft Learn. Source retrieved September 9, 2026.

", "content_text": "Source facts\nAn existing nonmanaged Service Fabric node type cannot be migrated to support multiple availability zones; the documented path adds a new node type. Its multipleAvailabilityZones property is set only at creation. For a node type already using that property, increasing the durability level also requires a new node type rather than an in-place upgrade. Microsoft Learn.\nApplicability\nScope this review to the nonmanaged cluster migration path, not the separate managed-cluster procedure. Identify the current node types, desired zone layout and required durability before preparing a deployment. Use the source’s full prerequisites for the chosen topology; this brief is not a cutover command sequence.\nDSE recommendation\nDSE recommends treating this migration as a new-node-type design and service transition, not a property toggle. Have the cluster owner select the target durability before creation and plan how services move onto the new capacity. Keep the original node type available until the documented transition and acceptance checks are complete. Separate that plan from decisions about application upgrade-domain ordering.\nVerification\nIn a representative migration rehearsal, inspect the new node type’s declared zone capability and intended durability. Verify that services reach the target placement and remain usable before approving retirement of old capacity. Record both configuration and workload observations. If the proposed plan depends on modifying the existing node type’s zone flag or raising its zonal durability in place, return it for redesign before production execution.\nOfficial references\nMicrosoft Learn. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nAn existing nonmanaged Service Fabric node type cannot be migrated to support multiple availability zones; the documented path adds a new node type. Its multipleAvailabilityZones property is set only at creation. For a node type already using that property, increasing the durability level also requires a new node type rather than an in-place upgrade. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones).\n\n## Applicability\n\nScope this review to the nonmanaged cluster migration path, not the separate managed-cluster procedure. Identify the current node types, desired zone layout and required durability before preparing a deployment. Use the source’s full prerequisites for the chosen topology; this brief is not a cutover command sequence.\n\n## DSE recommendation\n\nDSE recommends treating this migration as a new-node-type design and service transition, not a property toggle. Have the cluster owner select the target durability before creation and plan how services move onto the new capacity. Keep the original node type available until the documented transition and acceptance checks are complete. Separate that plan from decisions about application upgrade-domain ordering.\n\n## Verification\n\nIn a representative migration rehearsal, inspect the new node type’s declared zone capability and intended durability. Verify that services reach the target placement and remain usable before approving retirement of old capacity. Record both configuration and workload observations. If the proposed plan depends on modifying the existing node type’s zone flag or raising its zonal durability in place, return it for redesign before production execution.\n\n## Official references\n\n[Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones). 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-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "url": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Plan a new node type for nonmanaged Service Fabric zone migration", "item": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "url": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/", "headline": "Plan a new node type for nonmanaged Service Fabric zone migration", "description": "Can an existing nonmanaged Service Fabric node type be switched to multiple availability zones in place?", "abstract": "Can an existing nonmanaged Service Fabric node type be switched to multiple availability zones in place?", "articleBody": "Source facts\nAn existing nonmanaged Service Fabric node type cannot be migrated to support multiple availability zones; the documented path adds a new node type. Its multipleAvailabilityZones property is set only at creation. For a node type already using that property, increasing the durability level also requires a new node type rather than an in-place upgrade. Microsoft Learn.\nApplicability\nScope this review to the nonmanaged cluster migration path, not the separate managed-cluster procedure. Identify the current node types, desired zone layout and required durability before preparing a deployment. Use the source’s full prerequisites for the chosen topology; this brief is not a cutover command sequence.\nDSE recommendation\nDSE recommends treating this migration as a new-node-type design and service transition, not a property toggle. Have the cluster owner select the target durability before creation and plan how services move onto the new capacity. Keep the original node type available until the documented transition and acceptance checks are complete. Separate that plan from decisions about application upgrade-domain ordering.\nVerification\nIn a representative migration rehearsal, inspect the new node type’s declared zone capability and intended durability. Verify that services reach the target placement and remain usable before approving retirement of old capacity. Record both configuration and workload observations. If the proposed plan depends on modifying the existing node type’s zone flag or raising its zonal durability in place, return it for redesign before production execution.\nOfficial references\nMicrosoft Learn. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:22:43+00:00", "dateModified": "2026-09-10T02:14:30+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/" }, "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-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/#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 a new node type for nonmanaged Service Fabric zone migration" }, "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": "Migrate an Azure Service Fabric cluster to availability zone support - Azure Service Fabric | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones" } } ] } }