SQL Data Sync: Subscription Operation Not Supported During Migration — Request for Assistance

Tajal-8792 0 Reputation points
2026-10-17T14:42:48.9666667+00:00

Problem description

I am experiencing an issue with Azure SQL Data Sync, where operations are blocked with the error 'DataSync_SubscriptionOperationNotSupported.' This occurs even though my subscription was previously active and used Data Sync. I need assistance in restoring Data Sync access to complete my migration.

Environment

Azure SQL Database with SQL Data Sync enabled in the West US 2 region.

What I've already tried

I have identified the affected sync group and confirmed that the subscription is active and the sync agent is online. I removed the on-premises member successfully, but adding it back is blocked by the 'DataSync_SubscriptionOperationNotSupported' error. I also reviewed documentation and confirmed that the sync group was previously operational before the issue occurred.

Current status

I am seeking support to restore Data Sync access for my subscription to allow re-adding the on-premises member and completing my migration process.

Azure SQL Database
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andriy Bilous 12,596 Reputation points MVP
    2026-10-18T05:16:58.2766667+00:00

    Hello Tajal-8792

    This is a subscription eligibility restriction introduced during SQL Data Sync retirement, rather than a problem with your sync agent. SQL Data Sync retires on September 30, 2027. New subscriptions cannot onboard, but existing sync groups should continue operating until retirement.

    To restore access, need Microsoft to add the subscription to an allowlist. Did Azure SQL Data Sync get retired early

    Recommended next steps:

    1. Open an Azure SQL Database support request.
    2. Explain that your subscription already had operational SQL Data Sync groups before the retirement restrictions.
    3. Ask Microsoft to verify your subscription's existing-customer eligibility/allowlist status and restore permission to modify existing sync groups.
    4. Include the subscription ID, sync group resource ID, error message, and UTC timestamp privately.

    If Microsoft cannot restore access, consider Azure Data Factory or transactional replication to finish the migration, depending on your synchronization requirements.

    Official documentation:

    My recommendation: Request an eligibility/allowlist review first, rather than troubleshooting the agent or rebuilding your sync configuration.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.