Power BI licensing explained without the jargon
Power BI licensing confuses many buyers, because it mixes per-user licenses with shared capacity. The idea underneath is simple, however. Some licenses belong to a person, and others buy computing power for a whole organization. The right mix depends on how many people build reports and how many only read them. This guide explains the options in general terms and points to Microsoft for current details.
- General terms only
- Authors versus readers
- Links to Microsoft's pages
Last updated
How does Power BI licensing work in general?
Two questions decide what you need. First, who creates and shares content? Second, where does that content live? The answers lead to either per-user licenses, a capacity or a blend of both.
A per-user license gives one named person the right to publish and to view shared reports. A capacity is different. It reserves computing resources for your organization, and workspaces assigned to it gain extra features.
So small teams usually start with per-user licenses alone. Larger audiences often add a capacity later, because it changes who can read content without a paid license. If you want the seats you already hold audited, that work is our Power BI license optimization service.

What are the main license types?
This overview is correct as of October 2026; Microsoft updates names, limits and plans, so check its pages before you buy.
| License | Who holds it | What it is for |
|---|---|---|
| Free | One user | Personal use in the user's own workspace, and viewing content hosted on an F64 or larger capacity |
| Pro | One user | Publishing, sharing and collaborating in standard workspaces |
| Premium Per User | One user | Everything in Pro, plus selected premium features for that user |
| Fabric capacity | The organization | Reserved resources, wider platform workloads and, from F64 upward, viewing by free users |
| Embedded capacity | The organization | Showing reports inside your own application for outside users |
Which license do authors and readers need?
Authors need a paid per-user license in almost every setup. They publish to shared workspaces, and that right comes with Pro or Premium Per User. Even on a capacity, the people who build still hold one.
Readers are where the options diverge. In a standard workspace, each reader needs a paid license too. On a Fabric F64 or larger capacity, however, readers with a free license can open the content. Below F64, every reader needs Pro or Premium Per User.
Therefore the reader count matters most. A company with twenty authors and fifty readers may stay on per-user licenses. One with twenty authors and several thousand readers should compare that cost with a capacity. For the per-user choice, see Power BI Pro vs Premium Per User, and for the capacity choice, see Power BI Premium vs Fabric capacity.
Power BI licensing mistakes that waste budget
These errors waste budget or block a rollout, and all of them are avoidable.
- Buying a capacity before anyone has counted authors and readers
- Paying for licenses that sit unassigned in the admin center
- Overlooking licenses already included in a Microsoft 365 plan
- Placing content in a Premium Per User workspace that Pro users must read
- Sizing a capacity by guesswork instead of measured workload
- Assuming last year's rules still apply without checking Microsoft's pages
How to plan Power BI licensing in four steps
A short review now prevents an expensive correction later.
Count your users by role
First list who builds, who reads often and who reads rarely. Those three groups drive the whole plan.
Check what you already own
Then review your Microsoft 365 agreement, because some plans include licenses that nobody has assigned.
Compare the two routes
After that, cost the same audience on per-user licenses and on a capacity, using Microsoft's current published plans.
Review each year
Finally, repeat the exercise yearly. User numbers change, and Microsoft revises its offers as well.
Questions about Power BI licensing
Can people use Power BI without a paid license?
Yes, within limits. A free license lets a user work in a personal workspace and build with the desktop application. Free users can also view shared content when it sits on a Fabric F64 or larger capacity. Sharing from a standard workspace, however, needs a paid license for both the author and the reader.
What happened to Premium capacity?
Microsoft announced the retirement of Premium per-capacity (P) SKUs in March 2024. As of October 2026, it no longer sells new P SKUs, and each existing P subscription retires at the end of its agreement term. So existing customers move to Fabric (F) SKUs at renewal. F capacities carry the reporting workload along with other data workloads.
Do external guests need a license?
Usually, yes. A guest from another organization follows the same logic as an internal reader. Either the guest brings a suitable license, you assign one, or the content sits on a capacity that allows free viewing. For customer-facing applications with many outside users, an embedded approach is often a better fit.
How do we know what capacity size we need?
Measure first. A trial capacity and Microsoft's capacity metrics app show how much your real models and refreshes consume. Because usage varies widely, general rules mislead. We test the heaviest reports, watch the metrics for a few weeks and then recommend a size with some room for growth.
Do you sell or resell licenses?
No. Power BI Agency is a division of Sataware Technologies and is independent of Microsoft. We do not resell licenses or capacity. Instead, we help you work out the mix that suits your users and then build on it. A free 30-minute assessment is a good place to raise license questions.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.