Still Using SQL Data Sync? Microsoft Says It Is Time to Move

Microsoft has started the final phase of retiring SQL Data Sync for Azure SQL Database, bringing the service closer to its permanent shutdown on September 30, 2027.

SQL Data Sync allows organizations to synchronize selected data bidirectionally between databases running on-premises and in Azure. Microsoft first announced plans to retire the technology in 2024.

New customers can no longer use SQL Data Sync

Microsoft has now stopped customers who have never used SQL Data Sync from creating new deployments.

Organizations that already use the service can continue operating their existing sync groups until September 30, 2027.

Microsoft says the restriction will help move customers toward newer data synchronization and replication technologies before the service disappears completely.

Existing customers should start migrating

Microsoft is urging current SQL Data Sync users to identify their existing sync groups and begin planning migrations as soon as possible.

Some deployments may require significant re-architecting depending on the amount of synchronized data, database topology, and synchronization requirements.

Waiting until closer to the retirement date could leave organizations with limited time to redesign complex environments.

Microsoft recommends several alternatives

Microsoft recommends different replacement technologies depending on the workload.

Azure Data Factory can handle scheduled, incremental, and orchestrated data movement, while transactional replication supports one-way distribution from SQL Server to Azure SQL Database.

Always On availability groups and Managed Instance link can support reporting replicas. Active geo-replication and read replicas provide options for regional availability and read-scale workloads.

Microsoft also points to Azure SQL triggers for Azure Functions for application-specific synchronization and Microsoft Fabric mirroring for continuous replication in analytics scenarios.

SQL Data Sync will stop working on September 30, 2027, regardless of whether customers have completed their migrations.

The retirement comes as Microsoft customers also deal with other SQL Server-related issues. Recent Windows Server 2025 memory changes have been causing SQL Server and application crashes.

Meanwhile, Windows Server 2016 systems can experience CompatTelRunner crashes after an August update, although Microsoft says the crashes do not affect system functionality.