# Plan a new node type for nonmanaged Service Fabric zone migration

> Can an existing nonmanaged Service Fabric node type be switched to multiple availability zones in place?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:43+00:00
- Modified: 2026-09-10T02:14:30+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Can an existing nonmanaged Service Fabric node type be switched to multiple availability zones in place?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones). Source retrieved September 9, 2026.

## Primary reference

- Name: Migrate an Azure Service Fabric cluster to availability zone support - Azure Service Fabric | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/service-fabric/migrate-service-fabric-availability-zones
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Plan a new node type for nonmanaged Service Fabric zone migration,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-553-plan-a-new-node-type-for-nonmanaged-service-fabric-zone-migration/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.