I'm unable to delete the DataSync table

Question

I'm unable to delete the DataSync table

Jean Rodriguez 0

I have been unable to delete the DataSync table, the sync metadata database, which we are not using anymore as we moved away from DataSync groups. The data sync group was deleted, and then I've applied all cleanup scripts so we don't have any of the data sync schemas, users, etc. But I'm still getting the "Database xxxxxx' cannot be deleted because it is used as a sync metadata database which still contains sync groups and/or sync agents. (Code: CannotMoveOrDropSyncMetadataDatabase)" error everytime I tried deleting the db.

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-05T20:03:48.58+00:00

Hi @Jean Rodriguez
Thankyou for reaching microsoft Q&A!
Could you please share requested details in private message.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-15T18:47:16.16+00:00

Hi @Jean Rodriguez
Apology for delay!
The error indicates that Azure SQL still considers this database to be registered as a SQL Data Sync metadata database. Removing the Data Sync schemas, users, and tables from the database does not remove the Data Sync service-side association.

Please first verify in the Azure portal that there are no remaining Data Sync sync groups or sync agents associated with the subscription/region, including any stale configuration. Microsoft documents that the Sync Metadata Database cannot be deleted while sync groups or sync agents still exist.

If the sync group has already been deleted and there are no remaining sync agents or groups, but the database continues to return CannotMoveOrDropSyncMetadataDatabase, this is likely a stale Data Sync metadata registration rather than an issue with the database contents. The error is enforced by the Azure SQL management plane and is also returned by the database delete API.

In that situation, avoid manually deleting or modifying additional Data Sync system objects. The recommended next step is to open an Azure support request with the SQL Data Sync/Azure SQL team and provide the subscription ID, logical server, database name, region, and confirmation that the sync group and agents have already been removed. The service team can verify and clear the remaining Data Sync association if one is still present.

As a validation step, retry the database deletion after confirming that all Data Sync resources have been removed. If the same error persists, the issue is not caused by ordinary database objects or permissions.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-18T20:33:54.7433333+00:00

Hi Jean,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Jean Rodriguez 0 Reputation points

2026-08-19T18:07:10.5933333+00:00

@Pilladi Padma Sai Manisha

Hi:

I already replied with private message but will comment here as well in case you didn't see that. I've already verified all data sync resources have been removed, no data sync groups or agents remain. And yes, still getting the error. I tried opening the support request using the link you sent me, but I'm stuck at step 3 (check the private message) as I don't see any button to advance to step 4, where the request is actually created. Please advice.

1 answer

Your answer

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-05T20:03:48.58+00:00

Hi @Jean Rodriguez
Thankyou for reaching microsoft Q&A!
Could you please share requested details in private message.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-15T18:47:16.16+00:00

Hi @Jean Rodriguez
Apology for delay!
The error indicates that Azure SQL still considers this database to be registered as a SQL Data Sync metadata database. Removing the Data Sync schemas, users, and tables from the database does not remove the Data Sync service-side association.

Please first verify in the Azure portal that there are no remaining Data Sync sync groups or sync agents associated with the subscription/region, including any stale configuration. Microsoft documents that the Sync Metadata Database cannot be deleted while sync groups or sync agents still exist.

If the sync group has already been deleted and there are no remaining sync agents or groups, but the database continues to return CannotMoveOrDropSyncMetadataDatabase, this is likely a stale Data Sync metadata registration rather than an issue with the database contents. The error is enforced by the Azure SQL management plane and is also returned by the database delete API.

In that situation, avoid manually deleting or modifying additional Data Sync system objects. The recommended next step is to open an Azure support request with the SQL Data Sync/Azure SQL team and provide the subscription ID, logical server, database name, region, and confirmation that the sync group and agents have already been removed. The service team can verify and clear the remaining Data Sync association if one is still present.

As a validation step, retry the database deletion after confirming that all Data Sync resources have been removed. If the same error persists, the issue is not caused by ordinary database objects or permissions.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-08-18T20:33:54.7433333+00:00

Hi Jean,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Jean Rodriguez 0 Reputation points

2026-08-19T18:07:10.5933333+00:00

@Pilladi Padma Sai Manisha

Hi:

I already replied with private message but will comment here as well in case you didn't see that. I've already verified all data sync resources have been removed, no data sync groups or agents remain. And yes, still getting the error. I tried opening the support request using the link you sent me, but I'm stuck at step 3 (check the private message) as I don't see any button to advance to step 4, where the request is actually created. Please advice.

Answer 1

Hi Jean,

If the database still returns CannotMoveOrDropSyncMetadataDatabase, then Azure SQL still has that database registered in the SQL Data Sync service metadata, even if the Data Sync schemas/tables/users were already removed from inside the database.

The important point is that deleting dss / TaskHosting objects from the database does not necessarily remove the Azure Data Sync resource registration. The sync groups, members, or agents must be removed from the Azure side.

Please check these items:

Go to the database in Azure portal and check: SQL database > Data Sync > Sync Groups / Sync Agents If the portal blade is empty or stuck, try checking with PowerShell or REST API for any remaining sync groups/agents. If you find any sync groups, delete them first and wait for deletion to fully complete. If there are on-premises sync agents, make sure they are removed/unregistered as well. If an agent is offline, bring it online if possible and then remove the sync group/agent cleanly. Do not manually drop more Data Sync objects in the database at this point. The issue is likely the service-side registration, not remaining user tables.

If nothing is visible in the portal/PowerShell but the database still cannot be deleted, this is likely an orphaned SQL Data Sync metadata registration. In that case, Microsoft Support needs to clear/reset the backend Data Sync registration for the database.

Please open a support request and include:

Subscription ID

SQL server name

Database name

Region

Error code: CannotMoveOrDropSyncMetadataDatabase

Confirmation that the sync group was deleted

Any sync group/agent names, if known

Approximate time when Data Sync was removed

Docs:

SQL Data Sync troubleshooting: https://learn.microsoft.com/en-us/azure/azure-sql/database/sql-data-sync-troubleshoot

Sync Groups delete REST API: https://learn.microsoft.com/en-us/rest/api/sql/sync-groups/delete

Sync Agents delete REST API: https://learn.microsoft.com/en-us/rest/api/sql/sync-agents/delete

In short, this is usually not fixed by database cleanup scripts alone. If Azure still thinks the database is a sync metadata database, the remaining sync registration has to be removed from the SQL Data Sync service metadata, and Microsoft Support may need to do that if the objects are orphaned.