Forum Discussion
How to deploy Fabric resources across multi tenants
Hi ,
How can we deploy Fabric resources/Items from one tenant to other tenant ?
Example: I have Dev and Test in Tenant01(company.in) and my production in Tenant02(company.global) , now i want to deploy my new items created in fabric DEV to Production . Using Terraform we can do that but is there any way using Azure Devops or internal Azure .
#fabric #dataengineering #fabriclakehouse
Thanks
Rather coincidentally I was looking at a GitHub repository the other day that shows how you can do it with GitHub Actions. So all you need to do is port the logic over for it to work in Azure Pipelines instead.
https://github.com/alisonpezzott/pbi-ci-cd-isv-multi-tenant
I hope this helps.
8 Replies
Hi ObungiNiels ,
Thanks for your response !
Here our Azure Devops is in a different tenant like Azure Devops in TenantA, Dev and Test are in Tenant01 and Production is in Tenant02
- ObungiNiels
Resolver III
Hi navakanth_DE ,
yes I wanted to follow up on this because I missed the part that the AzureDevOps is of course also not working cross-tenant. For cloning the DevOps repo, I'd probably see to colne the repo locally and then create a new repo in the Azure DevOps Tenant02 which can then be connected to your Prod Workspace. Could that work out for you?
kind regards,
Niels
v-aatheequeCommunity Support
Hi navakanth_DE ,
Just checking in ObungiNiels has shared a response to your query on how to deploy Microsoft Fabric resources across multiple tenants.
If the provided solution was helpful, kindly consider marking it as Accepted Answer this helps others in the community who may be facing similar challenges.
If you still need further clarification or are encountering issues, feel free to share more details we’re here to help!
Thank you for being part of the Microsoft Fabric Community!
Hi ObungiNiels ,
We are currently using Terraform to automate this process, although there are still a few manual steps involved — such as parameterizing the notebook ID, lakehouse ID, and other components.
Thank you for your support. We’re hopeful that future updates to Microsoft Fabric will enable seamless multi-tenant deployments.- ObungiNiels
Hi navakanth_DE ,
have you tried using Git for the deploymemt?
I'd try the following steps:
- Create an Azure DevOps repo and connect your Workspace on DEV Tenant to it
- Commit all items from Fabric WS to your repo
- On Test/Prod Tenant, create your emtpy WS to the same repo and sync your workspaces. It will then be populated with all times synced to Git
I'm confident that this should deploy all Git integrated items to your Tenant. Concerning the items, which are currently not Git integrated, I'm afraid that Terraform would indeed be the way to go. AFAIK, this is the only IaC solution which communicated with the Fabric API.
Hope this helps! If this solved your request, please Accept it as solution so other people can find it quickly.
Kind regards,
Niels
KevinChantSuper User
Rather coincidentally I was looking at a GitHub repository the other day that shows how you can do it with GitHub Actions. So all you need to do is port the logic over for it to work in Azure Pipelines instead.
https://github.com/alisonpezzott/pbi-ci-cd-isv-multi-tenant
I hope this helps.
- v-aatheeque
Hi navakanth_DE ,
Just checking in @ObungiNiels KevinChant has shared a response to your query on how to deploy Microsoft Fabric resources across multiple tenants.
If the provided solution was helpful, kindly consider marking it as Accepted Answer this helps others in the community who may be facing similar challenges.
If you still need further clarification or are encountering issues, feel free to share more details we’re here to help!
Thank you for being part of the Microsoft Fabric Community!
- v-aatheeque
Hi navakanth_DE
I wanted to follow up on your question regarding the deployment of Fabric resources from one tenant to another.
As noted by our community member, there are indeed methods to achieve this, including using Azure DevOps for deployment. If the provided solution has addressed your query, I kindly encourage you to mark it as the Accepted Answer. This not only acknowledges the contributor's effort but also assists others in the community who may have similar deployment scenarios.
If you have any further questions or need additional assistance, please don’t hesitate to reach out. We’re here to help!
Thank you for being an engaged member of our community!
