Forum Discussion
PowerBI Workspaces
Hi pokesfan_72
Thank you for the clarification.
A common approach is to allow business groups to continue gathering requirements from SMEs and developing reports in their own development workspaces, while implementing controls such as source control, deployment pipelines, workspace standards, and documented ownership. This gives IT visibility into what has been developed, who owns it, and what content is considered supported in production.
In many organizations, IT's role is focused on governance, platform administration, security, and production support, while business teams retain responsibility for report development and business validation. Content that is promoted to production typically follows a defined review and deployment process, ensuring that only approved and supportable solutions become part of the organization's supported reporting portfolio.
This model generally provides a good balance between enabling business innovation and maintaining the governance, supportability and lifecycle management that IT requires.
References : Power BI implementation planning: Develop content and manage changes - Power BI | Microsoft Learn
Workspaces in Power BI - Power BI | Microsoft Learn
Hope this helps !!
Thank You.
Power BI started as a way to circumvent your setup, targeting "citizen developers" that were unbound from the shackles of rigid IT processes.
What exactly are you trying to "reel"? You want to make it harder for business users to get to their insights?
Note that workspaces, reports and dashboards by themselves have no cost. Cost is created by running refreshes or running queries against semantic models, for example.
Controlling cost is a valid objective. Maybe you can shift your focus to that? (Hint: Multiple environments means potential for multiple costs)