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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
anonymouseke
New Member

Problems with making a multitenant setup for embedded Power BI

I am trying to implement the `app owns data` embedded flow for power Bi. I have been succesfull in creating a report, publishing it and displaying it on a webpage with the embed url, token and stuff... that is not the problem.

Now I am trying to setup the reporting so we have 1 (or 1 per tenant) report with each of them containing their own data. Let me give you some context:

We have an SQL database per tenant (they can also host the DB themselfs), all the databases have the same schema and have the same reports. We need a convenient way (with the REST API's or minimal effort) to add a new Tenant to our application.

How do I achieve this with 1 embedded licensed workspace? This is a requirement because we don't have global admin in azure thus we cannot create new Tenants for the application when needed (like microsoft recommends).

 

This I have tried:

What doesn't work:

  • Modify datasource while it is embedded -> all embeddings are updated live with new data, so the tenants could see other reports when viewing them together.
  • Copy of report to get new semantic model -> semantic modeldoes not get new copy, so we cannot modify it
  • Create own new semantic model -> gateway needed and can only be done for onpremise? Push dataset doesn't seem like the right use case either
  • Dateflow cannot be used directly for report -> a semantic model has to be made of it first

What might work:

  • Connecting multiple databases with the same semantic model and then filtering? really no idea about this
  • Maybe somehow copy both a semantic model and report (so we get a new semantic model and report per tenant) and then we can modify the datasource connection string in code?

I have tried different things all day but did not have any success with the multitenancy. If anyone has more insight to this, please help!

 

3 REPLIES 3
anonymouseke
New Member

Hi @GilbertQ ,

 

Thank you for your quick response! Now I am wondering how I would be able to combine multiple databases into 1 semantic model? I would also like it to be auto refreshed. We are aiming at about 40 tenants with quite a lot of data, so I don't really know how big 1 semantic model can get. You got any insights to this?

 

EDIT

Also we should be able to programatically add the new data to the model, is this possible? Adding a datasource with a connectionstring, doing the transformations, updating the semantic model and publishing all via the rest api?

 

Kind regards

Hi @anonymouseke 

 

Depending on how you model your data you could have a lot of rows in your semantic model (dataset) that will not consume a significant amount of memory.

 

I think you could find a way to use a control table which has got all the data sources. You then use this control table to loop through the databases to get the data into your semantic model.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

GilbertQ
Super User
Super User

Hi @anonymouseke 

 

If I was architecting this and the data size wasn't too big, I would create a single semantic model with all the customer's data in a single model. I would then use row level security and when the customer logged in using Row Level

security, there would only see the data that they have got access to. That way you only have to manage a single report and a single semantic model.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

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