Forum Discussion
Deploy Master Semantic Model 2 Multiple Workspaces with Schema Change Using Microsoft Fabric Mirror
- 10 months ago
Thank you for contacting the Microsoft Fabric Community Forum.As mentioned by GilbertQ , the recommended and industry-standard approach is to use a parameterized PBIT deployment together with the Update Parameters API. This is also the Microsoft-endorsed method for managing multi-workspace or multi-tenant Power BI environments.
Create a master Power BI Template (.pbit) that includes your model relationships, measures, and visuals, along with parameters for key data-source elements such as Server, Database, Schema, or Tenant ID. These parameters allow each workspace to dynamically connect to the correct tenant data.
Once the template is ready, use the Power BI REST APIs to automate deployment by importing the .pbit file into each workspace. After that, update the parameter values for each tenant as shown in the snapshot included in the provided ,MS document.
This method fully supports Delta Lake and Microsoft Fabric Mirror connections. You can update parameters like SchemaName for each workspace so it connects to the appropriate tenant schema within the mirrored database.
In short, parameterized PBIT deployment with automated parameter updates is the most scalable, flexible, and Microsoft-supported solution for multi-tenant semantic model management in Power BI and Fabric.
I hope this information is helpful. . If you have any further questions, please let us know. we can assist you further.
Regards,
Microsoft Fabric Community Support Team.
Thank you so much, GilbertQ . What is the Power BI or industry standard in terms of importing reports and the semantic model?
Create a parameter that is used for your data sources — does this work for a Delta Lake connection?
If I want to experiment with the remaining options, could you provide more details?