.jpg)
To share Power BI with franchisees without buying a Pro license for each location, deliver the reports on a Microsoft Fabric capacity instead of the per-user model. On capacity, unlimited franchisees can view their dashboards without an individual Power BI Pro or Premium license — you pay one fixed capacity fee, and Row-Level Security keeps each location scoped to its own data. This replaces a bill that grows ~$14/franchisee/month with a flat, predictable cost, and avoids the admin of provisioning a license for every location.
If you've priced out giving every franchisee access to Power BI, you've hit the wall that makes franchise reporting painful: the per-user license. At $14 per user per month, a 50-location network is $700+/month in licenses alone — before any admin — and it climbs with every new franchisee. The good news is that per-user licensing isn't the only way to share Power BI. Here's the licensing reality and the model that removes the per-location cost.
TL;DR — sharing Power BI with franchisees
- Per-user licensing is the trap. Power BI Pro (~$14/user/month) means every franchisee who logs in needs their own license — cost and admin grow with the network.
- Capacity-based delivery removes it. On a Fabric capacity, unlimited viewers see reports with no per-user license; you pay one fixed capacity fee.
- Security is handled by RLS, so each franchisee sees only their own location — not a side effect of who holds a license.
- Avoid Publish to web for franchise data: it's license-free but makes reports public to anyone with the link.
- A managed portal adds branding, SSO, and per-franchisee spaces on top of the capacity model, live in hours.
Why per-location licensing breaks down
Microsoft's default sharing model is per user: to view shared Power BI content, each person generally needs a Power BI Pro license (or Premium Per User). For an internal team that's fine. For a franchise network it's the wrong shape — you're buying a productivity license for people who only need to view their own location's numbers, and you're doing it dozens or hundreds of times over. In April 2025 Pro rose to $14/user/month, so networks that budgeted on the old $10 figure are now 40% over. And beyond cost, there's the admin: inviting, licensing, and offboarding a license for every franchisee as the network churns. (See Power BI Embedded vs Pro vs Premium for external sharing.)
The fix: deliver on capacity, not per user
Put your franchise reporting on a Microsoft Fabric capacity. Viewers then consume reports without an individual Pro or Premium license — you pay one fixed capacity fee (an F2 starts around $263/month) for unlimited franchisees, sized to load rather than to how many locations you have. Row-Level Security scopes each franchisee to their own location's data, so isolation comes from security rules, not from who holds which license. This is the same "app owns data" economics that lets any business share Power BI externally without per-viewer licensing. (See share Power BI with external users without extra Pro licenses and 4 ways to share Power BI reports externally.)
Ways to share Power BI with franchisees — compared
Don't solve it with Publish to web
It's tempting: Publish to web is free and needs no licenses. But it makes the report publicly accessible to anyone with the link — no authentication, no per-location isolation. For franchise data (sales, margins, staff) that's a data-exposure risk, not a sharing strategy. Capacity-based delivery gives you the same "no per-user license" benefit with authentication and RLS. (See Publish to web vs a secure embed and guest user access: pros and cons.)
The practical setup
A managed portal on top of the capacity model gives each franchisee a branded login, SSO, and their own scoped view, all administered centrally — live in hours rather than a build. Adding a franchisee means adding them to the portal and RLS role, with no new license. Head office keeps its network roll-up on the same capacity. (See how sub-organizations work, Power BI for franchises, and the DataTako for franchises & multi-location page.)
Frequently asked questions
Can I share Power BI with franchisees without buying each one a license?
Yes. Deliver the reports on a Microsoft Fabric capacity instead of the per-user model. On capacity, unlimited franchisees view their dashboards without an individual Power BI Pro or Premium license — you pay one fixed capacity fee. Row-Level Security keeps each franchisee scoped to their own location's data.
How much does it cost to give 50 franchisees Power BI access?
On per-user licensing, roughly $700+/month (50 × ~$14) plus admin, rising with every new location. On a Fabric capacity, it's a fixed fee starting around $263/month for an F2 serving all 50 (and more), sized to load rather than location count — so the cost stays flat as the network grows.
Is Publish to web a safe way to share with franchisees?
No. Publish to web is license-free but makes the report publicly accessible to anyone with the link, with no authentication or per-location isolation. For franchise data that's a data-exposure risk. Use a capacity-based portal with Row-Level Security instead to get license-free access with proper security.
How do franchisees log in if they don't have a Power BI license?
Through a portal on the capacity model, using SSO (SAML/Entra/Google) or portal credentials — not a Power BI license. The portal authenticates them and Row-Level Security scopes them to their location. They never need a Power BI account of their own.
Does each franchisee still only see their own data?
Yes. Isolation comes from Row-Level Security, which filters the shared dataset so each login sees only its own location's rows, and from portal-level separation. It's independent of licensing — you get both no per-user license and strict per-location isolation.
Pricing franchise access? Run the cost calculator for your location count, or book a walkthrough. Related: DataTako for franchises & multi-location, Power BI for franchises, the hidden cost of Power BI Pro, and share Power BI with external users without extra Pro licenses.
