Power BI Pro vs Premium Per User: Right-Sizing Before You Renew

Power BI is the add-on nobody budgets for properly. It arrives one analyst at a time, then a department, then someone decides it's simpler to give everyone Premium Per User. In April 2025 Microsoft raised Pro from $10 to $14/user/month and Premium Per User (PPU) from $20 to $24, so a line item that used to be rounding error now deserves the same scrutiny as the E3 vs E5 decision.

The good news: Power BI licensing has fewer rules than most of Microsoft 365, and the waste falls into a handful of predictable patterns.

Who actually needs a paid license

Three rules cover almost every case:

• Building reports is free. Power BI Desktop costs nothing. So does the Free license, which gives a user their own My workspace and nothing else. Nobody needs Pro to author a report on their own laptop.
• Sharing and viewing shared content needs Pro. The moment a report lives in a shared workspace or an app, both the person who publishes it and every person who opens it need Pro (or PPU). A viewer is not a free seat unless the content sits on a large enough capacity (see below).
• PPU content needs PPU on both ends. If a workspace runs on Premium Per User, everyone who consumes content from it needs PPU, including people who only look at a dashboard once a week. Pro holders can't open it.

That third rule is where most of the money goes.

The price ladder

• Free — $0. Desktop authoring and personal use.
• Pro — $14/user/month. Publish, share, and view shared content. Models up to 1 GB, 8 scheduled refreshes a day. Included in Microsoft 365 E5 and Office 365 E5.
• Premium Per User — $24/user/month. Models up to 100 GB, 48 refreshes a day, XMLA read/write endpoint and the other Premium features, licensed per person.
• Fabric capacity (F64 and up) — ~$5,000/month on a one-year reservation, ~$8,400 pay-as-you-go. Content on F64 or larger can be viewed by users on the Free license. Report authors and publishers still need Pro.

Five places the Power BI bill goes wrong

1. Paying for Pro on top of E5

E5 includes Power BI Pro. Tenants that bought standalone Pro for their analysts years ago and later moved those people to E5 often keep both assignments. Nothing errors. The standalone seat just renews.

How to check: intersect your E5 (or Office 365 E5) assignments with your standalone Power BI Pro assignments. Every user on both lists is a zero-risk removal. It's the same double-pay we found in Teams Phone, and it hides for the same reason: the user notices nothing.

2. Pro for people who never open a report

Someone needed a dashboard for a board paper in 2024. They got Pro. The board paper went out; the license stayed. Pro seats accumulate like this because they are granted for a task and never reviewed when the task ends. That's license drift in its purest form.

How to check: the Power BI activity log (Admin portal → Audit logs, or the admin activityevents API) records every view, edit, and export per user. List Pro holders with no view events in 90 days. The catch: the activity API only reaches back 30 days, so a 90-day answer means you've been collecting it for 90 days. The same rule we covered in how to read the usage reports applies here: start collecting before you need the answer.

3. PPU for everyone because one workspace needed it

This is the expensive one. One team outgrew the 1 GB model limit or needed hourly refreshes. The workspace was moved to PPU. Suddenly everyone who viewed its reports needed PPU too, and the path of least resistance was to upgrade the whole Pro population.

Most of those people are consuming reports that would run fine on Pro. The fix is structural, not a licensing trick: keep the heavy model in its own PPU workspace and publish the everyday reports from a Pro workspace. Then only the people who genuinely use the big model need PPU.

A worked example for a 150-person firm that went PPU across the board:

• Before: 150 × $24 = $3,600/month.
• After: 12 analysts plus the 30 people who actually use the large model stay on PPU (42 × $24 = $1,008). 60 people who view the everyday reports move to Pro (60 × $14 = $840). 48 people who haven't opened a report in 90 days lose the license entirely.
• Result: $1,848/month, a saving of $1,752/month (about $21,000 a year) with no one losing access to anything they use.

How to check: in the Admin portal, list workspaces by license mode. For each PPU workspace, ask what Premium feature it actually uses. If the answer is "none, it just ended up there", move it back to Pro.

4. Seats IT didn't buy

Power BI is one of the products where users can start a paid trial or make a self-service purchase with their own card. Trials expire into requests for a "real" license; self-service subscriptions turn up on expense reports, outside your Microsoft agreement and outside anyone's audit.

How to check: Microsoft 365 admin center → Billing → Your products shows self-service purchases made in your tenant. If you want every seat to go through IT, you can turn self-service purchase and trials off per product with the MSCommerce PowerShell module. Decide the policy deliberately. Blocking trials also blocks the analyst who would have found Power BI useful.

5. Departed authors

When a report author leaves, their Pro license is usually caught by the disabled-accounts check. The problem is what they owned: scheduled refreshes run under the owner's credentials and start failing, and nobody notices until a dashboard goes stale.

How to check: before removing a departed author's Pro seat, transfer ownership of their datasets and refresh credentials to a current owner. Then reclaim the seat. The license is the easy part; the data plumbing is what makes people nervous about touching Power BI at all.

When capacity starts to make sense

Fabric capacity pays off when you have a large population of people who only view. The arithmetic is simple:

• F64 at ~$5,000/month is the price of about 357 Pro seats, or about 208 PPU seats.
• Authors and publishers still need Pro on capacity, so only count viewers.

Below a few hundred viewers, per-user licensing is cheaper, which covers most SMB tenants. If a vendor is pitching you capacity with fewer viewers than that, ask them to show the numbers.

A Power BI audit you can run in an afternoon

1. Export license assignments for Power BI Pro, PPU, and E5.
2. Remove standalone Pro from E5 holders.
3. Pull 90 days of activity (or start collecting now if you don't have it) and list paid seats with no views.
4. List PPU workspaces and the Premium feature each one needs. Move the rest to Pro.
5. Re-license by role: builders of large models on PPU, their audience on PPU, everyone else who views shared reports on Pro, non-users on Free.
6. Check self-service purchases and trials and decide your policy.
7. Transfer ownership before reclaiming any departed author's seat.

Add this to the rest of your pre-renewal license audit. Power BI seats renew with everything else, so the week before renewal is when the savings are real.

SeatPrune syncs Power BI activity alongside your other Microsoft 365 usage data and flags Pro and PPU seats with no activity in the evidence window, priced in $/month. The workspace restructure is still a human decision. Knowing which seats to look at first isn't.

The Power BI question isn't "Pro or PPU?". It's "what does this person do with Power BI?" Build big models: PPU. Look at shared reports: Pro. Haven't opened a report since the last renewal: Free.