Choose a File Sync share-migration branch from the actual cloud-tiering state

Source facts

Microsoft separates File Sync share migration into procedures for cloud tiering being off or on. With tiering on, the guide copies data inside Azure to avoid unnecessary recalls through the source and says cutover requires downtime. For the tiering-enabled procedure, a cross-region move requires a new File Sync server connected to the target share because the registered server belongs to one Storage Sync Service and that service must share the share’s region. Microsoft Learn

Applicability

This review applies to a planned migration between SMB Azure file shares that already participate in Azure File Sync, including moves between regions.

DSE recommendation

DSE recommends recording the observed tiering state, source region, target region, and registered-server relationships before choosing the migration procedure. Ask the workload owner to approve the cutover window and identify who controls source writes. Build the plan from the branch that matches those observations, with explicit source, staging, and target roles. For the tiering-enabled cross-region branch, include the replacement server before copying data.

Verification

Recheck tiering state and regional relationships before the migration window. Compare the selected procedure with the recorded topology, and validate representative destination files and synchronization health during the approved test. Keep data-copy progress separate from cutover completion and document any unresolved server-registration or target-share issue.

Official references

• Microsoft: Migrate files between file shares when using Azure File Sync | Microsoft Learn