Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →

Released component

Power BI

Power BI embeds a report, dashboard or single tile on your website — either a Publish-to-web link, or a secured token-based embed of a private report that visitors need no licence to see.

The component platform is in pre-launch, so Power BI for WordPress is the route open today — the same Microsoft 365 job, delivered as a WordPress plugin. If the web component is what you need, tell us and we will come back to you.

contoso-retail.example/performance
contoso retail
Regional performance Secure embed · toolbar hidden
Shapes only — no figures are shown, because there is no real report behind this drawing.

A drawing of Power BI on a fictional site, in our own tokens rather than a customer’s brand. The released component renders live Microsoft 365 data; this frame shows its arrangement only.

Putting it on the page

What you paste into the page.

Two lines, and neither of them is a build step. Everything the component shows is resolved from the key at request time, so the markup on the page is the last markup anyone writes.

<script src="https://cdn.wpintegrate.com/v1/powerbi.js"></script>
<wpi-powerbi embed-key="your-embed-key"></wpi-powerbi>
Illustrative markup — cdn.wpintegrate.com stands in for the bundle host. The real snippet, carrying your own embed key, comes from the builder.
  1. The script tag

    One bundle for one component. It defines the custom element and does nothing else — no framework, no build step, and no change to how the rest of the page is built.

  2. The element

    An ordinary HTML tag, placed wherever the component should appear — including inside a page builder’s raw-HTML block, a shortcode, or a template partial.

  3. The embed key

    The key resolves to one configured instance — the Microsoft 365 source, the arrangement, the theme, and the domains allowed to render it. Change any of those and the page itself never has to be edited again.

What it does

How it works

The Power BI component renders a Power BI report on your page in one of two modes. Publish-to-web takes a public URL and needs no credentials. Secure mode uses a service principal to mint a short-lived embed token for each view, so a private report can be shown to visitors who have no Power BI licence — optionally filtered per viewer by row-level security.

Why it exists

Publish-to-web is the only easy way to get a Power BI report onto a public page, and it makes that report readable by anyone who finds the URL. The secure alternative has always needed a developer to wire up service principals and embed tokens. This turns that into a form in a builder.

Element
<wpi-powerbi>
Reads from
Power BI Publish to web, The Power BI service via a service principal
Arrangements
4 in the builder
Graph access
managed or proxy — the tenant chooses

Arrangements in the builder

  • Full report
  • A single named report page
  • Dashboard
  • Single dashboard tile

Where it runs

Anywhere you can paste two lines of HTML

A custom element needs no build step and no framework, so where your site is built is not a question you have to answer before this one.

  • WordPress
  • Webflow
  • Squarespace
  • Shopify
  • Wix
  • Astro
  • Next.js
  • Drupal
  • SharePoint pages
  • Plain HTML

Named as examples of places HTML can be pasted. No partnership is implied and none of these are customers. WordPress is the one that gets more than an embed — the same Microsoft 365 jobs also ship as plugins with a Gutenberg block.

In detail

Everything Power BI does.

8 capabilities, every one of them resolved from the embed key rather than written into the page.

  1. Two embed modes

    A Publish-to-web URL for a report that may be public, or an app-owns-data embed where the server issues a short-lived token per view for a report that must not be.

  2. Reports, dashboards and tiles

    Secure mode can embed an entire report, one named page of a report, a dashboard, or a single dashboard tile.

  3. Row-level security per viewer

    Where the dataset defines RLS roles, the embed token is minted with an effective identity, so one embed shows each viewer only the rows they are entitled to.

  4. Show or hide Power BI’s own chrome

    The toolbar, filter pane, bookmarks pane and report page tabs are independently switchable, so the same report can be a full analysis surface on one page and a single clean visual on another.

  5. Saved views that stay with the visitor

    Visitors can capture the current filter state and re-apply it on a later visit. It is stored in their own browser and never written back to Power BI, which is what lets it work with a read-only embed token.

  6. Fullscreen and print

    Optional action buttons rendered above the embed and driven by the Power BI client SDK.

  7. Sized and labelled by you

    A pixel height, any CSS width, an optional title and description above the report, and a loading placeholder carrying your own text and image while the report renders.

  8. Locale, domain allowlist and custom CSS

    Render the report in a specific locale, restrict the embed to the domains you list, and style the surround with custom CSS.

One of these you can have today.

Power BI for WordPress is on sale in the store now and does this job inside WordPress. The web component is in pre-launch — if that is the delivery you need, tell us and we will come back to you.

Reaching your tenant

Two ways for us to reach Graph. One of them never lets us.

Every tenant runs in one mode or the other, and the choice belongs to your IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.

managed

We hold the credentials

WPIntegrate runs the client-credentials flow for your tenant. Your administrator grants consent once and is not asked again.

proxy

You hold the credentials

You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.

Questions

The things people ask before they buy.

If yours is not here, ask it — the answers come back from a person rather than a form.

Do viewers need a Power BI licence?

No. In secure mode the server holds the service principal and mints an embed token for each view, so a visitor with no Microsoft account at all can see the report.

Is Publish-to-web safe for private data?

No, and that is Microsoft’s own position: a Publish-to-web URL is readable by anyone who has it. Use secure mode for anything that should not be public.

Can different visitors see different rows?

Yes, where the dataset defines row-level security roles. The embed token is minted with the roles and username you configure, and the report filters itself accordingly.

Can visitors save their filters?

Yes. Saved views capture the current state in the visitor’s own browser and can be re-applied later. Nothing is written back to Power BI.

Can we embed one visual rather than a whole report?

Yes. Secure mode can target a single dashboard tile, or one named page of a report.