Plan a new node type for nonmanaged Service Fabric zone migration

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.

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. Source retrieved September 9, 2026.