Embedding Power BI Reports in the Intranet: Licensing, Permissions and RLS

Safely embedding Power BI reports in SharePoint, Teams and web apps; the publish to web risk, department separation with dynamic RLS, licensing and gateway checks.
Technical summary
Technology
Power BI, SharePoint Online, Microsoft Teams, DAX, On-premises data gateway, Microsoft Fabric
Topic
Publishing Power BI reports securely on the intranet
Level
Intermediate
Prerequisites
  • Report development with Power BI Desktop
  • Power BI workspace management
  • SharePoint page editing rights
In this article7 sections

The sentence “we embedded the report in the intranet” doesn’t answer the question of who sees which data. The wrong embedding method can open all company data to the internet or show each department the other departments’ figures. Both happen silently; nobody gets an error. Below, we go through the ways to embed Power BI reports in SharePoint, Teams and custom web apps, row-level security, and the licensing and data refresh checks that cause the most problems in the field.

Ways to bring a report to the intranet

Before choosing an embedding method, clarify the consumption scenario. Three questions give most of the decision:

  1. Who will see the report? Only internal Entra ID accounts, or also external people without an account?
  2. Will everyone see the same data? Or different rows by region, department or branch?
  3. Where will the report live? On a SharePoint communication site, in a Teams channel, or in a custom-developed web application?

In internal SharePoint intranet scenarios, the answer is almost always the same: users sign in with their own identity and see whatever they’re authorized for. Microsoft calls this model “embed for your organization” (user owns data). Presenting reports to customers or dealers without accounts requires a different architecture (app owns data, Power BI Embedded capacity and a service principal); we don’t go into that scenario here.

Comparison of embedding methods

Method Authentication RLS Suitable use
SharePoint Power BI web part The user’s M365 session Applied Intranet pages
Teams Power BI tab The user’s Teams session Applied Team/channel reports
Secure embed (Website or portal) Power BI sign-in required Applied Internal web apps
Power BI Embedded (via API) Identity managed by the app Defined by the app Custom apps, external users
Publish to web None, public Not supported Public data only

SharePoint web part

With a report open in the Power BI service, File > Embed report > SharePoint Online generates a link. A Power BI web part is added to the SharePoint page and the link is pasted in; the page, size and visibility of the filter pane are set in the web part. The question we get most often in the field is: “I can open the page, why doesn’t the report load?” Because seeing the SharePoint page doesn’t mean seeing the report. The user must also have view permission on the Power BI side. The cleanest way to match the two permission layers is to share the report with the relevant Entra ID group through a Power BI app and use the same group in the page permissions. One group, one source. For group design on the SharePoint side, see the SharePoint permission model guide.

Teams tab and secure embed

When a Power BI tab is added to a channel or chat in Teams, the report moves into the team context; the permission logic is the same. In a custom internal web app, the secure embed code generated with Embed report > Website or portal can be used as an iframe. With this method, the user is asked to sign in to Power BI, and all permissions and RLS are applied. If an experience integrated with the app’s own authentication and managing filters from code is needed, full embedding is done with the Power BI JavaScript client library and REST APIs. That’s a development job, not paste-and-go.

Why Publish to web isn’t suitable for corporate data

Publish to web turns the report into a public link viewed without sign-in. Anyone who knows the link sees the report and all the data in it; if the link lands on a public page, search engines can find it too. RLS isn’t applied, and access can’t be restricted by identity. Even if the intranet page where the code is embedded is password-protected, the iframe address can be copied. The assumption “the page is on the internal network anyway” provides no protection. The link gets out.

If sharing public statistics is really needed, the report should rely on a separate semantic model containing only open data and shouldn’t be kept in the same workspace as the internal model. Publishing “just a few pages” from the same model isn’t a solution; all the data in the model becomes accessible through the link.

Separating data with row-level security

Row-level security (RLS) shows each user only the rows they’re authorized for, through the same report and the same semantic model. Copying the report per department looks easy on day one; by the sixth month nobody knows which of twelve copies is current. RLS is the right way for both maintenance and consistency.

The dynamic RLS pattern

With static roles, a separate role is defined for each department and members are assigned by hand. As the number of users grows, this becomes unmanageable. With dynamic RLS, an access mapping table (user email and the department code they’re authorized for) is added to the model, and a single role filters according to the signed-in user’s UPN:

// Role: Department Access, filtered table: Department
// The AccessMapping table sits unrelated (disconnected) in the model and is hidden.
[DepartmentCode]
    IN CALCULATETABLE(
        VALUES(AccessMapping[DepartmentCode]),
        AccessMapping[UserEmail] = USERPRINCIPALNAME()
    )

// Model relationship: Department[DepartmentCode] 1 → * Sales[DepartmentCode]
// The filter flows to the Sales table through the single-direction relationship;
// no bidirectional cross-filtering is needed.

