Microsoft Blocks New Azure SQL Data Sync Deployments Ahead of September 2027 Retirement
Microsoft has stopped subscriptions that never used Azure SQL Data Sync from creating new sync groups, entering the final phase before the service's September 30, 2027 shutdown.
Overview
Microsoft has entered the final phase of retiring Azure SQL Data Sync, blocking new deployments in subscriptions that have never used the service, according to The Register. The restriction took effect on September 9, ahead of the service’s shutdown on September 30, 2027, as The Register reported, a date Microsoft’s own documentation confirms: SQL Data Sync retires on September 30, 2027.
What We Know
Subscriptions that already use SQL Data Sync can continue creating, modifying, and managing sync groups and member databases until retirement, while other subscriptions can no longer adopt it, according to The Register. Microsoft’s documentation puts it the same way: “As part of the retirement process, you can’t create new sync groups in Azure subscriptions that didn’t previously use SQL Data Sync. Existing sync groups can continue operating until the retirement date,” according to Microsoft’s Azure SQL documentation.
The service uses a hub-and-spoke model, with an Azure SQL database serving as the hub and other databases joining its synchronization group, as The Register described. Members can be other Azure SQL databases or on-premises SQL Server databases, which require a sync agent, and a conflict resolution policy determines whether the hub or member database takes precedence when changes clash. Microsoft’s own documentation confirms the same architecture, describing a “hub and spoke topology” in which sync occurs only between the hub and individual members, with a group-level policy that can be set to “Hub wins” or “Member wins” for conflict resolution.
SQL Data Sync supports scenarios including hybrid environments, in which applications and databases are split between local infrastructure and Azure, as well as geographically distributed applications, The Register noted. Microsoft’s migration guide similarly lists three main scenarios for the service: hybrid data synchronization, distributed applications, and globally distributed applications, according to Microsoft’s retirement migration guide.
Microsoft offered little technical explanation for the retirement, referring only to evolving “operational, security, and compliance requirements,” The Register reported. The company acknowledged that customers will need to choose among several possible replacements, listing alternatives including Azure Data Factory, Azure Functions, read replicas, linked servers, database mirroring, availability groups, and transactional replication, but noted that “there is no single replacement that maps to every SQL Data Sync configuration,” according to The Register. Microsoft’s own migration guide lists the same set of alternatives, organized by use case, including Azure Data Factory, Azure Functions, read replicas, linked server, mirroring, Always On availability groups, and transactional replication.
Microsoft announced the retirement roughly two years before this September restriction, The Register noted, and existing users have just over a year left to migrate before the final cutoff.
What We Don’t Know
Microsoft has not detailed the specific operational, security, or compliance issues that led to the retirement decision, beyond the general reference reported by The Register. The company also has not published usage figures indicating how many subscriptions or sync groups remain active on the service ahead of the 2027 shutdown.
Analysis
The move follows a familiar pattern for Azure services nearing end of life: a lengthy runway between the initial retirement announcement and a hard deployment freeze, followed by a further grace period for existing users before final shutdown. By blocking new sign-ups more than a year ahead of the September 30, 2027 cutoff while leaving existing sync groups untouched, Microsoft is pushing customers who have not yet adopted SQL Data Sync toward alternatives such as Azure Data Factory or transactional replication from the outset, while giving current users a defined but lengthening window to plan a migration path that Microsoft itself says has no single drop-in replacement.