How To Embed Power BI In SharePoint With Copilot Turned On

You built the dashboard. You maintain the model and refresh it before every business review. And the only people who open it are the people who built it.

So I put mine somewhere leadership already goes. This walkthrough shows how to embed Power BI in SharePoint with the Copilot pane still attached, so a regional VP can ask the report a question from the intranet page they open every Monday instead of emailing you for the number.

It takes one checkbox and a paid Fabric capacity. Then there’s a second step most people skip: one written instruction on the semantic model that makes every answer come back the way your finance team would present it.

If you’d rather watch the whole build, it’s here.

Your dashboard has a distribution problem

The report lives behind a Power BI login that most of the business opens twice a year. The rest of the time they email you. That’s a distribution problem, and no amount of work on the model fixes it.

Copilot in Power BI used to have the same ceiling. The chat pane sat next to the report inside the Power BI service, so the only people who could ask it anything were the people already in the tool. It’s one of the more useful pieces of AI in Power BI, and it was parked in the one place the CFO never goes.

That changed. A checkbox in the embed dialog now sends Copilot along with the report onto a SharePoint page or anywhere else that takes an embed. The people who ask you for numbers can ask the report.

What you need before you start

• A published Power BI report in a workspace. I use the executive dashboard for F9 Coffee Co., a seven-store demo coffee chain, with the usual set of pages down the left side.
• A paid Fabric capacity at F2 or higher, or legacy Power BI Premium at P1 or higher, assigned to that workspace. I run the smallest one, F2. A Pro license on its own doesn’t switch Copilot on.
• Copilot turned on for your tenant, plus Q&A enabled on the semantic model. Copilot still runs on the Q&A engine underneath.
• A SharePoint site you can edit. If you work in Power BI, you almost certainly have SharePoint too, which is why it’s the surface worth learning first.

If the capacity and the tenant settings aren’t in place yet, that’s its own job. I walk through it in how to set up Power BI Copilot, including the billing side.

What Copilot in Power BI costs

Copilot runs against your capacity, so somebody is paying for it before anyone types a question. Microsoft’s Copilot in Power BI overview sets the floor at a paid F2 or a P1, and says a Pro or Premium Per User license alone isn’t enough. Trial capacities don’t count.

The good news is the floor came down. You no longer need a big capacity for people to use Copilot. F2 lists at $262.80 a month pay-as-you-go on the Microsoft Fabric pricing page, or about $156 a month on a one-year reservation (Central US, September 2026).

The part people miss is the viewers. Below F64, Microsoft’s Fabric licensing rules say every person viewing Power BI content needs a Pro or Premium Per User license, and SharePoint embeds are named specifically. So on an F2, the VP opening your SharePoint page needs a Pro seat and access to the report. At F64 and up, free-license viewers can see it. Price that before you promise it to the whole company.

There’s a deadline worth putting in your calendar too. Microsoft moved the Power BI Q&A retirement to February 2027. After that the Q&A visual stops working and reports carrying one show an error. If people use a Q&A visual on one of your reports today, Copilot is the replacement Microsoft is pointing you at.

Prices, tiers and dates as of September 2026. Microsoft moves these a couple of times a year, so check the linked pages before you write the business case.

How the embed works

SharePoint gets a link to the live report, and the Power BI web part renders it inside the page. Nothing gets copied. The report still runs on your semantic model, with your measures and your refresh schedule, and each viewer is signed in as themselves, so row-level security still applies.

Copilot answers by querying that same model. That’s the reason to do this rather than paste a screenshot into a slide: there’s one version of the numbers, and the page is a window onto it.

Embed Power BI in SharePoint with Copilot turned on

Everything depends on one checkbox in the embed dialog.

1. Open your report in the Power BI service.
2. Go to File, then Embed report, then SharePoint Online.
3. Tick Turn on Copilot. Microsoft’s docs call it Enable Copilot. It’s unticked when the dialog opens, and it’s what lets Copilot use your Fabric capacity to answer questions against the embedded report.
4. Copy the link.

