DATABASES
Existing customers can continue operations, but Microsoft offers no direct replacement strategy
Microsoft has entered the final phase of retiring Azure SQL Data Sync, imposing restrictions on new deployments within subscriptions that have never previously utilized the service.
The limitation began on September 9, preceding the scheduled service termination set for September 30, 2027.
Subscriptions currently employing the service can continue creating, modifying, and managing sync groups and member databases until the retirement deadline. However, new adoption by other subscriptions is now blocked.
The service operates through a hub-and-spoke architecture, featuring an Azure SQL database as the central hub with other databases participating in its synchronization group. Members can include additional Azure SQL databases or on-premises SQL Server databases, the latter requiring a sync agent for connectivity. A predefined conflict resolution policy dictates whether the hub or member database takes precedence when concurrent modifications occur.
SQL Data Sync supports diverse use cases, including hybrid environments where applications and databases span local infrastructure and Azure, as well as geographically distributed systems. Microsoft cited evolving operational, security, and compliance requirements as the rationale for the service retirement, offering minimal technical detail about the decision.
The retirement was first announced two years ago, but the current restriction on first-time deployments provides customers with an impetus to initiate migration planning. Microsoft recommends alternatives such as Azure Data Factory, Azure Functions, read replicas, linked servers, database mirroring, availability groups, and transactional replication. It emphasized that no single replacement fully replicates every SQL Data Sync configuration.
Existing users now have just over a year to transition before the final cutoff. Organizations without a migration plan must develop one prior to the service’s shutdown.