Everything else

Start from what you are seeing rather than from what you think is broken. Each page below names the symptom, explains why it happens, and says what to do about it.

Several of these are the product working as designed, which is worth knowing before anybody raises a ticket.


#At a glance

Symptom

Usually because

Macro shows 'Power BI not configured' with a 'Paste a Power BI URL, embed code, or report ID' messag

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 /rep

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 tall report is clipped by the frame rather than expanding the page.

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 is deliberate. The original Connect app hardcoded the frame to full width, and an unclamped pixel w

Scrolling the Confluence page stops when the mouse is over the report; the first click on the report

An invisible 'Click to interact' overlay sits over the report so page scrolling is not captured by it. The first click removes the overlay rather than reaching the report.

Someone types a lookalike address such as app.powerbi.com.example.net and the macro appears to accep

After the strict checks fail, there is a final loose fallback that tests whether the hostname merely contains an allowed host name rather than exactly matching it, so a lookalike hostname ca

Expecting Power BI in the Capable Suite and not finding the macro

Power BI Embed is not part of the Capable Suite. It is a separate app.

There is no Migration tab in the Power BI app's settings

That tab is deliberately hidden for the acquired embed apps, because there is no earlier Capable-native Power BI feature to migrate content from.

After upgrading from the old Connect app, the macro still resolves but the width now behaves differe

The Connect app stored width as a whole number of pixels and applied it to an outer wrapper while keeping the frame itself at 100%.


#In this section



Most of these are expected behaviour.