This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I am sure that this has been asked a few times, and while I am searching for solutions, I thought that I would post this scenario/question here, looking for comments/solutions/how you are doing things similar/etc.
We have different Business groups creating PowerBI reports/dashboards for their end consumers.
We (as in the company's IT group) are trying to "reel" in the creation of reports/dashboards and create a deployment workflow that we can share with leadership. To stop the "Wild West" type of approach to Business users.
With different groups "developing" PowerBI reports/dashboards, what is the process that you and your company use? We have thought about incorporating each Business Group their own PowerBI workspace to work with, then have a consolidated workspace, then have each PowerBI developer check in/out their PowerBI "code" into a code management solution (similar to TFS or ADO), then have a "TEST" environment, once the PowerBI "code" is "blessed", promote it to a "PROD" environment for consumers to use (view reports/dashboards, etc).
Is this the correct way of thinking?
How are you and your company working similar to this process now? And, is it successful, what would you update?
Thank you
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |