Power BI licensing costs: what you actually pay

Power BI costs €12.10 per user per month for a Pro license and €20.80 for Premium Per User, both excluding VAT and on annual billing. Building in Power BI Desktop is free, you only start paying the moment you want to share something.

That is the price list. What you end up spending on Power BI licenses is not on it, because that depends on a split almost nobody works out in advance: how many people are going to build reports themselves, and how many only want to look. Skip that count and you order everyone the heaviest option one person once needed, and a license too many never throws an error.

Something else is missing from that price list. A license buys access, not a better decision. There are plenty of organizations where every employee can log in, every department has its own report, and where someone in the monthly meeting still says it feels about right. What you pay is one question, what you get back is another. Both are covered below: first the license types and the rates, then the sum that decides which mix is cheapest for your organization, and finally what lands on top of the license invoice.

Which Power BI licenses exist?

Five types, and the first four build on each other:

• Free. Power BI Desktop is a free download and you can build fully featured reports in it. Sharing is out: what you build stays on your own laptop or in your personal workspace.
• Power BI Pro. The license that lets you publish, share and collaborate in a shared workspace. For the vast majority of SMEs this is the entire licensing question.
• Premium Per User (PPU). Everything in Pro, plus the heavier engineering: a model of up to 100 GB instead of 1 GB, 48 refreshes a day instead of 8, and XMLA endpoint access for anyone who wants to read the model from outside.
• Fabric capacity. Here you buy compute rather than users, per month, for the whole organization. This is what used to be called Power BI Premium per capacity. Microsoft no longer sells those P options to new customers and points everyone to the F capacities of Microsoft Fabric.
• Power BI Embedded. Not a license for your own staff but for your own software: you build reports into an application you sell to customers. If that application settles up with Power BI itself, your end users need no license at all. It is the one type that does not fit the ladder above, and also the one you never need if you only report internally.

What comparisons nearly always get wrong: PPU and capacity are not two sizes of the same thing. PPU is a feature set attached to a person, capacity is compute you put workspaces on. An organization holding only PPU licenses therefore has no Fabric environment, however many of them you line up. Microsoft sets out the rules per license type in its own documentation, and that is also where you check them before signing.

What does Power BI cost per user?

Pro sits at €12.10 per user per month, PPU at €20.80, both excluding VAT and on annual billing. Microsoft raised both rates in April 2025, and these are the amounts that have been on its price page for the Netherlands ever since.

The €8.70 difference does not buy extra dashboards. It buys room and speed: a larger data model and more frequent refreshes. That matters if you work with millions of rows, or if your figures have to move with your operation several times a day. Refresh once a night with a model that fits comfortably inside a gigabyte, and PPU is paying for room that stays empty.

Before you order anything extra, look at the Microsoft agreement you already have. Power BI Pro is included in Microsoft 365 E5 and Office 365 E5, and those licenses only need assigning. On E3 or lower you buy Pro separately. This is the cheapest saving in the whole article, and it costs you half an hour in the admin portal.

Power BI Pro vs Premium: what are you buying?

This is the comparison everyone gets wrong, because Power BI Premium is not a better version of Pro. It is the same Power BI with different limits around it. Everything you can build in Pro you can build in Premium, and nothing in Premium makes a report better on the substance.

Read that table top to bottom and you see where the real jump sits: not between Pro and PPU, but between PPU and capacity. PPU raises the limits for one person, capacity changes who is allowed to look and where the reports are allowed to run. Microsoft itself uses 250 users as the rule of thumb: if you need Premium features for fewer people than that, PPU works out cheaper than buying a capacity.

So the practical question is not whether you want Pro or Premium, but whether anyone in your organization is running into one of those limits. Usually the answer is no. A financial model holding three years of ledger stays well under a gigabyte, and figures refreshed once a night are still current enough to steer on the next morning.

Who is allowed to buy Power BI licenses?

Not everyone, which is why the order stalls on permissions more often than on budget. To buy or assign licenses you need the billing administrator role in Microsoft 365. That same person handles the per-user assignment afterwards, in the Microsoft 365 admin center or through Microsoft Entra.

There is also a switch running that almost nobody knows about: self-service purchase. Leave it on and a colleague who hits a share button simply buys themselves a Pro license, on their own credit card, outside your procurement process. Convenient, until you are looking at twelve separate subscriptions with twelve separate billing dates on the invoice. Microsoft describes how to set up that purchasing and assignment, including how to turn self-service off.

If you want to try it first there are two routes, and they differ more than the names suggest. A Power BI Pro trial runs 30 days and covers up to 25 licenses. A Fabric trial runs 60 days and gives you a trial capacity that behaves like an F64, including 1 TB of storage. That second one is the only way to see, without paying, how it works when viewers no longer need a license of their own.

One thing to know up front: a license that expires does not stop overnight. A volume license has a 90-day grace period, a license you bought directly has 30 days. A trial has no grace period at all, and access to paid features stops the day the trial ends.

Which license fits which role?

