Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
Srisakthi
Resolver II
Resolver II

Workspace movement across Tenant

Hi All,

 

Is there anyway to move Fabric Workspace and its item from One tenant to another tenant?

1 ACCEPTED SOLUTION
v-jingzhan-msft
Community Support
Community Support

Hi @Srisakthi 

 

Resources between tenants are usually  isolated from each other. Users cannot move a workspace from one tenant to another tenant on their own. If the two tenants are in different data regions, it becomes even more complicated. For example, non Power BI Fabric items can't move between regions. 

 

If you want to move it directly, you might need to open a support ticket with Microsoft to see if it's possible to do so from the backend.

 

Another approach is to export the artifacts you want to move from the current workspace and then import them into a new workspace in the other tenant. This might require you to rebuild some artifacts, as not all artifacts can be directly exported or downloaded.

 

A third alternative is to use Git integration. Steps are:

  1. Connect an empty repository to the source workspace.
  2. Commit existing artifacts to the repository.
  3. Clone the repository or disconnect it from the source workspace.
  4. Connect the repository to the (empty) target workspace in the other tenant.
  5. Sync the artifacts from the repository to the target workspace.
  6. Disconnect the repository from the target workspace.

However some of the items for Git integration are in preview and some items are not supported currently. And there are some known limitations of this feature. To learn more, please read the following document:

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Get started with Git integration - Microsoft Fabric | Microsoft Learn

Git integration process - Microsoft Fabric | Microsoft Learn

 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

View solution in original post

4 REPLIES 4
Srisakthi
Resolver II
Resolver II

Hi @v-jingzhan-msft ,

 

For notebooks these are the steps which is followed with few customization to deploy on another tenant using script.

1. Download the notebooks and upload to new tenant unders lakehouse files section.

2. Then use the scripts available in semantic link labs to push deploy those notebooks with lakehouse attached to it.

3. Majorily customized and used this function 

import_notebook with required dynamic parameters

Reference link - https://github.com/microsoft/semantic-link-labs/blob/main/src/sempy_labs/_notebooks.py

 

 

Similarly for semantic model, data pipeline we can do.

Regards,

Srisakthi

Srisakthi
Resolver II
Resolver II

Hi @v-jingzhan-msft ,

 

Thanks for the detailed explaination. I have also explored another option i.e, using semantic link labs we can move certain Fabric items to another tenant but with few modifications to the script.

 

Regards,

Srisakthi

Hi @Srisakthi 

 

That's cool! I've never used that! Could you please share some reference documents or links to help us understand it better? This would be very helpful! Thank you. 

 

Best Regards,
Jing

v-jingzhan-msft
Community Support
Community Support

Hi @Srisakthi 

 

Resources between tenants are usually  isolated from each other. Users cannot move a workspace from one tenant to another tenant on their own. If the two tenants are in different data regions, it becomes even more complicated. For example, non Power BI Fabric items can't move between regions. 

 

If you want to move it directly, you might need to open a support ticket with Microsoft to see if it's possible to do so from the backend.

 

Another approach is to export the artifacts you want to move from the current workspace and then import them into a new workspace in the other tenant. This might require you to rebuild some artifacts, as not all artifacts can be directly exported or downloaded.

 

A third alternative is to use Git integration. Steps are:

  1. Connect an empty repository to the source workspace.
  2. Commit existing artifacts to the repository.
  3. Clone the repository or disconnect it from the source workspace.
  4. Connect the repository to the (empty) target workspace in the other tenant.
  5. Sync the artifacts from the repository to the target workspace.
  6. Disconnect the repository from the target workspace.

However some of the items for Git integration are in preview and some items are not supported currently. And there are some known limitations of this feature. To learn more, please read the following document:

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Get started with Git integration - Microsoft Fabric | Microsoft Learn

Git integration process - Microsoft Fabric | Microsoft Learn

 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.