Skip to main content

Org apps with audiences for Power BI and Fabric (Generally Available)

Announcing general availability of org apps in Power BI and Fabric, including one of the most requested capabilities: audiences.

Audiences_4_all.gif

Figure: Org apps with audiences for Power BI and Fabric.

 

Org apps with audiences set you up to get the right reporting to the right people, in just the right experience. Curate and distribute reporting at scale across your organization—from leadership and management to frontline teams—while securely and efficiently building app experiences that help everyone find the data they need, understand what matters to them, and make better decisions from branded and customized experiences built for how they work.

Why audiences matter to you

dustinaskinpbi_9-1781215954110.png

Figure: One workspace app with audiences vs multiple org apps per workspace.

 

When we introduced audiences to workspace apps, many of you told us:
audiences are great, but I need multiple apps per workspace.

Then when we introduced org apps as items, you told us:
multiple apps per workspace are great, but I need audiences too.

What we heard was clear: you want the best of both!

 

Before_after_light.gif

Figure: Multiple org app items per workspace, now with audience support.

 

Organizations rarely have a single audience that uses data in their work, so a single delivery experience is not always quite right. Executives, managers, and frontline teams may all need access to the same underlying data, but each group needs tailored content access and experiences.

 

With org apps and audiences, you now have multiple ways to shape those experiences:

  • Create multiple org apps per workspace: each app can have content curated for and the experience customized for a specific context; like apps for executives, apps for managers, apps per department, an app for a meeting series, or apps for project teams.
  • Or create a single org app with audiences: the overall look and feel stays consistent, while navigation and content are filtered per audience.
  • Or combine both approaches: use multiple apps where needed, and audiences within each app for further targeting.

 

Capabilities within an org app with audiences:

  • Define multiple audiences within an app.
  • Control what each audience sees.
  • Deliver unique navigation and content experiences.
  • Keep everything governed from a single app surface.

Now, it's easier to assign users to audiences. When sharing an org app, you can add users and select their audiences directly from the share experience...no need to manage access audience by audience in a separate publishing / update flow.

 

dustinaskinpbi_7-1781215924645.png

Figure: Select audiences when sharing an org app with others.

 

You can easily design and share the experience that fits each unique need or context in your organization. Sales gets pipeline and forecasting reporting, execs get OKR reporting and real-time dashboards, and frontline teams get regional maps and other reporting…all from one app with audiences or unique apps.

A new approach: audiences as navigation

 

Navigation.gif

Figure: Navigating audiences in an org app with content shown per audience selected.

 

Audiences in org apps are not just about filtering content. They shape how the experience is presented. You define a single navigation structure for the org app, then control what each audience sees within that structure.

 

As items are shown or hidden per audience, the experience feels different for each group, even though it is built on a shared navigation foundation.

 

Capabilities

  • Create audience-specific experiences through visibility of navigation items.
  • Tailor landing experiences without rebuilding the app structure.
  • Have shared and exclusive content across audiences within the same app.

 

bubble_content.gif

Figure: Manage audiences in an org app and configure what content each audience sees.

 

Fun tip: We made it easier for you setup new audiences by starting from an existing audience and duplicating that audience and its item visibility settings.

 

dustinaskinpbi_4-1781215882126.png

Figure: Duplicate an audience and its item visibility settings.

Flexible navigation configurations

On top of audience-based visibility, org apps now give you more control over how navigation is presented. That means you are not only deciding what audiences can see. You can also decide how audiences appear and how they guide app consumers through the app experience.

 

Nav options.gif

Figure: Multiple audience visibility configurations supported.

 

For example, you can:

  • Show both the All tab and audience tabs: great when you want users to move between a broad app view and curated audience-specific views.
  • Hide the All tab: a popular request for apps, great when you want to use audiences as “primary navigation,” like the first audience tab acting as a “Home” page and the org app nav acting as a secondary navigation. This lets you guide users directly into audience-based experiences without a broader catch-all view.
  • Hide audiences altogether: another common request, great when you want the app to feel seamless and context-specific, with visibility rules shaping the experience behind the scenes...with no audience tabs visible.

 

Of note: users who are members of just one audience won't see audience tabs at all.

 

Rather than maintaining separate apps or separate navigations just to achieve what you want, you can design once, then configure the experience to match what you are trying to accomplish per context.

 

You have a lot more flexibility when it comes to distribution with audiences in org apps. We're bringing together secure governance, conditional display, and experience design in one place.

 

We look forward to hearing about what you build when you have the best of both worlds: multiple org apps per workspace and audiences.

Audiences are just the latest in a bigger org apps story

Bringing audiences to org apps is based on what customers told us they needed most. We listened closely to the capabilities you needed in org apps to reduce migration blockers and reach stronger parity with workspace apps. We also invested in capabilities customers have long wanted from workspace apps but could not get until org apps.

 

Org apps general availability is about the right balance of parity and differentiation. It addresses what you need to move from workspace apps to org apps, while also delivering the added value that makes org apps a more powerful long-term approach for distribution.

Let's review what's been introduced since org apps were first launched

 Multiple apps per workspace

 

dustinaskinpbi_2-1781215745719.png

Figure: Create multiple org app items with audiences in one workspace.

 

Org apps are now first-class items in Fabric:

  • Create multiple org apps per workspace.
  • See org apps in OneLake Catalog, workspaces, and workspace task flows.
  • Manage org apps in deployment pipelines and Git.

 Deliver fuller data experiences

 

dustinaskinpbi_1-1781215729370.png

Figure: Add multiple item types as elements in org app navigation.

 

Org apps now support a wide range of content and capabilities:

  • Reports, paginated reports, notebooks, real-time dashboards, and map items
  • Access management for underlying models on reports and paginated reports
  • For reports: support for bookmarks, filtered state persistence, subscriptions, and storytelling...inserting and presenting reports from org apps in PowerPoint
  • Sharing, including the ability for consumers to reshare

 Modern access management

 

dustinaskinpbi_0-1781215716642.png

Figure: Streamlined access management with consistent grant and revoke behavior.

 

Org apps introduce a new approach to access management:

  • Access propagation applies to both items and underlying semantic models
  • Removing a user or removing content revokes access consistently
  • No lingering access to semantic models

This ensures secure-by-default behavior and eliminates a common source of confusion from the previous approach in workspace apps.

Customize the experience

 

dustinaskinpbi_4-1781215569529.png

Figure: Customize branding, navigation, and audience visibility in org apps.

 

Org apps provide powerful customization options:

  • Full color spectrum theming
  • Flexible layout and navigation configurations
  • Overview pages for landing experiences or as indexes of content in the app
  • Preview before publishing changes

With these capabilities, you can shape experiences that feel purpose-built for each org app.

Everywhere your users are

 

dustinaskinpbi_3-1781215564878.png

Figure: Org apps available across desktop and mobile experiences.

 

Org apps are available across Power BI experiences:

  • Power BI service
  • Power BI mobile apps for iOS and Android
  • Support for Pro-licensed workspaces
  • View org apps in the Power BI personal app for Microsoft Teams

Audience support for Power BI mobile apps is coming soon, extending tailored experiences across devices.

Built for staging, scale, and developer workflows

 

dustinaskinpbi_2-1781215556630.png

Figure: Staging, deployment pipelines, and APIs for app lifecycle management.

 

Org apps are built for Fabric-native workflows, reflecting how you manage, stage, and automate experiences.

 

That starts with how content flows into org apps:

  • Items included in org apps are sourced directly from workspace content. By popular request, updates to those items flow automatically into the app.
  • But you can still stage and promote changes using deployment pipelines or Git.

 

This gives you a more Fabric-conventional ability to iterate on items with confidence, working through changes without disrupting production experiences.

 

On top of that, org apps integrate directly with developer workflows:

  • Deployment pipelines for staged rollout across environments
  • Git integration for versioning and collaboration
  • Org app item CRUD APIs for automation and scripting, for both org app items and audience child items

This means org apps are more than a distribution tool; they are part of your end-to-end lifecycle from development and staging to deployment and automation at scale.

Bringing it all together

Bring_it_together_compressed.gif

Figure: Org app icon

 

Org apps have evolved based on continuous feedback:

  • Multiple apps per workspace
  • Access management as you expect it to work
  • Rich customization and navigation
  • Deep Fabric integration for all, especially developers
  • And now, audiences

Audiences complete the vision: a single org app can now serve many experiences, each tailored to the needs of its users, without sacrificing governance or manageability.

Get started, learn more, and thank you!

To use audiences, create a new org app and begin defining tailored experiences for your users.

 

get_started.gif

Figure: Introducing audiences in the org app edit experience.


For those still using workspace apps, there is no published timeline for deprecating Power BI workspace apps, and there is no migration tool for moving workspace apps to org apps. Power BI workspace apps are fully supported alongside org apps going to GA.

 

Thank you to all the customers who posted feedback, met with us at conferences, and took calls and worked closely with us to understand how you use apps today and shared early feedback on org apps.

 

Comments

Popular posts from this blog

SSRS INTERVIEW QUESTIONS

Q: What is SSRS? Ø   SSRS or SQL Server Reporting Service is a server-based report generation software systems from Microsoft and is part of Microsoft BI. Ø   It is used for preparing and delivering interactive and variety of reports. Ø   It is administered through an web based interface. Ø   Reporting services utilizes a web service interface for supporting and developing of customized reporting applications. Ø   SSRS lets you create very rich reports (Tabular/Graphical/Interactive) from various datasources with rich data visualization (Charts, Maps, sparklines) Ø   SSRS allows are reports to be exported in various formats (Excel, PDF, word etc) Q: Explain SSRS Architecture? Reporting services architecture comprises of integrated components. It is a multi-tiered, included with application, server and data layers. This architecture is scalable and modular. A single installation can be used across multiple computers. It includes the fo...

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got...

Failed to execute the package or element. Build errors were encountered

Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package