This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hello I would like to have a best practice scenario for an enteprise level for how to structure the workspace structure and deployment pipeline and git integration.
In the example scenario the Enteprise wants to structure for department (around 10) and wants to keep Semantic Models and Reports on different workspaces (in order to give access to some users to workspaces of only Semantic Model).
I would like to know if a Scenario can manage 10 (Dep) x3 (Dev Test Prod) x2 (dataset + report) workspaces ... and how to manage the versioning controlling through Git.
Keep in mind the most of the users will access through Dept. Aps
Thanks for the answer what is the example of your deployed envoriment? can you make an example?
We have hundreds of developer teams in our company, each with their own idea what CI/CD means. Any example I would mention would be biased. You will have to find your own sweet spot.
The number of workspaces is rarely a concern. There is no known limit of the number of workspaces in a capacity.
Make your setup as complex as it needs to be, but not more.
Check out the April 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 |
|---|---|
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 5 |
| User | Count |
|---|---|
| 24 | |
| 23 | |
| 22 | |
| 21 | |
| 20 |