Embedded approaches

[AnonymousPerson]

We want to publish a report portal for 500-1000 customers and are struggling to find an approach.

Requirements:

• Must be simple to access and navigate
  • Rules out "User Owns Data" because
    • The MS365 login is a pain - especially for external users with personal email addresses.
    • Too much of the Power BI portal is exposed, with no apparent way to restrict it (users can browse data hub and author reports in "My Workspace", among other things they don't need to see).
• Must permit user-created subscriptions
  • Rules out "App Owns Data" because
    • There's apparently no way to use subscriptions.
    • Requires web development effort that we are stretched too thin to handle.

[Anonymous · Accepted solution]

Hi  @AnonymousPerson ,

Power BI provides an option to securely embed reports in internal web portals. This method respects all item permissions and data security through row-level security (RLS) and Analysis Services tabular model object-level security (OLS). It requires only basic HTML and JavaScript knowledge1. However, this method still requires users to sign in to Power BI.

Embed a report in a secure portal or website - Power BI | Microsoft Learn

You may also consider using Power BI Embedded Analytics . This is a Microsoft Azure service that lets you embed visuals, reports, and dashboards into an application. This could be a potential solution, but it might require some development effort.

Or you can try subscriptions. Power BI allows users to subscribe to reports, dashboards, and paginated reports. Users receive an email on a schedule they set, which contains a snapshot and link to the report or dashboard. This could be a workaround for the subscription requirement, but it might not be the most elegant solution.

Email subscriptions for reports and dashboards in the Power BI service - Power BI | Microsoft Learn

Best regards.
Community Support Team_Caitlyn

[lbendlin]

Is this for internal use, for external use, or for both? Maybe you need separate solutions for these separate audiences.

If this is for "customers" then "App owns Data" is your only choice, warts and all.