Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have to migrate the data from fabric warehouse to another fabric warehouse in different tenant. How I can easily migrate the data?
I don't see the script generate option after connecting the warehouse to ssms.
Solved! Go to Solution.
Hi @DiKi-I
Welcome to the Microsoft Fabric Community Forum.
Microsoft Fabric does not natively support direct cross-tenant data migration for warehouses. Additionally, it does not support traditional SQL Server Management Studio (SSMS) script generation features like “Generate Scripts” or “Tasks- Export Data,” as Fabric warehouses are not full SQL Server instances and lack full SQL Server Management Objects (SMO) compatibility. Since you are migrating data across tenants, cross-tenant queries or direct data transfer via T-SQL or Linked Servers is not possible.
To perform the migration, export the data from the source Fabric Warehouse using supported methods such as Fabric Pipelines, Azure Data Factory, or Notebooks, and write the data into an intermediate storage location like Azure Blob Storage or OneLake in a portable format such as CSV or Parquet. Ensure that a service principal is configured in the source tenant to enable secure access to the storage location. Once the data is exported, transfer it to the target tenant using tools like AzCopy or Azure Storage Explorer.
If needed, configure secure cross-tenant access using Azure B2B collaboration or Shared Access Signature (SAS) tokens. In the destination tenant, configure a service principal with appropriate permissions, and then use T-SQL commands like COPY INTO, or Fabric Pipelines or Notebooks, to load the data into the target Fabric Warehouse. This method ensures secure, scalable, and Microsoft-supported migration across tenants.
Thank you for being part of Fabric Community Forum.
Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.
Hi @DiKi-I
We are following up once again regarding your query. Could you please confirm if the issue has been resolved? If so, kindly mark the helpful response and accept it as the solution to assist other community members in resolving similar issues more efficiently. If not, please provide detailed information so we can better assist you.
Thank you for your understanding and participation.
Hi @DiKi-I
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @DiKi-I
We are following up to see if you have had the chance to review the information provided. If you have any further questions, please do not hesitate to contact us. Could you confirm whether your query has been resolved? If so, kindly mark the helpful response and accept it as the solution to assist other community members in resolving similar issues more efficiently. If not, please provide detailed information so we can better assist you.
Thank You.
Hi @DiKi-I
Welcome to the Microsoft Fabric Community Forum.
Microsoft Fabric does not natively support direct cross-tenant data migration for warehouses. Additionally, it does not support traditional SQL Server Management Studio (SSMS) script generation features like “Generate Scripts” or “Tasks- Export Data,” as Fabric warehouses are not full SQL Server instances and lack full SQL Server Management Objects (SMO) compatibility. Since you are migrating data across tenants, cross-tenant queries or direct data transfer via T-SQL or Linked Servers is not possible.
To perform the migration, export the data from the source Fabric Warehouse using supported methods such as Fabric Pipelines, Azure Data Factory, or Notebooks, and write the data into an intermediate storage location like Azure Blob Storage or OneLake in a portable format such as CSV or Parquet. Ensure that a service principal is configured in the source tenant to enable secure access to the storage location. Once the data is exported, transfer it to the target tenant using tools like AzCopy or Azure Storage Explorer.
If needed, configure secure cross-tenant access using Azure B2B collaboration or Shared Access Signature (SAS) tokens. In the destination tenant, configure a service principal with appropriate permissions, and then use T-SQL commands like COPY INTO, or Fabric Pipelines or Notebooks, to load the data into the target Fabric Warehouse. This method ensures secure, scalable, and Microsoft-supported migration across tenants.
Thank you for being part of Fabric Community Forum.
Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.
The most easy way to sync the data from 1 fabric warehouse to another would be to create a simple data pipeline with copy activity to copy from 1 warehouse to another.
Based on my understanding, generate scripts via SSMS is not available as of today
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 |