Skip to content

Est. 2011ยทMicrosoft Partner 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Review

Power BI Pro Review 2026: The Licence Every Report Consumer Needs

9 min read Updated October 5, 2026 Microsoft Product Reviews

Fix it now

Power BI Desktop is free and that is where reports are built. Pro is the licence that lets you publish what you built, share it, and lets colleagues open it. That last clause catches organisations out: in an ordinary workspace the audience needs a licence too, not just the author.

  1. Buy it for everyone who publishes and, in an ordinary workspace, everyone who reads. A report with one author and forty readers is forty-one licences.
  2. Buy it if you need scheduled refresh from on-premises sources through a gateway, row-level security and proper workspace collaboration.
  3. Buy it as the starting point for almost any organisation, because it is the licence that makes sharing work at all.
  4. Skip it for people who only build reports for themselves and never share. Free Desktop and a personal workspace cover that.
  5. Skip it for readers once your content sits on a Fabric capacity of F64 or larger, or on Power BI Premium per capacity, where a viewer with only a free licence can open it. Authors still need Pro.
  6. Check what you already hold. Office 365 E5 includes a Power BI Pro licence, and organisations regularly buy it twice.

The free-viewing threshold is a specific capacity size, not any paid capacity. Below F64 every viewer still needs Pro or Premium Per User.

If that settles it you can stop here. If you want the service limits that shape a design, and the break-even method, keep reading.

Why it happens

There are three roles in Power BI and only two of them are obvious. Authors build reports, publishers push them to the service, and consumers open them. Power BI Desktop covers the first at no cost and is the full authoring environment, not a cut-down one. Publishing to a shared workspace requires Pro. Opening a report published in an ordinary workspace also requires Pro, because a free licence gives you your own personal workspace and nothing else.

There is one exception and it is the whole basis of the capacity conversation. Microsoft states that a user with only a free licence and a viewer role can view Power BI content in a workspace on a Fabric capacity of F64 or larger, or on Power BI Premium per capacity. Below that size, on F2 through F32, every viewer still needs Pro or Premium Per User. Authors need Pro either way: free viewing applies to reading, not to publishing.

The practical consequence is that Power BI cost is not driven by how much data you have or how complex your reports are. It is driven by how many people look at them. Count your readers first and everything else follows from that number, including whether the capacity conversation is worth having at all.

What a Pro workspace gives you is collaboration with roles that separate people who can edit from people who can only view. From a workspace you publish an app, which is the tidy way to distribute a set of reports to a wide audience without exposing the working artefacts behind them. Row-level security filters what each person sees from a single semantic model, so one report serves every regional manager without building one report per region. An on-premises data gateway lets scheduled refresh reach SQL Server and file shares inside your network.

Sharing is where discipline pays. Individual item sharing is convenient and becomes unmanageable within a year. Distribute through apps and Microsoft Entra ID groups instead, so leavers lose access when their group membership changes rather than when somebody remembers a report exists. This costs nothing and is the single most useful governance decision available to a small Power BI deployment.

The service limits are where designs meet reality, and two of them bite more often than the model size ceiling everyone quotes. On shared capacity, which is what a Pro licence uses, Microsoft limits a semantic model to eight scheduled refreshes a day, and a refresh must complete in under two hours. On Premium, Premium Per User or Fabric capacity the refresh limit rises to 48 a day and the duration limit to five hours. If your business wants near-current figures, or your model takes ninety minutes to refresh on a good day, you have a capacity conversation whether or not your reader count says so.

Full reference

Who needs which licence

Licence Who needs it What it unlocks
Free Individuals building for themselves, and viewers of content on F64 or larger Desktop authoring, a personal workspace, and viewing on a qualifying capacity
Pro Authors, publishers, and readers in ordinary workspaces Publishing, sharing, apps, collaboration, gateway refresh
Premium Per User Individuals needing larger models and more frequent refresh Most capacity features for one person, but everyone opening that content needs it too
Fabric capacity F64 or larger Organisations with a large reader population Free-licence viewing, paginated reports, XMLA write, deployment pipelines

The limits that shape a design

Limit Shared capacity (Pro) Premium, Premium Per User or Fabric capacity
Scheduled refreshes per day 8 48
Maximum refresh duration 2 hours 5 hours, and the XMLA endpoint can bypass it
Semantic model memory Capped at 1 GB Premium Per User supports models above 1 GB; capacity sizes vary
Who can view Pro or Premium Per User Free licence and viewer role, on F64 or larger

