Hi Microsoft team,
We would like to propose a new capability for Microsoft Org Apps to support an enterprise reporting hub across multiple independently managed workspaces.
Proposal: Enterprise Reporting Hub with Org App
We propose extending Org App so that it can act as an enterprise-wide reporting aggregation and navigation layer, providing users with a single, governed entry point to discover and access Power BI reports, paginated reports, and other supported Fabric experiences that are owned and managed across multiple workspaces.
The key requirement is that the content remains in its source workspace.
The Org App would provide the enterprise consumer experience, while the underlying artifacts continue to be developed, secured, deployed, and owned independently by their respective business domains.
Problem statement
We are defining a target architecture for a reporting estate covering approximately 10 business areas, with each area potentially containing 20–100 Power BI and paginated reports.
Our architectural baseline is:
- Domain-oriented workspaces separated by DEV / TEST / PROD
- Microsoft Entra ID group-based access management
- Independent ownership of reporting content by each business domain
- Independent development and deployment lifecycles
- A centralized consumer experience providing users with a single enterprise entry point
- No requirement to move or duplicate reports into a central workspace
The challenge is that users should not need to understand the underlying workspace topology in order to find the reports they need.
Requested capability: Cross-workspace Org App
We would like Microsoft to consider enabling an Org App to:
- Include or reference reports from multiple workspaces without moving or duplicating the underlying artifacts.
- Provide centralized navigation and discovery across independently managed business domains.
- Support audience-based experiences so different Entra ID groups can see the content relevant to them.
- Preserve the security model of the source artifact/workspace, rather than introducing a separate authorization model in the hub.
- Allow source workspaces to maintain their own DEV / TEST / PROD lifecycle and deployment processes.
- Support a seamless user experience when navigating between content belonging to different workspaces.
- Ideally provide extensibility for approved experiences outside Power BI/Fabric, for example Databricks agents or other enterprise applications, while respecting the relevant security boundaries.
Target experience
From the user's perspective, the desired experience would be:
Enterprise Reporting Hub / Org App
→ Executive
→ Finance
→ Operations
→ Sales
→ Other business domains
Users would see a single curated reporting experience without needing to know which workspace contains a report.
From the ownership perspective:
Business Domain → Own Workspaces → Own Reports → Own Deployment Lifecycle
The central Org App would therefore be a discovery and presentation layer rather than an ownership layer.
Why this capability is important
For large enterprises, consolidating hundreds of reports into one workspace is not an appropriate operating model.
At the same time, exposing many separate workspaces or applications directly to end users creates a fragmented consumer experience.
A cross-workspace Org App would allow these concerns to be separated:
Decentralized ownership and lifecycle + centralized discovery and user experience
This would make Org App a strong Microsoft-native option for an enterprise reporting hub without requiring organizations to introduce a separate portal solely for aggregation and navigation.
Could Microsoft please consider this as a feature/enhancement request for Org Apps?
We would particularly value Microsoft's feedback on:
- Whether this capability is already on the Org App roadmap
- Whether there is an existing feature request covering this scenario
- Whether Microsoft sees cross-workspace content aggregation as aligned with the future direction of Org Apps
- Whether there is another planned Microsoft Fabric capability intended to solve this enterprise reporting-hub scenario
- Whether this scenario could be considered for the future Org App product roadmap
We would be happy to discuss the architecture and business requirements in more detail and provide a concrete enterprise use case.
Thank you,
Svetlana Sura