The number of licenses you need does not follow from your headcount, it follows from what those people do with the figures. Four roles cover nearly every organization:

• Whoever builds. Anyone creating reports and publishing them to a shared workspace needs Pro as a minimum. Building in Desktop is free, publishing is not.
• Whoever looks. A team lead who opens the dashboard and filters it needs the same Power BI Pro license as the person who built it, as long as you sit below F64. This is the role most organizations underestimate in their budget.
• Whoever builds heavy models. If you work with datasets that no longer fit in a gigabyte, or the figures have to refresh several times a day, only that person gets PPU. Not the whole department.
• Whoever administers. Admin rights on your Microsoft tenant are a role, not a license. You do not buy them, you assign them, and you put them with your own people.

There is one group outside those four that regularly gets forgotten: people who are not on your payroll. To let your accountant or a franchisee look along, the person sharing needs a Pro or PPU license and so does the guest, unless the report sits on a capacity of F64 or larger. Sharing a monthly report outside the company is not a free action.

Count those roles literally, with names attached, before you order. That is the difference between a licensing line that adds up and one that quietly renews every year for people who never open the report.

Worked example: 25 employees

Take an organization of 25 people. Three colleagues build and maintain the reports, the other 22 look along: the board, the team leads, a few people in finance and sales.

The temptation is to find a cheaper viewing license for those 22. It does not exist. In a shared workspace, someone who only looks needs a Pro license as well, unless the reports sit on a Fabric capacity of F64 or larger. So not every user needs a different license type, but every user needs a license.

That makes the sum 25 times €12.10, or €302.50 a month and €3,630 a year. That is the entire licensing line for an organization this size. Put it next to the hours one hand-assembled monthly financial report costs and the discussion about license fees is usually over in two minutes.

Grow to 60 people and the bill grows neatly along to €8,712 a year. Linear, predictable, and still well under any alternative. Only much further along that line does the question of whether you still want to pay per user get interesting.

When does Fabric capacity get cheaper?

F64 is where it tips. From that capacity upward, colleagues with a free license are allowed to view the reports, provided they hold the viewer role on the workspace. Anything below F64 falls back on the ordinary rule: looking costs a Pro license. For anyone who still knows the old names: F64 is the successor to P1, with the same eight virtual cores underneath.

In West Europe an F64 capacity costs €5,364 a month on an annual commitment, and without that commitment you pay by the hour, which puts the bill roughly 41 percent higher. Divide that €5,364 by the €12.10 of a Pro license and you have the tipping point: 443 viewers. Below that, Pro for everyone is cheaper. And whoever builds needs a Pro license either way, capacity or no capacity.

So for most SMEs, buying a capacity so fifty colleagues can look along makes about as much sense as buying a truck because you help a friend move twice a year.

There is one situation where the sum works at smaller numbers: when you genuinely use that capacity for the rest of Fabric, with a lakehouse, pipelines and notebooks on it. At that point you are not buying a Power BI license anymore, you are buying a data platform. That is a different decision, with a different case behind it.

The costs that never reach your license invoice

The license is rarely the biggest line. What comes with it in practice:

• A gateway. If your source systems sit on your own server instead of in the cloud, you need a machine that keeps the connection open. That machine runs, gets patched, and occasionally falls over.
• Windows. Power BI Desktop only runs on Windows. If your finance team works on Macs, a virtual machine or a second laptop comes first, before anything gets built.
• Maintenance on the model. Every new kpi, every changed definition and every source that shifts a field costs work on the data model underneath. On a clean model those are hours, on a model that grew organically they are days.
• Training. A license teaches nobody how to read a report. Budget half a day per user to learn filtering and drilling down, and considerably more for the colleagues who will build.
• Changes at your supplier. Have every adjustment invoiced separately and after a year that is often a multiple of your Power BI costs. What the build itself costs, and where that range comes from, is worked out in our article on getting a Power BI dashboard built.

Of all those lines, maintenance on the model is the only one you can really steer without touching your licenses. A clean data model makes a new kpi a matter of hours, a model nobody can follow anymore turns it into a project.

Whose environment do your licenses live in?

One question rarely comes up during a proposal meeting: whose name will the licenses, the workspaces and the files be in. The answer decides what you can still do two years from now.

There are plenty of BI suppliers who deliver a tidy dashboard and quietly leave the environment sitting in their own tenant. That works fine, right up to the moment you want to switch or take over management yourself. Then it turns out you did not pay for a dashboard, you paid for access to a dashboard. A supplier who sets it up that way is not selling you reporting, they are selling you dependency.

So three things get settled before the first license is bought: the licenses and workspaces live in your own Microsoft tenant, at least two of your own people hold admin rights, and the source files of the reports are in your keeping, not only with whoever built them. Settling that costs you nothing at the time. Not having settled it costs you the migration of your entire environment later. That is exactly why our four-step approach deliberately hands management over to your own team.

---

Are you paying for a license, or for access to your own figures? Want to know which license mix works out cheapest for your organization? Get in touch, and we’ll run the sum on your own numbers.

Frequently asked questions