Forum Discussion
Post PartisanMigrate fabric warehouse data
Hi DiKi-I ,
We cannot generate scripts after connecting SSMS , but still we can generate scripts from Fabric Warehouse itself using download sql database project as shown below:
As of now, Fabric Warehouse does not support generating data scripts for data. A recommended approach is to create two Azure service principles, grant them access to the respective workspaces, and use ADF pipelines with Copy Data activities to move data from one tenant to another.
Below is the link for another workaround:
Solved: Re: MS Fabric migration between tenants - Microsoft Fabric Community
If this post helps, then please consider Accepting as solution to help the other members find it more quickly.Thank you.
Community SupportHi DiKi-I ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Wikkleyn_81 BhavinVyas3003 Poojara_D12 for the prompt response.
Microsoft Fabric does not natively support cross-tenant data movement.
If you need to move data from one Microsoft Fabric tenant to another-say from your environment to a client’s-the best way to do it is by using service principals, storage in between, and data pipelines. You’d start by setting up a service principal (an app identity) in your source tenant and give it the right permissions to access your Fabric workspace and the warehouse that holds the data.
Once that's set up, you use Fabric Pipelines or Azure Data Factory to export your warehouse data into a temporary storage location, like Azure Blob Storage or Data Lake, saving it in a standard format like CSV or Parquet.
Now, since you can’t directly connect two Fabric tenants, the next step is to move the exported files into the client’s tenant. You can use tools like AzCopy, Azure Storage Explorer, or ADF again to do this. Depending on the security setup, you might share access using SAS tokens or configure cross-tenant sharing using Azure B2B features if the client allows it.
After the files are in the client’s environment, you’ll repeat a similar setup on their side: create another service principal, give it access to their Fabric workspace and warehouse, and finally use another pipeline (or a SQL COPY INTO command) to bring the data into their Fabric Warehouse.
This approach gives you a secure, repeatable way to handle cross-tenant data transfers without needing any unsupported workarounds.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you.