How to migrate Microsoft Fabric to another Azure Tenant/Subscription? Luis Rodrigues

[luisr-optimus]

Hello.

Would it be possible to migrate Microsoft Fabric accounts and capacities to another Azure Tenant/Subscription? What are the steps and risks of this migration?

Thanks!

[KevinChant]

Hi, out of curiosity why do you want to move a capacity to another tenant? Would it not be easier to recreate new capacities in the other tenant instead and link them to new workspaces?

[burakkaragoz]

Hi @luisr-optimus ,

Right now, there’s no built-in or automated way to migrate Microsoft Fabric resources (like capacities, workspaces, Lakehouses, etc.) across Azure tenants or subscriptions. But here’s a general approach that might help:

 What you can do:

• Set up Fabric in the new tenant (make sure the right SKUs are provisioned).
• Export your assets:
  • Use Power BI Admin APIs or PowerShell to list workspaces and artifacts.
  • Download .pbix files for reports/datasets.
  • Export notebooks, pipelines, and Lakehouse data manually.
• Rebuild in the new tenant:
  • Re-publish reports and datasets.
  • Recreate Lakehouses, notebooks, and pipelines using the exported files.
  • Reconfigure RLS, credentials, and user roles from scratch.
• Note: Fabric capacities and user identities don’t transfer, so you’ll need to reassign everything manually.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[v-kpoloju-msft · Accepted solution]

Hi @luisr-optimus,

Thank you for reaching out to the Microsoft fabric community forum. I have identified few workarounds that may help resolve the issue.

Thank you for your inquiry about migrating Microsoft Fabric resources across different Azure Tenants or Subscriptions.

Currently, there is no direct or automated migration path available for Microsoft Fabric between different Azure tenants or subscriptions. This includes Fabric capacities, workspaces, and artifacts such as Lakehouse’s, notebooks, and pipelines. If you need to perform such a migration, usually due to organizational changes, you will have to use a manual re-deployment approach.

Set up Fabric in the destination tenant: Ensure Microsoft Fabric is enabled, and the necessary capacities (F/P SKUs) are provisioned. Inventory your current environment: Utilize Power BI Admin APIs or PowerShell to extract workspace and artifact metadata.

Export artifacts: Download .pbix files for reports and datasets. Export notebooks, pipeline definitions, and data from Lakehouse’s or warehouses.

Recreate assets in the new tenant: Manually republish reports and datasets. Rebuild Lakehouse’s, notebooks, and pipelines using exported data. Reconfigure security, RLS, and refresh credentials. Reassign users and workspace roles in the destination tenant.

Fabric capacities are not transferable across tenants you will need to relicense them. User identities and permissions do not migrate and must be recreated. Data refresh and gateway configurations will also need to be set up again.

Also kindly please refer to the below mentioned link for better understanding:
Migrate Data with the Migration Assistant for Fabric Data Warehouse - Microsoft Fabric | Microsoft L...

For further insights from the community, you may find this discussion useful, which addresses similar challenges related to tenant-to-tenant Fabric migration.
Solved: MS Fabric migration between tenants - Microsoft Fabric Community
Solved: Re: Tenant migration - Microsoft Fabric Community

These discussions align with the official guidance that Microsoft Fabric does not currently support automated tenant-to-tenant migration. Manual re-deployment remains the recommended path.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

[v-kpoloju-msft]

Hi @luisr-optimus,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.