Macro shows 'Power BI not configured' with a 'Paste a Power BI URL, embed code, or report ID' messag
What you are seeing
The macro shows 'Power BI not configured' with a 'Paste a Power BI URL, embed code, or report ID' message, even though a report was configured.
#Why it happens
The address in the macro did not pass validation. Power BI Embed only accepts app.powerbi.com and app.fabric.microsoft.com addresses whose path is exactly /view (with an r parameter) or /reportEmbed (with a reportId parameter), or a bare report UUID. A workspace or dashboard link copied from the browser address bar is usually a different shape and will be rejected.
#What to do
Go back into Power BI and use the explicit embed option ('Embed report - Website or portal' for a secure report, or 'Publish to web' for a public one) and copy that link or its iframe snippet. Paste that into the macro instead of the address-bar URL.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Power BI global settings entry | Confluence admin - Apps - Power BI | - |
Migration tab | Global settings | - |
Space settings | n/a | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Allowed report hosts | App.powerbi.com and app.fabric.microsoft | Anything else will not render. |
Bare report ID format | A standard 36-character UUID | A UUID is turned into https://app.powerbi.com/reportEmbed?reportId=<id>&autoAuth=true. It always targets app.powerbi.com, never Fabric. |
Scrolling | Off (scrolling="no") | Power BI manages its own scrolling inside the frame, as it did in the original Connect app. |
#A few things that catch people out
The Power BI global settings entry points at an icon file that does not exist in the repository (only the main icon and an unrelated forms image are present).
The Power BI client declares a feature flag (confluence.powerbi), but feature flag gating is only applied inside the Suite app, and Power BI is not in the Suite. The flag therefore does nothing today.
Power BI has no entry in the shared Confluence capability metadata table, which is what several settings and navigation surfaces read from first.
#Related
Report is cut off or too short, and there is a scrollbar inside it that is awkward to use
The frame defaults to 450px tall and the embedded report manages its own scrolling, so a t
Pixel width was set on the macro but the report still fills the whole column
A configured width is treated as an upper bound and clamped to the page column width. This
Everything else
The rest of this family.
Found it? Good.
