At a glance
| Status | Retiring 30 September 2027; no new sync groups for subscriptions that never used it |
| Sources | Azure SQL Database hub; Azure SQL Database or SQL Server members (no Managed Instance or Synapse) |
| Targets | Same as sources: the hub and member databases in a sync group |
| CDC mechanism | Trigger-based change tracking into side tables in the user database |
| Initial load | Adding tables to a sync group copies the data; schema must be created first or provisioned by the service |
| Schema evolution | Schema changes are not replicated automatically |
| Latency | Scheduled sync interval; Microsoft documents eventual, not transactional, consistency |
| Conflict handling | Hub wins or Member wins, set per sync group |
| Monitoring | Sync status and logs in the Azure portal; sync metadata database holds logs |
| Licensing | No charge for the service; you pay for the Azure SQL databases and data transfer |
Do not start a new project on SQL Data Sync. Microsoft retires it on 30 September 2027 and has already blocked new sync groups in subscriptions that never used it. If you run it today, plan a migration now: Microsoft's retirement guide maps each scenario to Azure Data Factory, transactional replication, read replicas, geo-replication, the Managed Instance link or Fabric mirroring.
Overview
SQL Data Sync is a service built on Azure SQL Database that keeps selected tables synchronised across several databases. A sync group has one hub, which must be an Azure SQL Database, and up to 30 endpoints in total, of which up to 5 can be on-premises SQL Server databases connected through a local sync agent. Sync runs only between the hub and each member, in one direction or both, on a schedule you set, and conflicts are resolved by a group-wide Hub wins or Member wins policy. It does not support Azure SQL Managed Instance or Azure Synapse Analytics.
Changes are tracked with insert, update and delete triggers that write to side tables in the user database, so Microsoft documents eventual consistency rather than transactional consistency, and a performance cost on busy databases. Every table needs a primary key, schema changes are not replicated, TRUNCATE is not tracked, only SQL authentication is supported (no Microsoft Entra ID), and Microsoft states it is not a disaster recovery tool. The service retires on 30 September 2027.
Key features
- Hub and spoke sync groups with an Azure SQL Database hub and Azure SQL Database or SQL Server members
- Bidirectional or one-way sync (hub to member, member to hub) on a configurable interval
- Group-level conflict policy: Hub wins or Member wins
- Local sync agent for on-premises SQL Server members
- Private link option using a service-managed private endpoint for Azure-hosted hub and members
- Setup through the Azure portal, PowerShell or the REST API
Integrations and ecosystem
Pros and cons
Pros
- Bidirectional sync between SQL Server and Azure SQL Database without extra software beyond the sync agent
- No separate service charge
- Simple conflict policy and portal-based configuration
Cons
- Retiring on 30 September 2027, and closed to subscriptions that never used it
- Trigger-based tracking adds load and gives no transactional consistency
- SQL authentication only; no Microsoft Entra ID or network security perimeter support
- Limits such as 30 endpoints, 500 tables per group and mandatory primary keys; schema changes are not synced
Pricing
Microsoft's FAQ says there is no charge for the SQL Data Sync service itself, but it only works with a paid Azure SQL Database as the hub, a customer-owned Azure SQL Database as the sync metadata database, and data transfer charges for data moving in and out. Treat it as part of your Azure SQL Database bill. Because the service is retiring, it should not be budgeted as a new purchase.
Pricing checked on the vendor's official page on 7 November 2026. Prices change; confirm before buying.
Who it is best for
Existing users who need to understand what their current sync groups do while they plan a migration before 30 September 2027.
Typical use cases
- Hybrid applications that keep on-premises SQL Server tables in step with Azure SQL Database (existing deployments only)
- Offloading reporting to a second Azure SQL database kept in sync
- Keeping regional copies of reference data in globally distributed applications
- Planning a migration of existing sync groups to Azure Data Factory, replication or Fabric mirroring before retirement
Who should look elsewhere
- Any new synchronisation or CDC project: see Microsoft's alternatives, or compare Azure Data Factory, Debezium or SymmetricDS.
- Disaster recovery or read scale-out, which Microsoft says it is not designed for.
Verdict
SQL Data Sync filled a real gap for two-way sync between SQL Server and Azure SQL Database, but it is now a retiring feature with a fixed end date and no new onboarding. Treat this profile as migration guidance: map each sync group to one of Microsoft's documented alternatives, or to a third-party bidirectional tool if you still need active-active writes.
Frequently asked questions
Is Azure SQL Data Sync being retired?
Yes. Microsoft Learn states that SQL Data Sync retires on 30 September 2027. New sync groups cannot be created in subscriptions that did not previously use it, and existing groups should be migrated before that date.
What should I use instead of SQL Data Sync?
Microsoft's retirement guide lists Azure Data Factory, Azure Functions, transactional replication, linked servers, Always On availability groups and the Managed Instance link, read replicas, active geo-replication, database copy and Fabric mirrored databases, depending on source, destination and scenario. None is a like-for-like bidirectional replacement in every case.
How much does SQL Data Sync cost?
Microsoft says there is no charge for the service itself. You pay for the Azure SQL databases involved, including the sync metadata database, and for data transfer in and out.
Does SQL Data Sync work with Azure SQL Managed Instance?
No. Microsoft documents that SQL Data Sync does not support Azure SQL Managed Instance or Azure Synapse Analytics.
Sources
- Microsoft Learn: What is SQL Data Sync for Azure?
- Microsoft Learn: SQL Data Sync retirement migration
- Microsoft Learn: Data Sync Agent for SQL Data Sync
- Microsoft Learn: Best practices for SQL Data Sync
- Azure bandwidth (data transfer) pricing
Checked November 2026.
Listed in: Change Data Capture & Replication.
How we research reviews and what star ratings mean: our editorial method.