Skip the checkbox and nothing warns you. The report embeds perfectly, the numbers are all there, and the Copilot button isn’t. You can’t fix it from the SharePoint side either. You come back to the report, generate the link again with the box ticked, and swap it in.

That’s also the fix for every Power BI embed already sitting on your intranet. They were created before the setting existed, so none of them have it. Microsoft’s page on how to embed a report in SharePoint Online has the full prerequisites list.

Build the finance hub page

I put mine on a new SharePoint page called Finance Hub, the page I want the business to treat as the front door for numbers.

1. Open the page and select Edit.
2. Select the + to add a web part and search for Power BI.
3. Select Add content in the web part.
4. Choose Enter a URL and paste the link you copied. You can browse workspaces here instead, but the link is what carries the Copilot setting, so paste the link.
5. Set the display ratio. I left mine at 16:9.
6. Pick the default report page. Mine opens on Executive Summary, which is what I want somebody landing cold to see first.

Check for the Copilot button before you publish

Before you publish the page, look at the report toolbar for the Copilot button. It being there is the whole point of the exercise. If it’s missing, go back, regenerate the link with the box ticked and re-embed.

Click it once while you’re still in edit mode. The pane opens. Then publish.

The two Copilot buttons on the page

Tell your audience this before they start, because Microsoft’s layout invites the mistake.

A SharePoint page has its own Copilot button, the Microsoft 365 one. The embedded report has a different Copilot button that belongs to Power BI. Only the Power BI one can answer questions about your report. They sit on the same screen and they look related.

Put one sentence about it in the message you send with the link. It saves you a week of people saying the dashboard’s AI doesn’t know anything about the dashboard.

What people can ask it

Once the page is live, put the report in full screen. That’s the view to show your business partners: the dashboard fills the window and Copilot sits on the right.

I started with the question the report was built to answer.

Which locations missed their revenue budget in the first half of 2026, and by how much?

None did. All seven stores came in ahead, and it listed each variance, from Upper West Side at +$5,605 to Hell’s Kitchen at +$142,768.

Two things came back with the answer, and both matter more than the number. Every answer carries a citation to the table it came from. And How Copilot arrived at this expands to show the query it ran. For finance that’s the difference between a chatbot and a tool you’d put in front of a business partner, because you can check its work without leaving the page.

Then I asked for something the dashboard doesn’t contain.

Show that as a chart, sorted from biggest miss to smallest.

There were no misses, so it sorted from smallest positive variance to largest and said so. The chart exists nowhere in the report. Copilot built it from the model and kept the report’s formatting, and Expand view opens it full size. The person asking never opens Power BI and still leaves with the picture they wanted.

It follows you around the report, too. I flipped to the Cash & Treasury page and asked about that data.

How many days was Astoria's operating checking account overdrawn in January 2026, and what was the lowest balance?

It came back with nine days and a lowest daily balance of $615,673, both cited. Those two numbers don’t sit comfortably together, and that’s exactly the moment to open How Copilot arrived at this and see which measure it used for each before anybody forwards it.

Questions the dashboard was never built to answer

A reporting dashboard holds what happened. Mine doesn’t hold a forecast. So I asked a forward-looking question anyway.

Based on the trend so far, which stores are at risk of missing budget in the second half of the year?

Copilot asked before it answered. It said it could only work from actuals and budget, with no forecasting, and asked how I wanted at risk defined. I picked stores that had missed budget in the most months so far. Five stores had missed monthly revenue budget in 3 of 6 months, Park Slope in one, and Long Island City in none.

Treat it as a read of the trend with the working shown, and don’t sell it as a forecast. It’s also the question that would otherwise have landed in your inbox.

The second one finance people underrate. My model includes the monthly commentary the store managers write, so Copilot can read it.

What did the Astoria store manager say about January 2026?

Labor broadly in line with minor overtime, operating expenses up on equipment maintenance and small repairs, and sales below the prior month on a dip in local foot traffic. That’s the explanation behind the variance, which is what most questions in your inbox are really asking for.

If your commentary lives in a spreadsheet nobody loads into the model, change that before you do any of this. It’s the most useful table you can add for a finance audience, and if writing it is the bottleneck you can automate your Power BI commentary first.

