Choose a durable File Sync group name before connecting endpoints

Source facts

Microsoft states that a File Sync group cannot be renamed because its name forms part of the URL used to manage child endpoints. The documented equivalent of renaming is to deprovision the group and create another with the desired name. The topology guide requires all server endpoints to be removed before the sync group or Storage Sync Service is deprovisioned. Microsoft Learn

Applicability

Use this planning review before naming an Azure File Sync group or when an existing group’s name is being reconsidered for organizational reasons.

DSE recommendation

DSE recommends reviewing the name with the operational owner before any endpoints are attached. Prefer a name that remains meaningful across routine team or ownership changes. If an existing name must change, assess the request as a topology replacement project with data-state checks, endpoint inventory, recovery arrangements, and an approved window. Do not treat a naming preference as authorization to remove synchronization resources or to bypass the documented deprovisioning procedure.

Verification

For a new group, compare its name and resource identifier with the approved convention before adding endpoints. For a replacement, verify the complete planned topology and source-data readiness before executing the authorized procedure. Afterward, inspect endpoint relationships and synchronization health, recording any unresolved data or configuration issue before completing the handoff.

Official references

• Microsoft: Modify Azure File Sync Topology | Microsoft Learn