1. The 4 Causes of “This Content Isn't Available”
Unlike full-page Power BI errors that tell you whether a report was deleted or requires access, Power BI's iframe player hides all authentication and permission failures behind a single generic message: “This content isn't available. Learn more about Power BI.” Here is how to diagnose which of the four underlying issues you are hitting:
Secure Embed (/reportEmbed) Guest Limitations
You added a /reportEmbed link to a Power BI App's navigation (with Open in: Content area) or a portal page. Microsoft documents guest account limitations for the secure embed iframe flow, and an un-scoped iframe can also evaluate against the guest's home tenant instead of the host tenant.
Missing Permission on the Linked Workspace Report
Adding a link to a Power BI App's navigation menu does not grant App Audience viewers access to that linked report. If the report lives in another workspace, viewers must be granted Read access on that report and its underlying semantic model separately.
Third-Party Cookies Blocked by the Browser
When a report is embedded on a different domain (such as SharePoint Online or an internal intranet), app.powerbi.com relies on cross-site session cookies. Safari, Chrome Incognito, and strict Edge tracking prevention block these cookies and trigger the gray error screen.
“Publish to Web” Disabled by Tenant Admin
If the URL uses app.powerbi.com/view?r=..., it is an unauthenticated public embed code. If a Power BI admin turns off Publish to web in the Tenant Admin Portal, all existing public embed codes stop working immediately.
2. External B2B Guest Limitations in /reportEmbed (and How to Open Reports Directly in the Host Tenant)
As covered in our Power BI App “Add a Link” Embed Error guide, linking to a report in another workspace inside a Power BI App's Content area uses a Secure Embed URL (/reportEmbed?reportId=...).
However, Microsoft's secure embed documentation lists explicit guest account limitations for this iframe flow. Even if you append &ctid= to a /reportEmbed URL, external Microsoft Entra B2B guest accounts can still hit “This content isn't available” inside an iframe due to secure-embed guest restrictions and browser third-party cookie policies.
Recommended troubleshooting for B2B guests: Open the shared App or report directly in the host tenant
- 1Avoid the Content area iframe for B2B guests: Instead of forcing an external guest through a nested
/reportEmbediframe, give them the direct Power BI report or App URL and set App links to open in a New tab or Current tab. - 2Include your Host Tenant ID (
?ctid=) on the direct link: Inapp.powerbi.com, click ? (Help & Support) → About Power BI to find your 36-character Tenant GUID, and include?ctid=YOUR-TENANT-GUIDso the link routes the guest into your host tenant rather than their home tenant. - 3Verify guest access and licensing: The
ctidparameter only routes the link to the right tenant. Per Microsoft's Entra B2B sharing documentation, the guest user still needs explicit permission on the report/App (and underlying semantic model) plus a qualifying Power BI Pro, PPU, or capacity license.
4. How LumioBI Eliminates “This Content Isn't Available” Errors
Whether you are unifying reports across internal workspaces or sharing dashboards with external clients, LumioBI removes the brittle /reportEmbed iframe layer that causes tenant and cookie failures:
For Internal Power BI Teams
Top-Level Sidebar on app.powerbi.com
Instead of nesting reports from other workspaces inside a Power BI App Content Area iframe, the LumioBI Chrome Extension pins a unified navigation sidebar directly inside app.powerbi.com. Viewers open native reports and apps in the same tab with zero iframe restrictions.
For Invited Entra B2B Guests
Pre-Configured ?ctid= Links in One Menu
When sharing with licensed Microsoft Entra B2B guests, administrators save the tenant-scoped ?ctid= report URLs once in the LumioBI Portal. Guests see only their assigned group's links in the LumioBI sidebar inside Power BI, while Microsoft Entra and Power BI continue to enforce sign-in, licensing, and RLS.
5. Comparing Cross-Workspace & External Sharing Approaches
| Capability | Power BI App “Add a Link” | SharePoint / Teams Embed | LumioBI |
|---|---|---|---|
| Cross-workspace report links | Requires manual /reportEmbed URL | Requires one web part per report | Native top-level navigation |
| External B2B guest behavior | /reportEmbed has guest limitations | Subject to guest & cookie limits | Opens direct ?ctid= links in top tab |
| Link to other Power BI Apps / Org Apps | Blocked in Content Area | Apps cannot be framed | Links reports, Apps & Org Apps |
6. Frequently Asked Questions
Why does Power BI say “This content isn't available. Learn more about Power BI.”?
Power BI displays this message inside an iframe when the embedded player cannot verify the viewer's tenant context (common for external B2B guests when &ctid= is missing), when the viewer lacks Read access to the underlying report or semantic model, when the browser blocks third-party cookies, or when a public Publish-to-Web code has been disabled.
Why do external B2B guest users see “This content isn't available” inside a Power BI App?
When a Power BI App loads a custom link in the Content area, it opens an iframe to app.powerbi.com/reportEmbed. Microsoft documents guest account limitations for the secure embed flow, and iframe links can also fail third-party cookie checks or evaluate against the guest's home tenant. For B2B guests, open the shared App or report directly in the host tenant in a top-level browser tab using a link with ?ctid=YOUR-TENANT-ID, and verify the guest has access and a qualifying license.