Teach it how your finance team answers

Out of the box, Copilot answers like a competent stranger. I asked which stores were behind budget and got a correct short list of differences. Correct, and not how anybody in finance would present it.

You fix that once, on the semantic model, and every embed and every viewer picks it up.

1. From the report, go to Edit, then open the semantic model.
2. Select Prep data for AI on the ribbon. You get three tools: simplify the data schema, verified answers and add AI instructions.
3. Open Add AI instructions. It’s a plain text box for business context. Mine already held the basics: F9 Coffee Co. is a seven-store specialty coffee chain in New York City, the fiscal year is the calendar year, and the monthly close finishes on workday 5.
4. Add a rule for how answers should be presented, give it a section name and select Apply.

The instruction I added:

When a viewer asks about budget performance, always show actual, budget, and the variance in dollars and percent, sorted from biggest miss to smallest.

Then I went back to the SharePoint page and asked the same question. Microsoft’s Prep data for AI documentation says changes can take a few minutes to reach Copilot, and the feature is still in preview.

The numbers stayed put, because the data did. The layout followed the instruction. Every store now came back with actual, budget, variance in dollars and variance in percent, sorted the way I asked. Same query, same filters, organized the way I told it to.

That’s the loop worth building a habit around. Anything you catch yourself correcting in an answer goes into the instructions as a sentence, once, and nobody has to correct it again. The same prepped model also feeds a Fabric data agent if you want a chat window that sits across more than one source.

What you want	Where it lives	Who it affects
Copilot on the page at all	Turn on Copilot checkbox in the embed dialog	Everyone opening that page
Which measures to use and how to present them	AI instructions on the semantic model	Every viewer, every embed
A known-good answer to a common question	Verified answers on the semantic model	Every viewer, every embed
Fewer fields for Copilot to consider	Simplify the data schema	Answer quality everywhere

Common issues

The Copilot button is missing from my embedded report

The link was generated without Turn on Copilot ticked. Regenerate it from File, Embed report, SharePoint Online with the box ticked, and replace the link in the web part. Old intranet embeds predate the setting, so they all need this.

Copilot works in the Power BI service but not on the page

Check that the workspace sits on a paid Fabric or Premium capacity and not a trial. If you bought or scaled the capacity today, Microsoft says it can take up to 24 hours for Copilot to recognize it, so give it a day before you assume the embed is broken.

The SharePoint Copilot button doesn’t know anything about my dashboard

That’s the Microsoft 365 Copilot button. Use the one inside the embedded report’s toolbar.

My viewers can’t open the report

SharePoint access and Power BI access are separate. Adding the report to a page doesn’t share it. Share it in Power BI with the people who need it, and on a capacity below F64, check they have a Pro license.

What it doesn’t do

It answers from the semantic model, so anything outside the model is outside the answers. A forecast isn’t in there, and neither is the reason behind a variance unless the commentary is loaded.

It’s also an internal pattern. It works because each viewer signs in as themselves. Reports embedded for external customers through your own application work differently, and Microsoft has said it has no plans to bring the Copilot chat to that setup.

And the answers aren’t deterministic. Ask the same question twice and the wording can change. That’s why the citations and the query view matter. Financial Executives International published a framework in June 2026 for AI inside financial reporting controls, and a human in the loop is one of its four control approaches. A Copilot answer about budget is a draft until somebody in finance has looked at how it got there.

Where to put this first

Pick the page people already open. For most finance teams that’s a SharePoint site the leadership team uses every week, not a new portal you have to teach anyone to visit. If you’ve already built an automated CFO dashboard, that’s the report to start with.

Put it on the page, tick Turn on Copilot, tell people which button to click, and add one instruction a week to the model for the first month, based on how people phrase their questions. By the end of that month you’ll know which questions the business asks when it doesn’t have to ask you.

The prompts and templates I use on builds like this are in the free AI Library. For the wider picture of where this fits, the Copilot for finance hub covers the rest of Microsoft’s Copilot tools and AI in finance covers the whole stack.