Microsoft has delivered one of the most consistently requested Power BI features the ability to create multiple org apps per workspace in Microsoft Fabric. Previously, a single workspace could only publish one app to users, forcing BI teams into a painful choice between workspace sprawl and over-bundled apps that served nobody particularly well. That constraint is now removed.

Power BI org apps are Power BI workspace apps reimagined as native Microsoft Fabric item types. You can create, manage, share, and govern multiple org apps from a single workspace - exactly as you would manage any other Fabric artefact such as a report, semantic model, or dataflow.

What Are Power BI Org Apps?

Org apps (organisational apps) are the next generation of Power BI workspace apps, redesigned as first-class Microsoft Fabric item types. Unlike the original Power BI app experience, which was tightly coupled to the workspace itself and limited to one app per workspace org apps are independent items you create, configure, and manage alongside reports, lakehouses, and semantic models within the same workspace.

Because org apps are items rather than workspace settings, they participate fully in the Fabric item ecosystem: they appear in lineage view, are tracked in the activity log, support sensitivity label inheritance, and integrate with Fabric deployment pipelines. This is a meaningful governance and operational improvement over the classic app model.

"With org apps, the question is no longer which audience gets the one app we can publish from this workspace. The question is how we design each audience's experience for maximum relevance and minimum clutter."

Org Apps vs Classic Workspace Apps: The Key Differences

Before committing to a migration strategy, it helps to understand precisely where the two models differ. The table below compares the capabilities of classic Power BI workspace apps against Fabric org apps across the dimensions most relevant to enterprise BI teams:

Why Multiple Apps Per Workspace Changes Everything for Enterprise BI

The single-app-per-workspace constraint in classic Power BI forced a structural decision that had significant downstream consequences. Teams either accepted a one-size-fits-all app that mixed content inappropriately across audiences, or they created separate workspaces per audience multiplying governance overhead, breaking dataset lineage, and creating maintenance burdens that scaled linearly with the number of user groups.

With Power BI multiple apps per workspace, both anti-patterns become unnecessary. A single, well-governed workspace with certified semantic models can now support:

• A CFO executive app with high-level financial KPIs and variance summary
• A Finance team app with full P&L detail, GL drill-through, and budget workings
• A Department heads app with cost centre budget vs actual, filtered by row-level security to each head's scope

All three apps, from the same workspace, the same certified semantic model, without duplication.

Step-by-Step: Creating Multiple Org Apps in a Microsoft Fabric Workspace

Follow these steps to create your first org app item. Ensure you are working in a Fabric-enabled workspace (F-SKU or trial capacity) with org apps preview enabled in your tenant settings.

The Fabric workspace toolbar — click + New item to open the full item catalogue including the Org app (preview) option.

Select Org app (preview) from the Fabric item catalogue and assign an audience-specific name to differentiate it from other org apps in the same workspace.

The org app editor, click Add content to select which workspace reports and dashboards appear in this app. Each app manages its content independently.

Governance Implications: What Power BI Admins Need to Know

The shift from workspace apps to org app items has important implications for Power BI administrators and data governance teams. These are the four areas that most immediately affect enterprise governance posture:

Audit Trail and Activity Logging

Org app creation, modification, publishing, and access events are captured in both the Microsoft Fabric activity log and the Power BI unified audit log in Microsoft Purview. Compliance teams get a complete, item-level record of every org app lifecycle event across the tenant, a materially stronger audit position than the workspace-level logging available for classic apps.

Sensitivity Labels and Data Classification

Org apps inherit sensitivity labels from the underlying reports and semantic models they surface. A report carrying a Confidentiallabel in Microsoft Purview propagates that classification to the org app experience automatically ensuring data classification is maintained end-to-end without manual relabelling at the app layer.

Deployment Pipelines

As native Fabric items, org apps integrate fully with Fabric deployment pipelines. You can promote org apps from Development → Test → Production using the same controlled release process you already use for reports and semantic models - replacing the manual publish-and-share workflow that classic apps required at each environment transition.

Tenant Admin Controls

Org app creation and publishing is controlled through Fabric Admin Portal → Tenant Settings. Admins can enable creation for the entire organisation or restrict it to specific security groups, control external sharing permissions, and set visibility defaults - the same governance levers available for other Fabric item types.

Enterprise Use Cases: Multiple Org Apps Per Workspace in Practice

Here are the three highest-impact scenarios where Power BI multiple apps per workspace delivers immediate, measurable value for enterprise teams:

Finance Reporting - Three Audiences, One Workspace

A single Finance workspace containing P&L reports, budget variance dashboards, cashflow forecasts, and GL-level detail can simultaneously serve three distinct audiences: a CFO Executive App with high-level KPIs, a Finance Team App with full transaction-level drill-through, and a Department Heads App with budget vs actual scoped to each head's cost centres via row-level security. Same certified dataset. Three app experiences. Zero workspace duplication.

Sales Performance - Region, National, and Rep-Level Views

A Sales workspace can publish a Regional Manager App with territory-level performance, a National Sales Director App with consolidated pipeline and revenue, and a Sales Rep App with individual quota attainment and deal-stage detail — eliminating the three separate workspaces that were previously required to deliver the same segmented experience.

Operations and Supply Chain

Warehouse operations, logistics coordination, and executive operations review each require different data granularity, different KPIs, and different levels of operational detail. Org apps allow all three audiences to receive a purpose-built experience from the same operations workspace - without over-permissioning any group or building duplicate data models to serve different views.

Preview Limitations: What to Be Aware of Before Production Deployment

As with any Microsoft Fabric preview feature, there are important limitations to understand before deploying org apps in production environments:

• Preview features can change the org app experience, APIs, and admin controls are subject to change before general availability
• Fabric capacity required org apps require a Fabric-enabled workspace (F-SKU or Fabric trial). Power BI Pro-only workspaces do not support org app items during preview
• Mobile app support is evolving the Power BI mobile app experience for org apps is still being refined during the preview period
• Embedding behaviour differs org app embedding in external applications may behave differently from classic Power BI app embedding during preview
• No automated migration there is currently no automated migration path from classic workspace apps to org apps. Existing apps require manual recreation as org app items

How to Enable Org Apps in Your Microsoft Fabric Tenant

Before workspace users can create org app items, a Fabric tenant admin must enable the feature. Here is the exact configuration path:

1. Go to Microsoft Fabric Admin Portal - navigate to fabric.microsoft.com, then select Admin from the left navigation
2. Click Tenant Settings in the Admin Portal left panel
3. Search for "Org apps" in the settings search bar at the top of the Tenant Settings page
4. Expand "Create and publish org apps" and toggle it to Enabled
5. Choose The entire organisation or restrict to Specific security groups as required by your governance policy
6. Click Apply — the setting propagates across the tenant within approximately 15 minutes

Once enabled, workspace members with Contributor role or higher in a Fabric-enabled workspace will see Org app (preview) in the New item catalogue.

Conclusion

Power BI multiple apps per workspace - delivered through Fabric org apps as native item types, solves one of enterprise Power BI's most persistent limitations. By decoupling app creation from the workspace-level single-app constraint, Microsoft has given BI teams the flexibility to serve multiple audiences with purpose-built experiences, while simultaneously strengthening governance through item-level audit trails, sensitivity label inheritance, and deployment pipeline integration.

For teams running on Fabric capacity, org apps should now be the default distribution model - replacing the classic single-app workspace pattern and eliminating the audience-driven workspace sprawl that undermined governance in many enterprise Power BI estates. Enable the preview in a test workspace today and build a more scalable, governed Power BI app distribution strategy on Microsoft Fabric.