Microsoft adjusts these figures over time, so treat the table as the current shape rather than a permanent contract, and check the published limits before designing against the edge of one.

What sits above Pro entirely

  • Paginated reports, for pixel-controlled printable output that Power BI’s interactive reports were never designed for.
  • The XMLA write endpoint, which lets external modelling and deployment tools manage semantic models directly.
  • Deployment pipelines for staged release between development, test and production.
  • Larger semantic models and more frequent refresh, whether through Premium Per User or capacity.
  • If you need one of those, the decision is made on capability and the seat arithmetic is beside the point.

Working out where capacity starts to win

  1. Count the people who need to read Power BI content today, and estimate the figure a year from now. Readers, not authors, drive the decision.
  2. Count the authors and publishers. They need Pro whether or not you buy capacity, so they sit on both sides of the comparison.
  3. Get the monthly figure for the smallest capacity that grants free viewing, which is F64, and for a Pro seat, from your own quote.
  4. Divide one by the other. That is the reader count at which capacity becomes cheaper.
  5. Add a margin for the administration capacity needs, and for the fact that pay-as-you-go and reserved commitments are priced differently.
  6. If your reader count is comfortably below that figure, buy Pro seats and revisit next year.

Habits that keep the bill honest

  • Distribute through apps and groups rather than sharing individual items, so access follows employment rather than memory.
  • Use one well-built semantic model with row-level security instead of one report per audience.
  • Watch refresh failures rather than assuming eight a day is enough, because a failed refresh consumes the allowance too.
  • Check whether your Microsoft 365 subscription already includes Power BI Pro before buying seats. Office 365 E5 does, and firms regularly pay twice.
  • Review assignments before renewal. Report authors leave, and their seats stay allocated.

When a licence is the actual fix

Power BI Pro is the licence that makes Power BI a shared tool rather than a personal one, and for most organisations it is the correct and only purchase for a long time. Buy it for everyone who publishes and everyone who reads in an ordinary workspace, remembering that the reader count drives the bill. Arco can supply Power BI Pro seats and will happily do the break-even calculation with you before you order a large block: if your audience is big enough that a Fabric capacity of F64 or larger costs less than the seats, we would rather tell you that than sell you two hundred licences. It is also worth checking whether Power BI Pro is already included in the plan you hold, since Office 365 E5 carries it and organisations buy it twice more often than they would like to admit.

Questions people ask about this

Do report viewers really need a paid licence?

In an ordinary workspace, yes. A free licence gives access to your own personal workspace only. The exception is content hosted on a Fabric capacity of F64 or larger, or on Power BI Premium per capacity, where a user with a free licence and a viewer role can open it. That single rule is the main driver of Power BI cost.

Is Power BI Desktop limited compared with the service?

No. Desktop is the full authoring environment and it is free. The service is where publishing, sharing, scheduled refresh and governance live, which is what the licence pays for. Nobody needs a Pro seat to build a report; they need one to give it to somebody else.

How often can a Pro workspace refresh?

Eight scheduled refreshes a day on shared capacity, and each refresh must complete within two hours. On Premium, Premium Per User or Fabric capacity the limits are 48 refreshes a day and five hours, and the XMLA endpoint can bypass the duration limit. If you need near-current figures, that is a capacity conversation regardless of your reader count.

Can we share a report with someone outside the organisation?

External sharing is possible through Microsoft Entra ID business-to-business guests, subject to your tenant settings, and the guest generally needs an appropriate licence or must be covered by a qualifying capacity. Confirm the rules before promising an external client a dashboard, because this is where informal arrangements become licensing problems.

Is Premium Per User a cheaper middle route?

Sometimes. It gives one person larger models and more frequent refresh, but everyone who opens that content must hold Premium Per User too, including through the XMLA endpoint, Analyze in Excel and composite models. It fits a small analytics team sharing among themselves and fits badly when the audience is the wider business.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Review SQL Server 2025 Standard Review: Core Licences, CALs and the Memory Cap Review Visio Plan 1 Review: Browser-Based Diagramming for Occasional Users Review Microsoft Intune Plan 1 Review: Device Management Without a Server Room Review Project Professional 2024 Review: Offline Scheduling, One Payment
โ† Back to Knowledge Base