Power BI Licences for Business Users - What You Actually Need to Pay For
The most common Power BI question we get from Australian organisations isn't about DAX or data models. It's "why can't Sarah open the report?" And the answer, about 80 per cent of the time, is licensing. Someone built a report, shared it, and the person on the other end hit a wall because nobody thought about what licence the viewer needs, only what licence the builder needs.
That distinction is the whole game. Power BI licensing is designed around two different people: the person who creates content and the person who consumes it. Microsoft's own docs call the second group "business users", and their article on licences and subscriptions for business users is written for exactly the person who's just been sent a report link and wants to know why it won't open. It's worth a read, but here's the version with the consulting scar tissue included.
The four things that matter
Ignore the marketing pages for a second. For a business user, there are really four licensing states you can be in:
Free licence. Anyone can get one. On its own, a free licence lets you use Power BI Desktop, publish to your own personal workspace, and look at your own content. What it does not do, by default, is let you view reports other people share with you. That surprises almost everyone. The free licence isn't a consumption licence, it's a sandbox licence.
Pro licence. Roughly $17 to $19 AUD per user per month depending on your agreement, and included in Microsoft 365 E5. Pro lets you share content, consume content shared by others, publish to shared workspaces, and use apps. If your organisation has no Premium or Fabric capacity, then everyone who touches shared content needs Pro. Author and viewer alike. This is the bit that makes finance departments wince when the user count hits four digits.
Premium Per User (PPU). Sits above Pro in price and adds the features that used to be capacity-only, like larger models, more frequent refreshes and paginated reports. The catch that bites people: PPU content can only be consumed by other PPU users. If one analyst upgrades to PPU and publishes to a PPU workspace, they've just locked out every Pro colleague. We've untangled exactly this mess at a mid-sized insurer where one enthusiastic analyst quietly moved the finance workspace to PPU and half the business lost access on a Monday morning.
Content hosted on capacity. This is where the free licence becomes genuinely useful. If your organisation has a Fabric capacity of F64 or larger (the successor to the old Premium P1), content in workspaces on that capacity can be viewed by users with only a free licence. The organisation pays for the capacity, and the viewers ride for free. This is how large Australian enterprises make the numbers work: a few hundred Pro licences for the builders, one capacity, and thousands of free-licence consumers.
That last model is the one Microsoft's business user documentation spends most of its time on, because it changes the answer to "what do I need?" from "a Pro licence" to "possibly nothing, depending on where the report lives".
How to work out what you have
The genuinely useful trick in the Microsoft doc, which almost nobody knows: you can check your own licence from inside the Power BI service. Open app.powerbi.com, go to your account settings (the profile picture, top right), and it will tell you whether you're on Free, Pro or PPU, and whether it's a trial. Ten seconds, and it settles the "but I thought I had Pro" argument that otherwise burns half an hour of a support call.
Whether the content you're trying to view sits on capacity is harder for a business user to see, and honestly, it shouldn't be their problem. In a well-run tenant, the BI or platform team knows which workspaces are on capacity and which aren't, and shares content accordingly. In a badly run tenant, viewers get links that half of them can't open and IT gets tickets. If your organisation is fielding those tickets weekly, that's not a user education problem, it's a workspace strategy problem, and it's one of the first things we fix on Power BI consulting engagements.
The trial trap
Power BI hands out 60-day trials of Pro and PPU fairly freely. A user hits a feature they're not licensed for, gets prompted to start a trial, clicks yes, and everything works. For 60 days.
Then the trial ends, the report they've been using every day stops opening, and they log a ticket saying Power BI is broken. Nothing is broken. They just fell off a cliff nobody told them was there. If you're an admin, you can see who's on trials and get ahead of it. If you're a business user and Power BI ever offered you a trial you accepted, put a note in your calendar for day 50 and tell whoever owns licensing. Genuinely, this one habit would eliminate a decent slice of the Power BI support tickets we see.
Admins can also switch off self-service trial sign-ups in the tenant settings, and for organisations with any licensing discipline, we usually recommend it. Not because trials are bad, but because a trial someone starts without telling anyone is a dependency nobody is managing.
What we recommend to clients
After enough of these engagements you develop opinions. Here are ours.
Under about 60 regular users, just buy Pro for everyone who needs it. The break-even maths on an F64 capacity (which runs to several thousand dollars a month) doesn't work until your consumer count gets into the hundreds. Small and mid-sized organisations overthink this constantly. Pro licences, one shared workspace structure, done.
Past a few hundred consumers, price up capacity. The free-viewer model on F64+ starts winning clearly. But do the maths on your actual numbers, not the vendor's example, and remember capacity brings obligations: someone has to monitor it, manage refresh contention, and stop one runaway dataset from slowing everyone's Monday morning reports. Capacity is infrastructure, and infrastructure needs an owner. If you're already heading down the Fabric path for data engineering reasons, this decision often makes itself, and our Microsoft Fabric consultants spend a lot of time helping clients size this properly rather than guessing.
Be very deliberate about PPU. It's the right tool for a small analytics team that needs Premium features without capacity spend. It's the wrong tool sprinkled randomly across an organisation, because of the consumption lockout described above. Decide who gets it, document why, and don't let it spread by osmosis.
E5 changes the calculation. If you're already on Microsoft 365 E5, Pro is bundled and the "who needs a licence" question mostly evaporates for sharing purposes. Plenty of Australian enterprises are paying for E5 and separately paying for Pro licences out of a different cost centre because the two teams never compared notes. Check before you buy anything.
The rough edges nobody warns you about
A few honest observations from the field.
The error messages are bad. When a free user opens a link to content they can't access, the message rarely says "you need a Pro licence" in plain language. Sometimes it offers a trial, sometimes it shows a generic access error that looks identical to a permissions problem. So the viewer can't tell whether they need a licence, need to be added to the workspace, or both. Admins end up diagnosing by elimination.
Licensing and permissions are separate systems and both must be satisfied. A Pro licence with no access grant gets you nothing; workspace access with no licence (and no capacity) also gets you nothing. When someone can't see a report, check both, always, in that order.
And the naming keeps moving. Premium capacity became Fabric capacity, P SKUs became F SKUs, and older internal wiki pages at every client we visit still reference the old names. If your organisation's Power BI onboarding doc mentions "P1", it's overdue for a rewrite.
Where this lands
For the individual business user, the practical answer is short: check your licence in your account settings, ask the report owner whether the content sits on capacity, and never accept a trial without telling someone. For the organisation, it's a design decision - Pro for everyone, capacity plus free viewers, or a mix - and it deserves an actual decision rather than an accumulation of accidents.
If your tenant's licensing has grown by accident rather than design, that's a solvable problem and usually a quick one. It's the kind of thing we sort out early in most business AI and data engagements, because there's no point building great reports on top of a licensing model nobody understands. Get in touch if you want a second pair of eyes on yours.