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 moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
what is the best pratice to handle the below scenario:
Iets say we have multiple workspaces A, B and C and out of it only A has app in that case if users requests the report from B and C workspaces to be added to app A, how do you usually approach this scenario? We want to avoid having the same copies of report accross multiple workspace from maintenance prespective it is hard.
I was thinking about using shared datasets across multiple workspaces but I dont want to rebuild the same report again because it already exist.
Solved! Go to Solution.
You can have a centralized repository for report development (say, a Sharepoint Document Library that holds your PBIX files) and then you can publish each of these reports to whatever workspace you want (ie workspace A). No duplication of work.
Shared semantic models would be an option too but there are some subtleties you will need to consider, like additional permission management and different artifact classification (queries across semantic models are considered "background" rather than "interactive").
Hi @Akmh ,
I would take a moment to thank @GilbertQ , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hi @Akmh ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hello @Akmh,
In Power BI, an App is tied to a single workspace, so you can’t directly pull reports from Workspaces B and C into an App published from A.
What usually works best is picking Workspace A as the App workspace and making sure the reports you want to expose live there. To avoid duplication and maintenance issues, those reports should all connect to a shared semantic model (dataset) using a Live connection.
In real setups, if reports already exist in B and C, they’re typically either re-pointed to the shared dataset or recreated as thin reports in Workspace A, rather than maintaining separate copies across workspaces.
Microsoft covers the shared semantic model approach here:
The best way to manage this is what @lbendlin described. I have used this method in many different organizations. Linking the a reports in a sharepoint would help you to manage this without duplication. You could follow the link below to understand how:
Hi @Akmh
What you can do is use Org Apps in order to do exactly what you are looking for. Here is the documentation. https://learn.microsoft.com/en-us/power-bi/explore-reports/org-app-items
You can have a centralized repository for report development (say, a Sharepoint Document Library that holds your PBIX files) and then you can publish each of these reports to whatever workspace you want (ie workspace A). No duplication of work.
Shared semantic models would be an option too but there are some subtleties you will need to consider, like additional permission management and different artifact classification (queries across semantic models are considered "background" rather than "interactive").
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 |
|---|---|
| 14 | |
| 10 | |
| 10 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 37 | |
| 32 | |
| 28 | |
| 22 | |
| 20 |