A Power BI client portal costs anywhere from $14 per viewer per month to a fixed capacity fee, depending on how you build it. The four routes are: Power BI Pro ($14/user/month), Premium Per User ($24/user/month), Microsoft Fabric capacity (from ~$263/month for an F2, unlimited viewers), or Power BI Embedded on an A-SKU (from ~$735/month). A managed white-label portal such as DataTako sits on top of Fabric capacity and starts at €279/month, removing the developer build. The right choice comes down to one number: how many external viewers you need to serve.
If you're pricing a client-facing portal — where customers, partners, or agency clients log in to see their own Power BI dashboards — the confusing part isn't the sticker price of any single licence. It's that the cheapest option flips completely depending on your viewer count. Per-user licensing looks cheap at 5 users and absurd at 500. Capacity looks expensive at 5 users and almost free at 500. This guide gives you the real 2026 numbers, a worked example, and the break-even point where each model wins.
TL;DR — the four ways to price a Power BI client portal
- Power BI Pro — $14/user/month. Every viewer needs their own licence. Fine up to ~20 external users; brutal beyond that.
- Premium Per User (PPU) — $24/user/month. Still per-user, so it scales the same way as Pro — just more expensive per seat. Rarely the right answer for external portals.
- Microsoft Fabric capacity (DIY embedded) — from ~$263/month (F2). One fixed fee, unlimited external viewers, no per-user licence. But you build the portal, auth, and embedding yourself.
- Power BI Embedded (A-SKU) — from ~$735/month (A1). The ISV-oriented capacity model; bills hourly and can pause. Same DIY build effort.
- White-label portal (e.g. DataTako) — from €279/month + your Fabric capacity. The capacity model without the months of development. Live in hours, not months.
The break-even is roughly 20 external viewers against raw DIY capacity, and roughly 35–40 viewers against a managed portal — past that, every additional viewer on the capacity model is effectively free, while every additional Pro seat keeps costing $14/month forever.
What "client portal pricing" actually includes
A Power BI client portal has three cost layers, and most pricing pages only show you one:
- The licence or capacity — what you pay Microsoft to let people view reports. This is the layer everyone quotes.
- The build — the developer time to create the portal UI, wire up authentication, pass Row-Level Security identities, handle refresh tokens, and manage users. This is invisible on a pricing page but often the biggest first-year cost.
- The ongoing management — user provisioning, branding, capacity monitoring, and support once it's live.
Per-user licensing (Pro/PPU) has a low build cost but a licence bill that grows with every user. Capacity models (Fabric/Embedded) flip that: a fixed licence bill, but a real build cost. A managed portal collapses layers 2 and 3 into a subscription. Keep those three layers in mind as you read the numbers below — comparing only layer 1 is how teams end up surprised.
The five pricing routes, with real 2026 numbers
1. Power BI Pro — $14 per user per month
Every external viewer needs a Power BI Pro licence. In April 2025 Microsoft raised Pro from $10 to $14 per user per month — its first price change in nearly a decade — so budgets built on the old $10 figure are now 40% short.
When it fits: a handful of named external users who are comfortable with a Microsoft sign-in. When it doesn't: any client portal past ~20 viewers, where the linear cost stops making sense.
2. Premium Per User (PPU) — $24 per user per month
PPU adds larger models, more frequent refreshes, and advanced features — but it's still a per-user licence, so it scales exactly like Pro, just steeper (it also rose in April 2025, from $20 to $24). For a client portal, you're paying enterprise-feature money for people who only need to view a dashboard. It's almost never the right portal model.
3. Microsoft Fabric capacity — from ~$263/month (F2)
This is where external portals get economical. Put your workspace on a Microsoft Fabric F-SKU capacity and viewers consume reports without a per-user licence. An entry-level F2 costs roughly $263/month on pay-as-you-go (about $156/month on a one-year reservation). Larger workloads step up to F4, F8, and beyond; an enterprise F64 runs ~$8,410/month pay-as-you-go.
Two things make capacity pricing genuinely flexible: it's a single fixed fee regardless of viewer count, and pay-as-you-go capacities can be paused when idle, so a portal that's only busy during business hours can cost a fraction of the always-on figure. The catch is the build — you need developers to create the embedding layer, the authentication handoff, and the portal itself. (For sizing, see Which Fabric capacity do I need? and Fabric pay-as-you-go vs reserved capacity.)
4. Power BI Embedded (A-SKU) — from ~$735/month (A1)
Power BI Embedded uses Azure A-SKUs designed for ISVs embedding analytics in their own product. A1 starts around $735/month always-on, bills hourly, and can pause. The licensing logic is the same as Fabric capacity — unlimited viewers, no per-user licence — but A-SKUs are aimed at "app-owns-data" scenarios where viewers authenticate to your application, never to Power BI directly. Same DIY build effort as route 3.
5. White-label portal via DataTako — from €279/month + capacity
A managed portal is the shortcut to routes 3 and 4. DataTako runs on Fabric capacity (so you keep the "no per-user licence" economics) but the embedding layer, authentication, Row-Level Security mapping, user management, and white-label branding are already built. You connect your existing Power BI workspace and go live in hours. Pricing starts at €279/month for the Launch plan, on top of your Fabric capacity. You trade a modest subscription for the months of engineering that DIY capacity requires.
Cost comparison at a glance
USD list prices for Microsoft licences; DataTako plans are priced in EUR. Capacity figures are approximate US-region pay-as-you-go rates for 2026 — always confirm current rates for your region.
Worked example: what 50, 200, and 500 external viewers actually cost
This is the number that matters. Assume a client portal serving read-only external viewers:
At 50 viewers, Pro already costs more than a fixed F2 capacity. At 500 viewers, per-user licensing is $7,000/month and the capacity model is a fraction of that. The break-even against raw DIY capacity lands around 20 viewers; against a managed portal like DataTako (subscription plus capacity), around 35–40 viewers — after which the managed route is both cheaper and saves the build.
The hidden costs people forget
- Developer build. A production-grade DIY embedded portal — auth, RLS handoff, token refresh, error handling, UI — is typically weeks to months of engineering. At blended developer rates that dwarfs the capacity fee in year one.
- Row-Level Security maintenance. Getting each client to see only their own data is straightforward to design and easy to get subtly wrong; it needs ongoing testing as you add clients.
- Guest accounts and IT reviews. The per-user route often drags in Microsoft Entra guest invitations, which trigger compliance reviews and confuse non-technical external users.
- Capacity right-sizing. Under-provision and reports crawl; over-provision and you burn budget. Pause/resume and reservations are the levers that keep this efficient.
Decision shortcut
- 1–20 named external viewers, Microsoft-comfortable → Power BI Pro.
- You need advanced modelling for a few power users → PPU (rarely for portals).
- 20+ external viewers and you have developers → Fabric capacity, DIY embedded.
- You're an ISV embedding analytics inside your product → Power BI Embedded (A-SKU).
- 20+ external viewers and you want a branded portal live this week → a managed white-label portal such as DataTako.
Frequently asked questions
How much does a Power BI client portal cost?
It ranges from $14 per viewer per month (Power BI Pro) to a fixed capacity fee starting around $263/month (Microsoft Fabric F2) for unlimited viewers. A managed white-label portal such as DataTako starts at €279/month on top of your Fabric capacity. The cheapest option depends almost entirely on viewer count: per-user licensing wins below ~20 viewers, capacity-based models win above it.
Do external users need a Power BI Pro licence to access a client portal?
Only if you build the portal on the per-user model. With a Fabric or Power BI Embedded capacity, external viewers consume reports without an individual Pro or PPU licence — you pay a fixed capacity fee instead. This is the core reason capacity-based portals become cheaper as viewer numbers grow.
What is the cheapest way to give clients access to Power BI dashboards?
Below about 20 viewers, Power BI Pro at $14/user is cheapest. Above that, a Microsoft Fabric capacity (from ~$263/month for an F2) serving unlimited viewers is consistently cheaper, because the fee is fixed regardless of how many people log in. If you don't have developers to build the embedding layer, a managed portal removes that cost.
How much is Microsoft Fabric capacity for a client portal?
An entry-level F2 capacity is roughly $263/month pay-as-you-go, or about $156/month on a one-year reservation. Larger SKUs scale up (F64 is around $8,410/month pay-as-you-go). Capacity can be paused when idle, so a portal used only in business hours costs far less than the always-on figure.
Is Power BI Embedded cheaper than Power BI Pro for external sharing?
For more than ~20–30 external viewers, yes. Power BI Embedded (A1 from ~$735/month) and Fabric capacity charge one fixed fee for unlimited viewers, while Pro charges $14 per viewer every month. The more external viewers you have, the more the fixed-fee model wins.
What does DataTako cost compared with building a portal myself?
DataTako starts at €279/month plus your Fabric capacity. A DIY portal avoids that subscription but adds weeks to months of developer time to build and maintain the embedding, authentication, and user management — which usually exceeds the subscription cost in the first year alone. DataTako trades that build for a fixed monthly fee and a launch measured in hours.
Does Premium Per User make sense for a client portal?
Rarely. PPU ($24/user/month) is still a per-user licence, so it scales the same way as Pro but costs more per seat. It's built for report authors who need advanced features, not for read-only external viewers. For a portal, capacity-based licensing is almost always the better economic fit.
How do I estimate the right Fabric capacity for my portal?
Size to peak concurrency and query load, not raw viewer count — a portal with 500 occasional viewers may run comfortably on an F2, while 50 heavy concurrent users might need an F4 or F8. Start small, monitor utilisation, and scale up only when the capacity metrics app shows sustained pressure.
