The Power BI Embedded Licensing Problem
Power BI Embedded is the version of Power BI designed for embedding analytics into applications — whether an enterprise internal portal, a customer-facing product, or an ISV software solution. Unlike standard Power BI Pro or Premium Per User (PPU), Embedded uses a capacity-based pricing model that charges for a block of compute rather than per individual user.
The commercial case for Embedded is compelling at scale: if you need to deliver Power BI reports to hundreds or thousands of users — internal or external — who do not themselves hold Power BI Pro licences, Embedded capacity is often dramatically cheaper than licensing each viewer individually. But the Embedded licensing landscape is genuinely confusing, with three overlapping SKU families (A-series, P-series, EM-series), two purchasing routes (Azure portal and Microsoft 365 admin centre), and a set of capability restrictions between Embedded and Premium that are not clearly documented.
This guide covers the mechanics precisely: what each SKU provides, when Embedded makes commercial sense versus per-user licensing, the most common pricing errors enterprises make, and how to structure Embedded in an EA negotiation.
The Three SKU Families: A-Series, P-Series, EM-Series
Power BI capacity SKUs come in three families with meaningfully different commercial and technical characteristics:
| SKU Family | Purchased Via | Typical Use Case | Internal Users Need Pro? | External (Non-M365) Users |
|---|---|---|---|---|
| A-Series (A1–A8) | Azure portal (pay-as-you-go or reserved) | ISV embedding, development/test, customer-facing analytics | Yes — authors/admins still need Pro | Supported — no licence needed for viewers |
| P-Series (P1–P5) | Microsoft 365 admin centre / EA | Enterprise internal analytics, large-scale internal deployment | No — all users in tenant can view without Pro | Limited — primarily for internal tenants |
| EM-Series (EM1–EM3) | Microsoft 365 admin centre / EA | Embedding into O365 apps (SharePoint, Teams) | Yes — viewers need Pro or Premium Per User | Limited |
The A-series is Microsoft's Azure-native Embedded offering, optimised for ISV and developer scenarios. The key commercial advantage: users accessing embedded Power BI reports via A-series capacity do not need individual Power BI licences. This makes A-series the correct choice for embedding analytics in customer-facing products or enterprise portals where the user population is too large or too external to licence individually.
A-Series Sizing: The SKU Progression
| SKU | V-Cores (Front End) | V-Cores (Back End) | Memory (GB) | Approx. List Price/Month | Recommended Max Concurrent Users |
|---|---|---|---|---|---|
| A1 | 1 | 0.5 | 3 | ~£735 | Up to 300 concurrent (simple reports) |
| A2 | 2 | 1 | 5 | ~£1,470 | Up to 600 concurrent |
| A3 | 4 | 2 | 10 | ~£2,940 | Up to 1,200 concurrent |
| A4 | 8 | 4 | 25 | ~£5,880 | Up to 3,000 concurrent |
| A5 | 16 | 8 | 50 | ~£11,760 | Up to 5,000+ concurrent |
| A6 | 32 | 16 | 100 | ~£23,520 | Large enterprise / high-complexity models |
The "recommended max concurrent users" figures above are for simple, cached reports with moderate data model complexity. Complex reports with live DirectQuery connections, frequent refreshes, and large data models will hit capacity limits at far lower concurrent user counts. Always test actual concurrent load patterns against a smaller SKU before committing to capacity-based pricing.
The Per-User vs Capacity Break-Even Analysis
The fundamental commercial question for Power BI Embedded is: at what user volume is capacity-based pricing cheaper than per-user Pro licences?
Power BI Pro costs £8.40/user/month at list price (typically £7.00–£7.50 at EA pricing). An A1 node at £735/month represents the equivalent of 87–105 Pro licences. If your user population for a given reporting workload exceeds approximately 87–105 users, an A1 node is commercially competitive with Pro licences.
However, the comparison is not simply Pro licences vs A-series capacity. Three additional factors adjust the break-even:
Factor 1: Content Author Licences
Users who create and publish Power BI reports — regardless of which capacity they use — require either Power BI Pro or Premium Per User (PPU) licences. Capacity does not eliminate the authoring licence requirement. For a deployment with 1,000 viewer users and 20 content authors, the comparison is: 1,000 × Pro (£8,400/month) vs A-series capacity + 20 × Pro (£168/month authoring overhead). The authoring overhead is usually small relative to viewer volume.
Factor 2: Azure MACC Consumption
A-series Embedded purchased through Azure can count against an Azure MACC commitment. If your organisation has an Azure MACC that is underspending, Power BI Embedded A-series is an Azure service that can absorb that commitment. This changes the effective cost: if the A-series spend displaces underutilised MACC that would otherwise be wasted, the incremental cost of the Embedded capacity is zero. See the Azure MACC guide for the broader MACC management framework.
Factor 3: Auto-Pause for Low-Usage Periods
A-series capacity on Azure can be paused programmatically when not in use. For report deployments with predictable off-hours (overnight, weekends), auto-pause can reduce effective monthly cost by 30–50%. A deployment that runs only 12 hours/day, 5 days/week pays approximately 36% of the full monthly rate. This makes the A1 vs Pro break-even shift significantly: the effective cost of a business-hours-only A1 node drops to approximately £265/month, breaking even with Pro licences at around 31 users.
Power BI Premium vs Embedded: The Key Differences
Power BI Premium Per Capacity (P-series) and Power BI Embedded (A-series) use the same underlying compute infrastructure and support the same dataset sizes and refresh rates at equivalent SKU levels (P1 ≈ A4 in compute terms). However, there are important differences in use case, purchasing flexibility, and what happens to workloads when capacity is paused:
| Dimension | Power BI Premium (P-Series) | Power BI Embedded (A-Series) |
|---|---|---|
| Viewer licence requirement | No — all tenant users can view without Pro | No — viewers via embedding need no licence |
| Purchasing route | M365 admin centre / EA (monthly/annual) | Azure portal (hourly, reserved, or MACC) |
| Pause capability | No — P-series runs continuously | Yes — A-series can be paused/resumed via API |
| Compute equivalence | P1 ≈ A4, P2 ≈ A5, P3 ≈ A6 | Same underlying infrastructure |
| MACC eligible | No — not an Azure service | Yes — counts against Azure MACC |
| Deployment dataflows | Supported | Supported |
| Paginated reports | Supported (P1+) | Supported (A4+) |
| AI features (Q&A, Insights) | Full Premium AI features | Standard only (Premium AI requires P-series) |
The practical conclusion: for enterprise internal analytics deployments where you want all M365-licenced users to access Power BI reports without individual Pro licences, P-series Premium is the right vehicle. For ISV product embedding, customer-facing analytics portals, and Azure-native deployments where pause/resume reduces cost, A-series Embedded is the right vehicle. Most enterprises running at scale need both: P-series for internal staff and A-series for external customer or partner reporting.
Common Power BI Embedded Licensing Mistakes
Mistake 1: Over-Sizing the A Node
The most common error is purchasing an A3 or A4 node for a workload that an A1 or A2 would handle. Over-provisioning Embedded capacity is expensive — each tier doubles in price. Before sizing, profile your actual concurrent user count and model complexity. A simple set of cached reports for 400 users with low concurrency (not all 400 accessing simultaneously) is well within A1 capacity. The same 400 users with live DirectQuery connections and complex DAX calculations may require A3.
Mistake 2: Running A-Series Without Auto-Pause
Leaving A-series capacity running 24/7 when reports are only accessed during business hours is one of the clearest Power BI cost optimisation opportunities. Implement auto-pause via Azure Automation runbooks or Logic Apps. The 10–15 minutes it takes to implement auto-pause pays back in the first month.
Mistake 3: Using A-Series for Internal Staff Reporting When P-Series Is More Economical
If your primary use case is eliminating Pro licences for internal staff who view reports but do not create them, P1 Premium capacity (approximately £3,200/month at EA pricing) eliminates Pro licence requirements for all tenant users. At 500+ internal viewers, P1 Premium breaks even with Pro licences and provides a cleaner internal deployment model than A-series. Reserving A-series for external/customer workloads while using P-series for internal creates the most efficient combined deployment.
Mistake 4: Forgetting the Author Licence Overhead in ISV Scenarios
ISV developers building Power BI Embedded applications often overlook that developers who use the Power BI REST API to push datasets, publish reports, or manage workspaces need Power BI Pro or Premium Per User licences. In a development team of 10 developers each with a £8.40/month Pro licence, the authoring overhead is £84/month — negligible. But for larger development teams or teams that did not budget for Pro licences, this can be an unplanned cost.
Negotiating Power BI in Your EA
Power BI Pro is included in M365 E3 and E5, making the standalone Pro licence irrelevant for enterprises with broad E3/E5 deployment. The EA negotiation scenarios for Power BI centre on Premium and Embedded capacity.
For Power BI Premium (P-series), negotiate the capacity as part of your broader Power Platform commitment. A P1 capacity commitment alongside a Power Apps per-user commitment positions you as a serious Power Platform customer and gives Microsoft commercial incentive to discount the package. Standalone P-series capacity negotiated independently typically achieves only 5–10% discount; bundled with Power Apps and Power Automate commitments, 15–25% is achievable.
For A-series Embedded on Azure, the correct negotiation vehicle is your Azure MACC. If you are negotiating a MACC increase to improve EA pricing for Azure services broadly, include explicit language that A-series Embedded counts toward MACC consumption. This is standard — A-series is an Azure service — but confirming it in the MACC amendment eliminates any dispute during true-up.
The Power BI Premium capacity guide covers the P-series commercial mechanics in detail, and the Power Platform licensing complete guide provides the broader context for Power BI in the Power Platform portfolio.
Frequently Asked Questions
Can external users access Power BI Embedded reports without any Microsoft licence?
Yes — with A-series Embedded capacity. External users accessing reports embedded in your application via A-series capacity do not need Power BI Pro or any other Microsoft licence. The capacity licence pays for the computational resources to render and serve the reports; end-user licensing is not required for consumers. This is the primary commercial case for A-series in ISV and customer-portal scenarios.
What is the difference between Power BI Embedded and Power BI Premium Per User (PPU)?
Premium Per User (PPU, £18.70/user/month) provides premium Power BI capabilities on a per-person basis — large dataset support, paginated reports, AI features — for individual power users and analysts. Embedded A-series provides capacity-based compute for deployment at scale without per-user licensing for viewers. PPU is for power users who need advanced authoring and analysis features; Embedded is for high-volume report consumption scenarios where per-user licensing is uneconomic.
Does Power BI Embedded A-series count against my Azure MACC?
Yes. Power BI Embedded A-series is an Azure resource that counts toward Azure MACC consumption. If your organisation has an Azure MACC with underspend, A-series Embedded can be allocated against that commitment at no incremental cash cost. This makes A-series particularly attractive for organisations with MACC surplus — the effective cost may be zero in the short term.