Power BI reports as references in Copilot Notebooks: useful, if permissions carry over properly
Quick summary
Copilot Notebooks can now add Power BI reports as a reference source, rolling out from late September 2026, covering:
A genuinely useful capability, though the one detail Microsoft hasn’t spelled out, how existing report-level permissions carry over, is worth checking before it’s relied on with anything sensitive.
Copilot Notebooks can now pull in Power BI reports as a reference source, so summaries, presentations and briefs generated from a Notebook can be grounded in real business data rather than documents alone. For organisations already using Power BI and Copilot together, it’s a small addition that could remove a fair bit of manual copying and pasting. The part worth pausing on is what happens to the permissions already sitting on those reports once they’re pulled into a Notebook.
What’s changing
Public preview begins worldwide in late September 2026 and is expected to complete by mid-October 2026. General availability follows worldwide from late October 2026, expected to complete by mid-November 2026 (Message ID MC1474458, published 19 September 2026).
Once available, users can add a Power BI report to a Copilot Notebook as a reference, in the same way they might add a file. Copilot then uses the data in that report to help generate more relevant summaries, presentations and briefs, grounded in the organisation’s own figures rather than working from documents alone. Organisations that already have Power BI and Microsoft 365 Copilot enabled need nothing further; the capability becomes available automatically. Organisations that don’t use Power BI won’t see any change.
Why this matters more than it first appears
This is a useful, low-friction addition on the surface, but it raises one question Microsoft’s own announcement doesn’t answer:
- Power BI reports are often built with row-level security and dataset-level permissions, so that different users see different data from the same report depending on their role or access.
- Microsoft’s announcement says a report can be referenced inside a Notebook, but doesn’t state whether those existing permissions are respected, or how, once the report is pulled in this way.
- This is worth checking directly rather than assuming either answer. We haven’t been able to independently confirm how permission enforcement works for this specific integration, and until Microsoft publishes that detail or an organisation tests it directly, it shouldn’t be assumed either way.
None of this means the feature is unsafe. It means the one thing worth confirming, if any of your Power BI reports carry row-level security, is whether that security travels with the report into a Notebook, before referencing anything containing data not everyone in the Notebook should see.
Who’s affected
- Organisations that already use both Power BI and Microsoft 365 Copilot, who’ll see this capability appear automatically
- Anyone who builds or maintains Power BI reports with row-level security or restricted dataset permissions
- Users of Copilot Notebooks, the persistent workspace feature Copilot Notebooks already provides
What we’d recommend doing now
No admin action is required, but this is worth a closer look if your Power BI reports carry any access restrictions:
- Identify which Power BI reports use row-level security or restricted permissions, if you haven’t already got a clear list.
- Check, before relying on this with sensitive reports, whether those permissions carry over when a report is referenced inside a Notebook. Treat this as unconfirmed until you’ve verified it against your own tenant, not as settled either way.
- Brief anyone who builds Notebooks regularly that this option now exists, and that it’s worth checking report permissions before referencing anything restricted.
- No documentation overhaul is needed if your organisation doesn’t use Power BI; this simply won’t apply.
Where we can help
If you’d like a second set of eyes on how this interacts with your existing Power BI governance, we can help in a couple of ways.
Talk to a consultant about Copilot readiness →
Explore our Microsoft 365 Copilot training →
This update is based on Message ID MC1474458, published 19 September 2026. Rollout dates are provided by Microsoft and may change.
Worth checking your Power BI permissions before you rely on this
Frequently Asked Questions
What is changing with Copilot Notebooks and Power BI?
Copilot Notebooks can now add Power BI reports as a reference source, alongside files, so Copilot can use that report data when generating summaries, presentations and briefs.
Do I need to set anything up to use this?
No, if your organisation already has Power BI and Microsoft 365 Copilot enabled, this capability becomes available automatically. Organisations that don't use Power BI won't see any change.
Does this feature respect existing Power BI permissions, such as row-level security?
Microsoft's announcement doesn't confirm this either way. It's worth checking directly against your own tenant before referencing any report with row-level security or restricted dataset permissions inside a Notebook.
Is this related to the earlier Copilot Notebooks update?
Yes. This extends the Copilot Notebooks capability, the persistent workspace inside the Microsoft 365 Copilot app, by adding Power BI reports as a new type of reference source alongside files and chats.
When is this rolling out?
Public preview begins worldwide in late September 2026, expected to complete by mid-October 2026. General availability follows worldwide from late October 2026, expected to complete by mid-November 2026.
