Power BI Copilot needs paid Fabric capacity (F2 or higher) or Power BI Premium (P1 or higher). Pro at $14 per user a month, or Premium Per User, is not enough, and trial capacities do not count. F2 is a few hundred dollars a month if it runs all month, less if you pause it.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThat makes the real question a business one: is Copilot worth a monthly capacity bill that is many times the cost of your Power BI licences? For a firm with four or five report viewers, the usual answer is "only if you already have a reason to buy capacity". The sums, the options for keeping the bill small and the checks to run before buying are below.
What does Microsoft say Copilot in Power BI requires?
Copilot in Power BI requires a paid Fabric capacity of F2 or higher, or Power BI Premium of P1 or higher, in a supported region, with the Copilot tenant setting switched on.
Microsoft's Copilot overview for Power BI (updated in August 2026) opens with a short requirements table. In plain words:
- Capacity: a paid Fabric capacity of F2 or higher, or Power BI Premium of P1 or higher. Trial capacities and free SKUs are not supported.
- Admin setting: the tenant setting "Users can use Copilot and other features powered by Azure OpenAI" must be on. It is on by default, but your admin may have changed it.
- Region: the capacity must sit in a supported region. Sovereign clouds are not supported.
- Licences: the same page says a Pro or Premium Per User licence alone is not sufficient, because Copilot requires organisational capacity.
Two more points save a bad purchase. For Copilot inside reports, the report must live in a workspace linked to the capacity, and anyone writing in Power BI Desktop needs write access to a workspace on paid capacity. And when you buy or scale up, Microsoft warns it can take up to 24 hours before Copilot recognises the change.
How much do the pieces of a Power BI Copilot bill cost?
A Power BI Copilot bill is the Fabric F2 capacity, about $0.36 an hour or roughly $263 for a month left running, plus $14 per user a month for each Pro licence.
Three costs matter to a small business. Prices below are list prices from Microsoft as of November 2026; the Fabric hourly rate is Microsoft's launch example figure for one region and varies by region, so confirm yours in Azure's pricing calculator before you commit.
| Item | List price | What it does for Copilot |
|---|---|---|
| Power BI Pro | $14 per user a month, paid yearly | Lets a person publish and share reports; not enough for Copilot alone |
| Premium Per User | $24 per user a month, paid yearly | Richer features per person; not enough for Copilot alone |
| Fabric F2 capacity, pay as you go | About $0.36 an hour, roughly $263 for a month left running | The cheapest capacity that supports Copilot |
| Fabric capacity reservation | Saves about 40% against pay as you go, billed as an annual commitment | Cheaper only if you will use the capacity all year |
Microsoft's pricing page lists Fabric reservations as an annual purchase that saves 40.5% against pay as you go, and notes that pay-as-you-go capacity can be scaled or paused. Azure's page shows reservations at about 41% off. Either way, plan on roughly 40%.
A photography studio with five users: the main worked example
Say a photography studio has five people who look at reports: two partners, an office manager and two photographers who check booking numbers. They already use Power BI to show bookings, payments and print orders, and a partner wants to ask questions in plain English.
- Licences today: five Pro licences at $14 = $70 a month.
- Copilot, pay as you go, left running all month: $0.36 × 730 hours = about $262.80, so the monthly bill becomes $70 + $262.80 = $332.80. Over a year that is about $3,994.
- Copilot, reserved for the year: about 40% off $262.80 gives roughly $156 a month, so $70 + $156 = $226 a month, or about $2,711 over the year, with the commitment fixed.
- Copilot, paused outside working hours: if the capacity runs 10 hours on 22 working days, that is 220 hours × $0.36 = $79.20, so $70 + $79.20 = $149.20. This only works if the reports on that capacity are not needed outside those hours, which you must check, because content on a paused capacity is unavailable until it resumes.
So for this studio, Copilot costs between roughly $80 and $263 a month extra, depending on how it is run, and the licence line is the smaller part. Ask what the partner would do with a Copilot answer that she cannot do by clicking a slicer: if the answer is "save ten minutes a week", the capacity does not pay for itself.
Do you still need Pro licences if you buy Fabric F2?
Yes, Pro licences are still needed on F2, because Microsoft's pricing page says viewers can consume content without per-user licences only at F64 and above. Below that, people who view reports in a workspace need their own licences. For a small firm on F2, assume you keep paying $14 a user for anyone who opens a shared report.
This matters for the cost of expanding. Adding a sixth viewer costs another $14, but the capacity bill does not change. Adding a sixth viewer does change who is competing for the capacity, which leads to the next point.
How does Copilot use up Fabric capacity?
Copilot uses Fabric capacity through token consumption, measured in capacity units and processed as background operations, which smooths demand. Fabric bills separately for anything Copilot triggers, such as DAX queries, data refreshes or email subscriptions. A capacity admin can open the Fabric Capacity Metrics app, go to the Item history page and filter on the Copilot in Fabric operation to see a 30-day breakdown.
In practice that means three habits keep the capacity small and calm:
- Keep reports on a modest semantic model. A large model with many refreshes eats capacity without any Copilot involved.
- Avoid scheduling many refreshes at the same minute, because refreshes use the same capacity.
- Look at the Copilot operation in the metrics app after a fortnight. If it is a thin sliver, you are paying for an F2 you barely use.
Is Copilot in Excel a cheaper route for a small firm?
Copilot in Excel can cost less for a small firm whose real need is a question answered from a workbook rather than a modelled report, but the two products are not a like-for-like swap. Microsoft 365 Copilot Business is listed on Microsoft's Copilot Business page at $21 per user a month on an annual commitment, with a promotional $18 for the first year on annual billing for purchases made between 1 July and 31 December 2026 (it needs an eligible Microsoft 365 business plan and is not available on trial subscriptions). Paying monthly on that annual commitment costs 5% more (about $22.05), and the month-to-month option that Microsoft partners sell costs $25.20, according to Microsoft's March 2026 partner pricing; Microsoft's own pricing page lists only the annual price (checked 20 November 2026). For five users that is about $105 a month at list, or $90 on the promotion, with no capacity to manage.
That is not a like-for-like swap. Copilot in Excel works on a workbook that someone prepared, while Copilot in Power BI works on a semantic model with shared definitions. The comparison for a dashboard is in Power BI vs Excel with Copilot for a small business dashboard, and the wider pricing picture is in Power BI Copilot pricing: what a small business must buy first.
What should you check before buying Fabric capacity for Copilot?
Before buying Fabric capacity for Copilot, check six things: the admin setting, the capacity region, the workspace link, write access, the data and who owns the bill. Work down the list with your admin; it is the one worth printing.
- Is the admin setting on? Ask the Fabric admin to confirm "Users can use Copilot and other features powered by Azure OpenAI" is enabled at tenant level. For the standalone experience (in preview as of Microsoft's August 2026 page), another tenant setting for a cross-item Copilot also needs switching on.
- Is the capacity region supported? Check the region list before choosing where to create the capacity. If it is outside the region where your data is held, Microsoft says an extra tenant setting about data being processed outside the tenant's geographic region may be needed.
- Is the workspace attached? The report must sit in a workspace linked to the capacity. A common slip is buying F2 and leaving the workspace on Pro.
- Who has write access? Report authors need write access to a workspace on paid capacity to use Copilot in Desktop.
- Can the data be prepared? Microsoft says Copilot works better on a semantic model prepared for AI and can misread an unprepared one.
- Who owns the capacity bill? Fabric capacity is bought through an Azure subscription or a partner, which is a different account from Microsoft 365. Make sure someone owns it and gets the invoice.
Why does Copilot answer wrongly on untidy data?
Copilot answers wrongly on untidy data because the AI charts the values in the model, not what the owner meant. A bookshop owner buys F2, switches Copilot on, and asks "which authors sold best last quarter?" Copilot answers with a chart that looks authoritative, but the model contains one sales table with the author in a free-text column that has "Smith, J", "J. Smith" and "J Smith" as separate values. The chart splits one author into three bars. The numbers are not wrong, the model is untidy.
The fix is on the data, not the AI. Clean the column first (see cleaning messy data), add a measure for revenue, and describe each field in plain words so Copilot has a guide. A $263 capacity bill does not rescue a messy model; it only makes the mess answer faster.
If tidying messy data in a spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
Three more small-firm sketches
A removals firm of twelve. The owner wants a weekly job-volume view for three supervisors. Three Pro licences ($42 a month) with a scheduled refresh already do this. Copilot would add the F2 bill for questions that the three supervisors ask rarely. Not worth it yet.
A florist with a shop and web orders. The owner is the only person who looks at reports. One Pro licence is $14 a month. Even a reserved F2 at about $156 is more than ten times that. The better route is an Excel workbook with Copilot, if she has the licence, or a plain pivot table.
A photography studio that already runs a Fabric capacity. A partner has bought F8 for a data project. Copilot then costs extra consumption on a capacity already paid for, and the marginal cost is low. This is the case where Copilot makes sense: the capacity bill is already sunk, so you only manage the usage.
The pattern across these is simple. If you do not already run capacity, Copilot in Power BI is a capacity decision first, a licence decision second. If you do, the extra bill is usage, and you watch it in the metrics app. If you want to talk through which of those you are, my AI implementation consultation covers it, and you can get in touch.
How do you test Copilot during one paid month?
Test Copilot fairly by setting the trial up in advance, before you buy F2 for a month, so the month is not wasted. Use questions you ask every week, in these shapes:
1. Summarise this report for a partner in five bullet points.
2. Which three products or services grew most this quarter against last?
3. Show monthly revenue as a column chart with a line for the target.
4. Why did revenue dip in [month]? List the visuals that explain it.
5. Create a measure for average booking value and add it to the table.
Score each answer on three counts: right number, right wording and time saved against doing it by hand. Keep a simple tally on paper. If fewer than half the answers are useful without fixing, or the time saved is under an hour a week, pause the capacity at the end of the month and note why.
What a pause does, and what to confirm first
Fabric's pay-as-you-go capacities can be paused with no usage commitment, according to Azure's pricing page. Pausing stops the hourly charge. It also means Copilot stops working, and reports hosted on that capacity may be unavailable until it resumes (Microsoft's capacity documentation explains the behaviour), which you should test on a Friday afternoon rather than discover on a Monday morning. A reservation is an annual purchase, so check how pausing affects what you pay before relying on it; that is one reason reservations suit constant use only.
The cleanest approach for a small firm is: start on pay as you go, pause when idle, measure for a month, and move to a reservation only when the metrics app shows steady use. That order keeps the cost of being wrong to one month of a few hundred dollars rather than a year-long commitment.
Preparing the model so the capacity earns its keep
Microsoft's own overview says Copilot can misinterpret an unprepared model and return generic or inaccurate results, so preparation is the cheapest part of the whole exercise and should happen before the capacity bill starts. A bookshop's model might need these changes, each taking minutes:
- Rename columns in plain words. "amt_gbp_net" becomes "Net sales". Copilot reads names, so "Net sales" is far likelier to be chosen for "how much did we sell".
- Hide what nobody should ask about. Hide internal keys and helper columns so Copilot does not offer them as answers.
- Add descriptions to measures. One sentence each: "Net sales: invoice total excluding tax, after discounts, by order date."
- Fix the date table. If "last quarter" is ambiguous because the model has no proper date table, Copilot guesses.
- Remove duplicates in categories. The "Smith, J" problem again.
Budget two to three hours for a small model. Do this before the paid month, so the month is spent judging Copilot rather than cleaning data on the meter.
The trial month scorecard, filled in
This is an illustrative scorecard for the photography studio after a paused-outside-hours month. The figures are invented to show the layout, not benchmarks.
| Question asked | Right number? | Usable wording? | Minutes saved |
|---|---|---|---|
| Summarise the bookings report for a partner | Yes | Needed light edit | 10 |
| Which package sold best in spring? | Yes | Yes | 5 |
| Why did print orders dip in June? | Partly: named the right visual, wrong cause | No | 0 |
| Add an average-booking-value measure | Yes after one correction | Yes | 15 |
| Chart revenue against target by month | Yes | Yes | 10 |
Five questions, four useful, 40 minutes saved in that sitting. If the studio asked questions like these six times a month, the saving is about four hours. At $149 a month (the paused option above), the capacity costs roughly $37 per hour saved. That figure is the thing to compare with the hourly cost of the partner's time. If the partner's time is worth more than $37 an hour and the savings are real, Copilot pays; if the questions dry up after the novelty, it does not.
Which option suits a small team?
A team with one or two report users and no capacity should stay on Pro or use Excel with Copilot; five to ten users who ask regular questions can try one paused month of F2.
| Your situation | Sensible move |
|---|---|
| One or two report users, no capacity | Stay on Pro or use Excel with Copilot; skip Fabric |
| Five to ten users, regular questions from non-analysts | One month of pay-as-you-go F2, paused out of hours, then decide |
| Already on Fabric or Premium for other work | Switch Copilot on and watch usage in the metrics app |
| Several hundred viewers who only read reports | Look at F64 and above, where viewers need no per-user licence |
| Not sure what you need | List your top five weekly questions first, then price the answer |
The F64 row is arithmetic, not advice for a small firm. At the same $0.36 an hour for two units, F64 would be about $8,400 a month if left running, which is the price of roughly 600 Pro licences, so it only makes sense when licence savings for a great many viewers outweigh it. Dashboards for a team that size are better discussed with a Microsoft partner or a consultant than guessed at in a table.
How to tell whether it was worth it
At the end of the trial month, put four numbers on one page: total extra bill, number of Copilot answers used without edits, minutes saved per week as best you can estimate, and any decision made differently because of an answer. Divide the extra bill by the hours saved. If one hour of someone's time costs less than that figure, the capacity is not paying for itself. If a single answer changed a pricing or hiring decision, that counts too, but write it down at the time rather than recall it later.
Power BI Copilot cost: questions small businesses ask
Can a Power BI Pro licence alone run Copilot?
No. Microsoft's documentation says a Power BI Pro or Premium Per User licence alone is not sufficient, because Copilot needs organisational capacity: a paid Fabric capacity at F2 or higher, or Power BI Premium at P1 or higher. Pro licences still matter, since people who build or share content in smaller capacities need them.
Does the Fabric free trial work for Copilot?
No. Microsoft's requirements table says trial capacities and free SKUs are not supported for Copilot in Power BI. You can trial Fabric for other things, but you cannot test Copilot that way. Judge Copilot on a short paid capacity, then pause or delete it.
How long after buying capacity does Copilot appear?
Up to 24 hours, according to Microsoft, which says it can take that long for Copilot to recognise new or scaled-up capacity. Buy the capacity the day before a demo or training session, not an hour before, and assign the workspace in advance.
Who switches Copilot on?
A Fabric or tenant administrator controls the setting called Users can use Copilot and other features powered by Azure OpenAI. Microsoft says it is on by default, but an admin may have turned it off. If you cannot find Copilot, ask your admin to check it before you buy anything.
How much does Power BI Copilot cost a small business a month?
On the page's worked example, a five-user studio pays $70 for Pro licences plus the F2 capacity: about $262.80 if it runs all month, about $156 reserved for the year, or about $79.20 if it runs 220 hours a month. These are list-price sums, and the Fabric hourly rate varies by region.
Does Power BI Copilot need F64?
No. F2 is the cheapest capacity that supports Copilot. F64 and above matters for a different reason: Microsoft's pricing page says viewers can consume content without per-user licences only at F64 and above, so on F2 you keep paying for Pro licences.
Further reads
- Can Copilot Build a Sales Dashboard in Excel? What It Gets Wrong — Build a one-page sales view in Excel with Copilot instead.
- Claude for Microsoft 365 vs Copilot Business: Which Add-In Fits Best? — Another AI add-in decision for Microsoft 365 firms.
- Copilot in Excel: What It Can and Can't Do With Your Numbers — What Copilot in Excel does with your numbers.
- Power BI for Accountants: Client Dashboards and Copilot Limits — Choose client metrics, reconcile the source and control sharing before paying for Copilot capacity or promising live dashboards.
Browse all AI-for-business tutorials
Sources: Microsoft Learn, Copilot for Power BI overview (requirements, updated August 2026); Microsoft Power BI pricing page; Microsoft Fabric pricing and capacity announcement, checked November 2026.
