Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Sam Duval]

Question for the masses here, kind of long so bear with me. We are a centralized BI department of 3-4 people, and all of us create and publish and make edits to each others power BI reports and paginated reports for anyone who needs a report in the company. Because everything is centralized within the BI department, we we manage all the logic for the report logic in Azure SQL database (not going to debate this method). So the pbix and RDLs are typically sourced back to one stored procedure in the SQL database. To control access to the information, we have established schemas in SQL so end users don’t have access to anything that’s not in their assigned schema. 

This has worked great for the past 2 years, matching active directory groups to schema access and then to a power bi workspace.  However we are looking to reorganize how we store our power BI and paginated reports, as the result of some reorganization and an increase in cross functional collaboration between what used to be mostly siloed into individual departments. So here is the question for those who have a similar scenario, how do you organize your reports and/or manage security/access? 

We are thinking of converting the workspaces into more use case/purpose. So if a report is used to support customer facing interactions it would go into a customer support workspace, finance related reports go to a financials workspace etc.. anyone ever done something like this? 

Thanks for any/all ideas.

——————————
Sam Duval
Data Quality Analyst
Element Financial
Indianapolis IN
——————————