An Azure relational database service.
First, please accept my sincere apologies for the delay in responding and thank you for your patience.
Based on the information shared, it appears that the issue is not related to the current number of visible sync members in the Sync Group. Although only one on-premises sync member is currently listed, the service is still reporting that the maximum number of on-premises databases has been reached for a Basic Sync Group.
Since the previous on-premises server crashed and several sync members were removed and recreated, it is possible that stale synchronization metadata remains associated with the Sync Group configuration.
As a troubleshooting step, please ensure that:
- All old databases are unregistered from the Data Sync Agent.
- Unused sync members are removed from the Sync Group.
- The Data Sync Agent service has been restarted after the cleanup.
- A new Sync Group is created and tested with the on-premises databases.
If the issue continues even with a newly created Sync Group, further investigation please let us know to review the Sync Group configuration and associated metadata.
Please let us know the outcome after testing with a new Sync Group, and we'll be happy to assist further.