This pattern also covers the many-to-many case where a user is authorized for several departments. It’s also possible to solve it by connecting the mapping table with a relationship and using bidirectional filtering with the “apply security filter in both directions” setting; but bidirectional relationships create ambiguity and performance costs in the model. The disconnected table pattern is more predictable. It’s also easier to read when a problem occurs.

The role is defined in Power BI Desktop with Modeling > Manage roles and tested with View as role. After the model is published, members (preferably an Entra ID group) are assigned to the role from the semantic model’s Security setting in the Power BI service; in the service, Test as role checks what a specific user sees. The source of the mapping table can be a SharePoint list or the HR system; a permission change is reflected by a data refresh without republishing the report.

Situations that make RLS ineffective

  • RLS is applied to users with the Viewer role in the workspace. Those in the Admin, Member and Contributor roles, and those with write permission on the semantic model, see all the data. This is the mistake we see most often in the field: making department managers workspace members “to keep it simple”. Publish to consumers through a Power BI app.
  • The Build permission on the semantic model doesn’t remove RLS, but it allows the user to create their own report and export all the data they’re authorized for in the model. Grant this permission deliberately.
  • An empty mapping table in the role definition results in no data, not unfiltered data. When a newly joined user complains “the report is empty”, the mapping table is the first place to look.

Licensing and workspace requirements

The right to view an embedded report depends on the workspace’s capacity and the user’s license. The general rule: for content in shared capacity, both the publishing and viewing users must have a Power BI Pro or Premium Per User (PPU) license. If the content is in Power BI Premium or a large enough Microsoft Fabric capacity (F64 and above), viewers can access it with a free license. To view content in a PPU workspace, the viewer also needs a PPU license. This last item is the one that causes the most surprises after a pilot.

Licensing models and capacity products can be changed by Microsoft. Before making a final decision, verify against Microsoft’s current Power BI licensing page and the existing subscriptions in your tenant’s Microsoft 365 admin center. We compared which Microsoft 365 plans include Power BI Pro in the choosing a Microsoft 365 license article.

In workspace design, development and publishing should be separated: the workspace where reports are developed and the app opened to consumers are managed separately. In large teams, Power BI deployment pipelines make it easier to separate the development, test and production stages. Reports aren’t edited in production.

Data refresh and gateway checks

An embedded report is only as current as its data. Models connecting to on-premises SQL Server, file servers or ERP databases need an on-premises data gateway. In corporate use, standard mode is used, not personal mode; personal mode is tied to a single user and isn’t suitable for shared reports. When that user goes on leave, the report stops too.

The number of scheduled refreshes is limited by license: 8 scheduled refreshes a day with Pro, and 48 a day with Premium and PPU. If more frequent updates are needed, options such as DirectQuery or incremental refresh should be evaluated taking the load on the source system into account; putting DirectQuery load on the ERP during business hours opens another problem.

  • The gateway was installed on an always-on server with low-latency access to the source systems, not on a laptop.
  • A second member was added to the gateway cluster for high availability.
  • Data source credentials were defined with a least-privileged service account, not a personal account.
  • The gateway server’s outbound connections to the Power BI service were verified on the firewall.
  • Refresh failure notifications go to a distribution list or team channel, not to a single person.
  • The gateway software is updated regularly; during an update, the other cluster member keeps the service running.
  • The source of the RLS mapping table was also included in the refresh plan.

To present reports from a single entry point on the intranet home page and in Teams, the dashboard card approach in the Viva Connections setup article can be used. For management dashboards and corporate reporting infrastructure, take a look at our management dashboards and corporate reporting service. For details of embedding options and RLS behavior, the Power BI documentation should be the reference.

Frequently asked questions

Does everyone with permission to the SharePoint page see the embedded report?

No. The Power BI web part runs under the user’s own identity. If the user doesn’t have permission to view the report on the Power BI side and an appropriate license, the web part shows an access message instead of the report. Manage page permission and report permission through the same group.

No. A Publish to web link doesn’t require sign-in; anyone who gets hold of the link sees the report, and RLS isn’t applied with this method. For corporate data, use the SharePoint web part, a Teams tab or secure embed.

I applied RLS but some users see all the data; why?

The most likely reason is that these users have the Admin, Member or Contributor role in the workspace, or have write permission on the semantic model. RLS is only applied to Viewer-level access. Authorize consumers through a Power BI app.

Does every employee need a Pro license to view the report?

If the content is in shared capacity, viewers need a Pro or PPU license. If the content is in Premium capacity or a Fabric capacity of F64 or above, users with free licenses can view it. Since licensing rules can change, verify the decision against Microsoft’s current licensing page.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles