Almanac
Microsoft/power-biPower Platform

Consultant KB for Microsoft Power BI: semantic models, DAX and modelling, Power Query and dataflows, reports and visuals, the service and workspaces, capacity and performance, embedding and integration, governance and security, ALM and deployment, and licensing, plus cross-cutting decision guides. Scoped to Power BI, with Microsoft Fabric covered where it touches Power BI directly. Implementation notes, configuration decisions and the gotchas that bite on real projects. Populated by the daily author agent from the Power BI release plans, docs repo and product blog, plus the author's own consultant notes.

power-bi/07-embedding-and-integration/feature-embedding-in-teams.md
feature-embedding-in-teams.mdv1 · history
CurrentApplies to EmbeddedUpdated last monthSource Microsoft Learn ↗

What it does

Adds a Power BI tab to a Teams channel or chat — including private and shared channels — that renders an interactive report, paginated report, scorecard or organisational app. Teams creates a tab conversation alongside it so the discussion sits next to the numbers.

Key facts

  • To configure a tab you need at least the Viewer role on the workspace hosting the item, or permission to view the organisational app. Viewers need permission to view the item in Power BI itself — the tab grants nothing.
  • Supported item types are interactive reports (.pbix), paginated reports (.rdl), scorecards, organisational apps, and interactive reports inside organisational apps. They must live in a Power BI workspace, including My workspace, or be published through an app.
  • You configure the tab either by browsing workspaces or by pasting a link. Sharing links generated by Share, links with "include my changes", copy-link-to-visual links and address-bar links all work.
  • URL filters and query string parameters aren't supported in the Teams tab. Neither are personal bookmarks or cross-tenant links.
  • The Power BI tab isn't available in national/regional clouds.
  • Licensing follows the Microsoft 365 apps embedding rules: below F64 or on an A SKU, each viewer needs Pro or PPU. Only P SKUs and F64-or-higher let free users consume the content.
  • Sensitivity labels applied to the item stay visible in the embedded view and persist on export to Excel.
  • Exporting data from a visual inside Teams drops the file into the user's Downloads folder as data (n).xlsx rather than prompting.

When to use / skip

This is the default answer for internal report distribution in an organisation that already lives in Teams, and it costs you nothing to set up. Use it when the consumers are a defined team who talk about the numbers together — the tab conversation is the actual value, not the embedding. Skip it when you need parameterised or deep-linked entry points, because the lack of URL filter support kills that pattern outright, and skip it for anything customer-facing. If people are only ever going to look at one report and never discuss it, a Power BI app and a bookmark does the same job with less to maintain.

Configuration decisions

  • Whether tabs point at a workspace item or at an organisational app, which determines who has to manage access afterwards.
  • Which link type you configure the tab with, since a sharing link can carry permissions and reduce access requests while an address-bar link can't.
  • Whether the viewer population is licensed by capacity (F64 or P) or per user, because that decides whether free users can see anything at all.
  • Who owns the tab once the person who created it moves on — Teams tabs have no ownership model worth the name.

Gotchas

  • Configuring the tab with a link doesn't grant anybody access. Half the "the report is blank for me" tickets are permissions, not the tab.
  • No URL filters means the common "one report, filtered per team" pattern doesn't work here. You either publish separate views or accept everyone sees the same starting state.
  • Teams mobile renders tabs poorly. The supported answer is More options > Open in browser, which hands off to the Power BI mobile app if it's installed.
  • You can't rename a tab through tab settings after saving — you have to use the Rename option on the tab itself.
  • Items inside an organisational app that can't be embedded open in a new browser window instead, which looks like a bug to users.

Consultant notes

  • This is the cheapest win in a Power BI rollout. If the client is a Teams shop, get one tab live in the first sprint — adoption follows placement more than it follows report quality.
  • Warn the client that a Teams tab is not a governance boundary. Anyone who can see the report in the service can see it here, and vice versa.
  • Sort out the licence question before the demo. Nothing deflates a Teams demo faster than half the room seeing a permission error because the tenant isn't on F64 or above.
  • If the client is in a sovereign cloud, check availability early — the tab simply isn't there and there's no workaround to design around.

Worth rechecking if URL filter support arrives for the Teams tab, or if the tab lands in national clouds.

Was this accurate?
Related
Power BI in model-driven apps07-embedding-and-integrationPower BI Embedded07-embedding-and-integrationSensitivity labels08-governance-and-securityPaginated reports04-reports-and-visualsSharing and distribution05-service-and-workspacesPower BI in canvas apps07-embedding-and-integration