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
This is my first post on this forum.
I understand the security can be provisioned on MS PowerBI dashboard.
My question is related at the desktop level. If we have a set of senior business executives creating the MS PowerBI reports against a Stored Procedure on premise SQL Server, how should I architect the security? Should I put their network AD accounts into a AD group and give that AD group permission to that SP? Or should I use a SQL Authentication account? Also, because this is an on-premise SQL Server, I will have to install a gateway. In the past, I would install one gateway onto a server and that provides connectivity. Is this still the practice?
Any other tips, please feel free to share.
Thank You
Do you mean that you want some users to access stored procedure and some users cannot have access to this sp?
Please confirm my understanding.
I think I am asking what is the standard practice for business users to develop MS PowerBI Desktop reports and then they publish up to their workspaces.
That is the whole point of MS PowerBI where the business users can create their own reports, right? But what is the right practice to give them access to a Stored Procedure? Thanks
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 |
|---|---|
| 48 | |
| 46 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 69 | |
| 32 | |
| 27 | |
| 26 |