Power BI Copilot has been available in the Power BI Service for reports accessed through workspace apps since its initial rollout — but its availability has been bounded by who accessed reports through that channel. In most enterprise Power BI deployments, workspace apps serve a relatively small audience: the analysts, developers, and data team members who work directly in the Power BI Service environment. The larger audience — the operational managers, business unit heads, and frontline staff who consume reports through Power BI org apps as part of their standard workflow have been outside the Copilot boundary. The preview announcement of Power BI Copilot in org app reports changes this, extending the same AI-assisted data exploration to the broader business audience that org apps are designed to serve.

Workspace Apps vs Org Apps: The Distribution Model That Shapes This Update

Understanding why this update matters requires understanding the distinction between the two Power BI app distribution models that enterprise organisations use.

A workspace app is a Power BI app published from a specific workspace a curated bundle of reports and dashboards from that workspace, made available to a defined audience of Power BI Service users. Workspace apps are the standard distribution mechanism for reports maintained by a central analytics or BI team: the Finance BI team publishes a Finance app from the Finance workspace, the Sales Analytics team publishes a Sales app from their workspace, and so on. The audience for workspace apps is users who are logged into the Power BI Service and have been granted access to the app.

An org app short for organisational app — is a different distribution model introduced to serve broader business audiences. An org app is published organisation-wide rather than to a specific defined audience, making it discoverable by all users in the Entra ID tenant without requiring individual access grants or explicit app sharing. Org apps are typically used for reports that are genuinely organisation-wide in relevance — all-employee HR and wellbeing dashboards, company performance scorecards, organisation-wide policy compliance trackers — where the friction of managing individual audience lists is inappropriate and the content is appropriate for all employees to view.

"Org apps reach the audience that workspace apps miss: the frontline manager who never logs into the Power BI Service but opens the company dashboard every morning from Teams. That is the audience that Copilot in org apps now serves and it is typically the largest audience in the organisation."

Why the Copilot Gap Between Workspace and Org Apps Mattered

Before this update, the Copilot pane was available in the Power BI Service report viewing experience and in workspace apps — but not in reports accessed through org apps. For organisations that distribute their most widely consumed reports via org apps, this meant that the users who would benefit most from Copilot's natural language assistance business users without deep Power BI expertise who need help interpreting complex reports — were precisely the audience that Copilot did not reach.

The irony is that workspace app users are typically the analysts and power users who need Copilot the least — they understand the report structure, know which filters to apply, and can navigate to the data they need without AI assistance. The org app audience is the reverse: they may open a report infrequently, are unfamiliar with its navigation and filter options, and are most likely to benefit from a natural language assistant that can explain what a chart shows, answer a specific data question, and highlight what changed since the last period.

What Changed: Copilot in Org App Reports

The preview capability extends the Power BI Copilot pane to reports accessed through org apps, for users whose organisation has Copilot enabled and who hold a valid Copilot licence. When a Copilot-licensed user opens an org app and navigates to a report page within it, the Copilot pane is available in the same position and with the same capabilities as in a workspace app or the Power BI Service report viewer.

This extension does not change the underlying Copilot functionality — the same natural language question, report summary, and insight generation capabilities that are available in workspace apps are now available in org apps. What changes is the distribution scope: Copilot is now reachable by users who access Power BI content through the org app channel, which in many organisations represents the majority of the total Power BI audience.

What the Copilot Pane Does in an Org App Report

For users encountering the Copilot pane for the first time in an org app context, the pane offers three primary interaction modes that are designed specifically for the business user audience.

Report summaries. The user can ask Copilot to summarise the current page's content — "What does this page show?" or "Summarise the key findings on this report" — and Copilot generates a narrative description of the report's primary visuals, the data they show, and any notable patterns or changes visible in the current filter context. For a business user who opens an unfamiliar report or a report they have not accessed in several weeks, this immediate context is significantly more useful than reading through the visual by visual in sequence.

Natural language questions. The user can ask specific questions about the data "Which region had the highest sales last month?", "What drove the decrease in Q3 margin?", "Show me the top five products by revenue this year" and Copilot retrieves the answer from the report's connected semantic model, returning either a narrative response, a visualisation, or a specific data value. The question is answered in the context of the current report page's filter state, so a user who has applied a region slicer receives Copilot answers scoped to that region's data.

Insight generation. Copilot can be asked to identify anomalies, trends, or comparisons visible in the report data that the user may not have noticed — "What are the key changes compared to last quarter?" or "Are there any unusual patterns in this data?" — and returns a structured narrative of findings. This mode is particularly valuable for periodic review reports where the primary use case is identifying what changed rather than monitoring a specific metric.

Licensing and Prerequisites

Copilot in org app reports carries the same licensing requirements as Copilot elsewhere in the Power BI ecosystem. Both conditions must be met simultaneously for a user to access the Copilot pane in an org app report.

