Sync Azure SQL Database across Tenants

Hi @**Richard Clark
**
Thank you for contacting to Microsoft QA.

It sounds like you’re looking to set up sync for Azure SQL Database across different tenants while ensuring that the customer only has access to the necessary tables. Here’s what you need to know:

Cross-Tenant Sync: While Azure SQL Database supports multitenancy features, direct synchronization across different Azure SQL Database tenants isn’t natively provided through sync features. However, you can manage this by potentially exporting data to a .bacpac file, then importing it into the customer’s tenant. You can refer to the Troubleshoot Cross-Tenant Migration documentation that details the process of moving databases across tenants.

Data Isolation: Since you don’t want to give the customer access to your database, you may consider using Elastic Database tools or Row-Level Security, which help enforce tenant-level isolation and can limit access to specific rows of data based on tenant ID. More information about this is available here.

Cost Estimation: Regarding costs, you are correct that syncing or transferring data will have I/O impacts on your SQL server and may incur data transfer costs. To estimate these accurately:

• Check the Azure pricing calculator to estimate costs related to your database operations.
  • Keep an eye on the database size and the performance tier it’s allocated, as both will influence costs. More on estimating costs can be referenced here: Azure Pricing Calculator.

  Performance Impact: Sync operations may impact performance, including I/O scenarios. It would be wise to consider performing these operations during off-peak hours or using strategies like database Geo-replication for reducing performance impacts.

If you need to explore this further or discuss specific scenarios, a Teams talk sounds like a good plan.

Here are some links to relevant documentation for your reference: