Power BI Copilot Licensing Requirements

The short version of the Power BI Copilot licensing requirements: Copilot runs on organizational capacity. Microsoft's own documentation is blunt about it — a Power BI Pro or Premium Per User license alone is not sufficient. The content, or the person using Copilot, has to be backed by a paid Fabric capacity at F2 or above, or a Power BI Premium capacity at P1 or above. Trial capacities and free SKUs are not supported. Everything else on this page is the detail underneath that rule: which SKU to buy, where the F64 line bites, what Copilot consumes once it is switched on, and how a team of five or fifty can get access without moving every workspace it owns.

This page is deliberately narrow. It covers licensing and capacity only. If you are deciding whether to roll Copilot out across Microsoft 365 at all — the permission cleanup, the first three use cases, the training and the adoption measurement — that is the subject of our Copilot rollout for small business guide, and it is worth reading first if the decision is still open. If you are still on a Power BI Premium P SKU and the renewal date is what brought you here, read Power BI Premium to Fabric migration alongside this one.

Why a Pro or PPU license does not switch Copilot on

Copilot in Power BI is billed as compute against a capacity, not as a feature of a user license. Pro and Premium Per User workspaces do not directly support Copilot. To use it, the report or model has to live in a workspace on an F2-or-larger Fabric capacity or a P1-or-larger Premium capacity — or the user has to be assigned to a Fabric Copilot capacity, covered below.

This catches teams out because Premium Per User sounds like it should include the premium features. For most of Power BI it does: larger models, more frequent refresh, deployment pipelines. Copilot is the exception, because every prompt consumes capacity units and a per-user license has no capacity to charge them to. The same logic is why trial capacities are excluded — Microsoft states that the Azure OpenAI Service behind Copilot is not available on trial SKUs.

Three tenant-level conditions sit on top of the capacity. The admin setting Users can use Copilot and other features powered by Azure OpenAI must be on; it is enabled by default for tenants with paid Fabric capacity, but an administrator may have turned it off. The capacity must be in a supported region, and if it sits outside the United States or the EU data boundary, a second setting allowing data to be processed outside the capacity's geography must also be enabled. And Copilot is not yet supported in sovereign clouds.

• Capacity — paid Fabric F2 or higher, or Power BI Premium P1 or higher; no trial or free SKUs
• Tenant setting — Copilot and Azure OpenAI features enabled, ideally scoped to a security group rather than the whole tenant
• Region — a supported Fabric region, with cross-geo processing enabled if you are outside the US or EU data boundary
• Timing — after buying or scaling a capacity, Microsoft notes it can take up to 24 hours for Copilot to become available

Which Fabric SKUs unlock Copilot, and where F64 matters

Every paid F SKU from F2 upward can run Copilot in Power BI, as can every P SKU from P1 upward. F64 is not a Copilot threshold. It is a viewer-licensing threshold, and it changes the per-user bill far more than it changes what Copilot can do.

On F64 and larger, people holding only a free license can open content shared with them as viewers. On F2 through F32, every viewer needs a Pro or Premium Per User license of their own. For Copilot that distinction shows up in two places. Anyone asking Copilot questions about a report needs at least read access to it; anyone asking Copilot to build a report or add a narrative visual needs edit access to the workspace or build access to the semantic model. A small team where everyone who opens a report already holds Pro loses nothing by sitting below F64. A team that wants to hand reports to a large free-licensed audience is making an F64 decision, and Copilot simply comes along with it.

F128 and above buy more compute, not more Copilot features. Move up when the Capacity Metrics app shows sustained pressure, not because a larger SKU sounds like it should unlock something. The experiences themselves — the Copilot pane on reports, report creation, DAX query help, the standalone Copilot and app-scoped Copilot — carry the same requirements on every supported SKU, with the standalone and app experiences still in preview at the time of writing.

What a Fabric Copilot capacity changes for a small team

A Fabric Copilot capacity is an F2-or-larger (or P1-or-larger) capacity that an administrator designates to collect the Copilot usage of a named group of users. Once someone is assigned to it, their Copilot usage in Power BI Desktop and in Pro and Premium Per User workspaces is billed there, without moving their content onto that capacity.

For a small business that is usually the most important line in the documentation. It means the reporting estate can stay where it is — in Pro workspaces the team already pays for — while a small capacity is bought specifically to carry Copilot for the people who will use it. It also gives you one place to watch Copilot consumption instead of having it spread across every capacity that happens to hold content.

The constraints are specific and worth checking before you design around it. The Fabric Copilot capacity must be in the tenant's home region. Each user can belong to only one; if someone is assigned to several, the most recently created one takes their usage. Workspaces in the Embedded license mode are not supported. And it does not cover Fabric AI functions. The standalone Copilot experience in Power BI also relies on either a Fabric Copilot capacity or a workspace on a Copilot-enabled capacity to bill against — without one of those, a user cannot open it at all.

How Copilot consumption is billed on the capacity

Copilot usage is metered in capacity units and driven by token consumption. Fabric processes it as a background operation, which smooths the load rather than spiking it, and it draws on the same capacity your refreshes and report queries use. Any downstream work Copilot triggers — a DAX query, a refresh, an email subscription — is billed separately through its normal path.

The practical consequence is that Copilot has no separate invoice line to watch. It competes with everything else on the capacity, so an enthusiastic week of prompting can push a small capacity toward throttling and slow the reports people depend on. Microsoft's own guidance warns that enabling Copilot for the entire tenant without planning can raise capacity utilization. The control you have is scope: enable it for a security group, not the tenant, and watch the Copilot in Fabric operation in the Microsoft Fabric Capacity Metrics app, which breaks consumption down by report and semantic model over a 30-day window.

Copilot is also only as good as the semantic model it reads. Microsoft recommends that model owners prepare their data for AI before business users start asking questions — clear names, descriptions and relationships — because without that Copilot can misread the model and return generic or wrong answers. That preparation is modelling work, not licensing, and it is where most of the value is won or lost.

What it actually costs a small team to switch it on

Model the cost as three separate lines, because they land in different budgets. First, per-user licenses: Pro or Premium Per User for everyone who builds content, and — below F64 — for everyone who views it. Second, the capacity itself, billed through Azure, sized from measured consumption rather than from headcount. Third, the time to prepare the semantic models Copilot will read.

We do not quote Microsoft's per-seat or per-capacity figures on this page because they change and they vary by agreement; take them from Microsoft's current pricing pages or your reseller on the day you buy. What we can say is how the shape of the decision usually falls out. A team that already licenses everyone with Pro and only wants Copilot for its report builders and a few managers is typically looking at the smallest capacity that carries its measured Copilot load, designated as a Fabric Copilot capacity, with the content left where it is. A team that wants to reach a large free-licensed audience is making the F64 decision for viewer reasons first, and should cost it that way.

Two levers keep the Azure line honest. Pay-as-you-go capacity can be paused when it is genuinely idle and resized when the metrics justify it; a reservation lowers the rate for a capacity you know you will run all year. And the one cost nobody puts in the business case is your own people's time — deciding who gets access, preparing the models, and checking the answers before anyone relies on them. For a wider view of what a Power BI project costs end to end, see Power BI implementation cost for small business.

How we help you get the licensing right

Most licensing mistakes here are made once, at purchase, and then paid for monthly. We start from what you already own: the per-user licenses in the Microsoft 365 admin center, any existing capacity, where your workspaces sit, and who actually needs Copilot. From that we recommend the smallest setup that works, configure the tenant and capacity settings, and set up the monitoring so you can see what Copilot is costing from the first week.

Work is led by Edward Pinela, MBA, a principal consultant in business intelligence — the person who scopes it is the person who does it. For a bounded piece of work like this, Power BI Flex Support is usually the right vehicle: it starts at $2,500 for 20 hours at $100–$125 per hour, in prepaid blocks whose hours do not expire. If the capacity decision is part of a larger move onto Fabric, that belongs in a Microsoft Fabric implementation project with its own scope.

Further reading: Microsoft Learn — Copilot for Power BI overview and requirements.