For years, Power BI was an internal tool — a way for organisations to give their own employees access to data. Power BI Embedded changes that equation entirely. It allows organisations to embed Power BI reports and dashboards directly into their customer-facing applications, turning analytics from a cost centre into a product feature that customers will pay for.
The Licensing Model Explained
Power BI Embedded uses a capacity-based licensing model rather than per-user licensing. You purchase Azure capacity (measured in A-SKUs, from A1 to A8) and embed reports for any number of users without per-user fees. This makes the economics work for customer-facing applications where you cannot predict or control how many users will access your embedded analytics.
Licensing Tip
Start with A1 capacity (approximately R8,500/month) and scale up as usage grows. A1 supports up to 300 concurrent users for typical dashboard workloads. Most organisations find they can serve their initial embedded analytics use case on A1 for the first 12–18 months.
Architecture Patterns
The standard Power BI Embedded architecture uses a service principal to authenticate your application with the Power BI service, generate embed tokens on demand, and pass those tokens to the client-side JavaScript SDK. The key design decision is where to place the embed token generation logic — it must be server-side to protect your service principal credentials, but it needs to be responsive enough to not introduce perceptible latency in your application.
- Service principal authentication (not master user) for production deployments
- Row-level security (RLS) to ensure customers only see their own data
- Embed token caching to reduce API calls and improve performance
- Workspace-per-tenant isolation for strict data separation requirements
- Azure API Management as a gateway for embed token generation at scale
Making the Business Case
The ROI calculation for Power BI Embedded depends on your monetisation model. For SaaS vendors, embedded analytics can justify a 15–25% price premium on higher-tier plans. For financial services firms, providing clients with self-service portfolio analytics reduces inbound query volume to relationship managers — a cost saving that is measurable and attributable. For retailers, embedded supplier analytics portals reduce the manual reporting burden on category management teams.
“The organisations that get the most value from Power BI Embedded are those that treat it as a product, not a feature. That means user research, iterative design, and a dedicated product owner for the analytics experience.”
Common Implementation Pitfalls
The most common mistake we see is organisations that embed Power BI reports designed for internal use without redesigning them for external audiences. Internal reports are built for data-literate users who understand the business context. Customer-facing analytics need to be self-explanatory, mobile-responsive, and designed around the questions your customers are actually trying to answer — not the questions your internal analysts find interesting.