Forum Discussion

DiKi-I's avatar
DiKi-I
Post Partisan
10 months ago
Solved

multiple workspace power bi deployment

We are building multiple customer solution. Each customer has its own mirror db in workspace. How I can craete a template use it across multilple customer and do automatic parmeter binding for each w...
Need Help
  • tayloramy's avatar
    tayloramy
    10 months ago

    Hi DiKi-I,

     

    You’re essentially describing a classic multi-tenant pattern in Power BI/Fabric: one “golden” solution reused across many customer workspaces, each bound to its own mirrored database. There are two solid ways to do this-one for cross-tenant distribution and one for many workspaces inside your tenant.

     

    • If these customers are in other tenants: build a Template App and parameterize your connections. Each customer fills in their own server/DB (or Fabric item) at install. See Create template apps.
    • If these customers are in your tenant (one workspace per customer): use a “golden” workspace + Deployment Pipeline rules (Parameter Rules, Data Source Rules, and Default Lakehouse Rules) to auto-bind each stage/workspace to the right mirror. See Create deployment rules and Get started with deployment pipelines.

     

    If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

  • v-echaithra's avatar
    v-echaithra
    10 months ago

    Hi DiKi-I ,

    A Power BI Template file (.PBIT) is a reusable report structure that allows for dynamic parameter values when the report is opened.

    Steps:

    Create the Power BI Report: Build a report in Power BI that includes dynamic parameters, such as customer ID, workspace ID, etc.

    Define Parameters: Set up the parameters either in the Power Query Editor or Power BI Desktop, ensuring they can be adjusted as needed.

    Save as .PBIT: Save the report as a .PBIT (Power BI Template) file. This template can then be programmatically modified to reflect the specific parameters for each customer, ensuring they see only their relevant data when the report is opened.

    Reference: Create template apps in Power BI - Power BI | Microsoft Learn

     

    Thank you.

  • KevinChant's avatar
    KevinChant
    10 months ago

    Hi, I highly recommend looking to work with the fabric-cicd Python library if you are looking to do the automatic rebinding when deploying to another workspace:

    https://microsoft.github.io/fabric-cicd/0.1.29/

    Here's a link to an example Git repository that you can use with a YAML pipeline in Azure DevOps that can help you get started:
    https://github.com/kevchant/AzureDevOps-fabric-cicd-sample 

    If this answers your question please give kudos and/or accept as solution.

v-echaithra's avatar
v-echaithra
Community Support
6 months ago

Hi nganesh ,

A 404 after a successful token refresh usually means the token is fine, but the workspace/item ID is wrong, or you’re calling the wrong API for the artifact type.

Check these:

Correct Workspace & Item ID
Make sure the IDs actually exist in that environment.

Use the right API:
Fabric items:
https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items
Classic Power BI datasets:
https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/datasets

Token scope:
Ensure the identity has Workspace role: Member/Admin,
Entra scope: https://api.fabric.microsoft.com/.default

 

Quick Debug


print("Workspace:", workspace_id)
print("Item:", dataset_id)
print("URL:", request_url)
print("Status:", response.status_code)
print("Body:", response.text)


Then verify:
The item actually exists in the workspace
You’re using the correct API for the artifact type
The caller has the right permissions (Member/Admin)

Hope this helps.
Thank you.