First, the organisation must have Power BI Copilot enabled at the tenant level by a Power BI administrator — the parent tenant setting that gates all Copilot functionality. Second, the individual user must hold a Copilot licence — a Microsoft 365 Copilot licence or a Fabric Copilot licence assigned to their user account. Users without an individual Copilot licence will not see the Copilot pane in org app reports, even if the tenant setting is enabled.

The workspace hosting the semantic model that the org app report connects to must be backed by a Power BI Premium or Fabric capacity. Copilot features are not available on shared Pro capacity workspaces — a prerequisite that applies to org app Copilot exactly as it does to workspace app Copilot. For organisations that distribute their org app content from Pro-capacity workspaces, upgrading to at least an F2 or P1 capacity is a prerequisite for enabling Copilot in those reports.

Admin Enablement: How to Turn It On

The enablement path for Copilot in org app reports follows the standard Power BI Copilot admin flow. The Power BI administrator navigates to the Admin Portal → Tenant Settings → Copilot and Azure OpenAI Service section and ensures that the Copilot tenant setting is enabled. No separate toggle specifically for org app Copilot is required — once the tenant-level Copilot setting is on, Copilot becomes available in both workspace apps and org app reports for licensed users whose workspace is on Premium or Fabric capacity.

The security group scoping available for the tenant Copilot setting allows the administrator to enable Copilot for a defined subset of the organisation during a phased rollout for example, enabling it first for a pilot group of business users who access the org app, gathering feedback, and expanding the rollout once the team is confident in the user experience and data governance posture.

Data Access and Governance in the Org App Copilot Context

The data governance implications of Copilot in org app reports are consistent with Copilot elsewhere in Power BI: the Copilot pane respects all access controls defined in the underlying semantic model. Row-Level Security filters are applied before any Copilot response is generated — an org app user with an RLS filter that limits them to their own department's data receives Copilot answers derived only from that department's data, even if they ask a question that would logically span all departments.

For org apps which by definition are published to the full organisation the semantic model's RLS configuration is the primary mechanism that ensures each user's Copilot interaction is scoped to their authorised data. Organisations that publish org app reports from semantic models without RLS should review whether the data those reports expose is genuinely appropriate for all-employee access before enabling Copilot in that app. Copilot does not introduce new data access risks, but it does make data exploration significantly easier — which increases the likelihood that users will discover data they were not expected to engage with in the absence of a natural language interface.

Impact on Enterprise Self-Service Analytics Programmes

For enterprise organisations that have invested in self-service analytics programmes building the data literacy of business users so they can answer their own data questions rather than submitting requests to the analytics team — Copilot in org app reports is a material capability addition. It provides a natural language interface for data exploration that meets non-technical users where they are: they do not need to understand which visual to look at, which slicer to apply, or how to navigate the report to find a specific answer. They ask the question in plain language and get the answer.

The practical effect on analyst workload is the reduction of routine data request volume: questions like "What was last month's revenue by product line?", "Which branch had the lowest customer satisfaction score?", or "How does our headcount compare to this time last year?" are answerable directly by the business user through Copilot, without involving an analyst. The analyst's time is freed for the questions that genuinely require analytical expertise — not because the business user has developed data literacy, but because the natural language interface has made the routine extraction task self-serviceable.

Copilot Availability Comparison: Workspace Apps vs Org Apps

Next Steps for Enterprise Power BI Teams

For enterprise Power BI teams that have already enabled Copilot for workspace app users and are now evaluating the extension to org apps, the readiness check has two components. First, confirm that the semantic models powering the org app reports have appropriate RLS configurations for the broader audience that org apps serve. Second, confirm that Copilot licences are available for the intended org app Copilot audience — the per-user licence requirement means that enabling Copilot in org apps for all employees requires Copilot licences for all employees, which is a meaningful budget consideration if Copilot licences are currently held only by the analytics team.

For organisations beginning their Power BI Copilot journey and considering the org app distribution model, this preview is the right time to evaluate whether the org app architecture is the appropriate distribution mechanism for the reports that would most benefit from Copilot — high-traffic, broadly consumed reports that generate significant analyst support request volume. For a full picture of Power BI Copilot's capabilities across all its distribution contexts, see our posts on Power BI Copilot Chat with Your Data and Embedded Copilot and AI in Power BI for enterprise analytics.

If your organisation is designing its Power BI Copilot rollout strategy — including distribution model selection, licence planning, RLS governance review, and the sequencing of Copilot across different user audiences — speak with a certified Power BI consultant at Numlytics. We work with enterprise analytics teams across the US, UK, Australia, and UAE to design AI-augmented Power BI programmes that deliver the productivity benefits to the right audiences in a governed and scalable way.