Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
We have an on premise sql server with multiple identical databases (only the data is different) on it for different customers.
Using an enterprise gateway it should be possible to publish reports on app.powerbi.com which use these databases as datasources.
But since these databases belongs to multiple customers, each customer should only be able to use the datasets from his database.
Is this possible using powerbi.
Or should we replicate our data which we want to use in the reports from our on premise sql server to to sql azure (account of our client(s)) and publish the report in the powerbi subscription of our client(s) individual
Solved! Go to Solution.
Hi Franky,
if you want to publish the data into the database infrastructure of your clients, you would need acceess to their Power BI accounts etc. This sounds tricky, as most likely you have to setup each machine with an own AD etc., so the client users can authenticate against your infrastructure. Nevertheless, I see a complicated security architecture there.
Thus I would recommend the second option. Publishing data to client's Azure SQL DB sounds smarter. In the PBIX-file you could use the "live connect" and just replace the database name below it. Also, you do not have to care / centrally administrate all the clients accounts. Also, the security issue would not be that big.
BR
Hi Franky,
if you want to publish the data into the database infrastructure of your clients, you would need acceess to their Power BI accounts etc. This sounds tricky, as most likely you have to setup each machine with an own AD etc., so the client users can authenticate against your infrastructure. Nevertheless, I see a complicated security architecture there.
Thus I would recommend the second option. Publishing data to client's Azure SQL DB sounds smarter. In the PBIX-file you could use the "live connect" and just replace the database name below it. Also, you do not have to care / centrally administrate all the clients accounts. Also, the security issue would not be that big.
BR
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |