Power BI Embedded vs Power BI Service - Which Licensing Model
Power BI licensing is one of those topics that should be straightforward but isn't. Microsoft offers multiple licensing models, and choosing the wrong one can cost your organisation tens of thousands of dollars per year in unnecessary spend - or leave you hitting frustrating limitations.
The most common question we get from Australian businesses is whether to use Power BI Service (per-user licensing) or Power BI Embedded (capacity-based licensing for external-facing scenarios). The answer depends on who your users are, how they'll access analytics, and what you're trying to achieve.
Let me break this down clearly.
The Fundamental Difference
Power BI Service is for internal business intelligence. Your employees log in with their Microsoft 365 accounts and view reports. Each user needs a licence.
Power BI Embedded is for embedding analytics into your own applications. Your customers, partners, or external users access reports through your software without needing their own Power BI licences.
That's the core distinction. Everything else flows from it.
| Power BI Service | Power BI Embedded | |
|---|---|---|
| Primary audience | Internal employees | External users via your application |
| Authentication | Azure AD / Microsoft 365 | Your app handles authentication |
| Licensing model | Per user | Per capacity |
| Users need Power BI licence? | Yes | No |
| Reports accessed via | Power BI portal, Teams, SharePoint | Your custom application |
| Development effort | Low - standard Power BI publishing | Higher - requires app development |
| Best for | Internal BI and reporting | SaaS products, customer portals, partner reporting |
Power BI Service Licensing Options
Power BI Pro (~$15.10 AUD/user/month)
The standard licence for internal BI. Every user who creates or consumes shared Power BI reports needs at least this.
Includes:
- Create and publish reports
- Share reports and dashboards
- Access reports in the Power BI web portal, Teams, and mobile app
- 1 GB maximum dataset size
- 8 daily data refreshes per dataset
Best for: Organisations with under 500 Power BI users where datasets fit within 1 GB.
Watch out for: The 1 GB dataset limit catches people off guard. Once your data model exceeds 1 GB (which happens faster than you'd think with multiple data sources), you need Premium.
Power BI Premium Per User (PPU - ~$30.20 AUD/user/month)
PPU gives individual users access to Premium features without buying a full capacity.
Includes everything in Pro, plus:
- 100 GB maximum dataset size
- 48 daily data refreshes per dataset
- Deployment pipelines
- Paginated reports
- AI features
- XMLA endpoint access
- Dataflows Gen2
Best for: Smaller teams (under 200 users) that need Premium features like large datasets, more frequent refreshes, or paginated reports.
Watch out for: PPU content can only be shared with other PPU users. If you have 10 report builders on PPU and 200 viewers, those viewers also need PPU licences to view the content. This makes PPU expensive at scale.
Power BI Premium Per Capacity
Capacity-based licensing for internal use. Instead of paying per user, you buy a block of compute capacity.
| SKU | Approximate AUD/Month | v-Cores | Memory | Max Dataset Size |
|---|---|---|---|---|
| P1 | ~$7,200 | 8 | 25 GB | 25 GB |
| P2 | ~$14,400 | 16 | 50 GB | 50 GB |
| P3 | ~$28,800 | 32 | 100 GB | 100 GB |
Includes everything in PPU, plus:
- Unlimited viewers (viewers only need a free Power BI licence)
- Autoscale capability
- Multi-geo deployment
- Larger deployment pipelines
- Advanced workload management
Best for: Organisations with 500+ report consumers. The break-even point versus Pro licensing is approximately:
- P1 capacity (
$7,200/month) vs 475+ Pro users ($15.10 x 475 = ~$7,173/month)
If you have more than 500 consumers, Premium Per Capacity is almost certainly more cost-effective.
Microsoft Fabric Capacity
Fabric is Microsoft's unified analytics platform that includes Power BI. Fabric capacity (F SKUs) provides Power BI Premium equivalent capabilities as part of a broader data platform.
| SKU | Approximate AUD/Month | Equivalent To |
|---|---|---|
| F2 | ~$400 | Entry level, limited PBI Premium features |
| F4 | ~$800 | Basic Premium features |
| F8 | ~$1,500 | Equivalent to F8, good for small teams |
| F64 | ~$7,200 | Equivalent to P1 |
| F128 | ~$14,400 | Equivalent to P2 |
Why this matters: If you're planning to use Microsoft Fabric for data engineering, data science, or real-time analytics alongside Power BI, buying Fabric capacity is more cost-effective than separate Power BI Premium and data platform subscriptions.
Power BI Embedded Licensing
Power BI Embedded is a different beast entirely. It's designed for ISVs (independent software vendors) and organisations that want to embed Power BI analytics into their own applications for external users.
How Embedded Licensing Works
Instead of per-user licences, you buy Azure capacity (A SKUs) that your application uses to render reports. Your external users don't need any Microsoft licence - they authenticate through your application.
| SKU | Approximate AUD/Hour | Approximate AUD/Month | v-Cores |
|---|---|---|---|
| A1 | ~$1.50 | ~$1,100 | 1 |
| A2 | ~$3.00 | ~$2,200 | 2 |
| A3 | ~$6.00 | ~$4,400 | 4 |
| A4 | ~$12.00 | ~$8,800 | 8 |
| A5 | ~$24.00 | ~$17,600 | 16 |
Prices are approximate AUD. A SKUs are billed hourly through Azure, so you can pause capacity when not in use to save costs.
The Key Advantage - No Per-User Cost for External Users
This is why Embedded exists. If you have a SaaS product with 10,000 users who all need to see analytics, buying Power BI Pro licences would cost ~$151,000/month. With Embedded, you might pay $4,400-$8,800/month for an A3 or A4 capacity, depending on concurrent usage.
The trade-off is development effort. You need to build the application layer that authenticates users, manages row-level security, and renders Power BI reports within your UI.
When to Choose Embedded
You should use Power BI Embedded when:
You're building a SaaS product that includes analytics as a feature. Your customers see reports within your application, branded with your look and feel.
You have a customer or partner portal where external users need to see data specific to them. For example, a logistics company providing shipping analytics to their clients.
You have a large number of external users who would be prohibitively expensive to licence individually.
You want white-label analytics. Embedded allows you to remove Power BI branding and present reports as a native part of your application.
Your external users don't have Microsoft 365 accounts and you don't want to require them to create ones.
You should NOT use Power BI Embedded when:
All your users are internal employees with Microsoft 365 accounts. Power BI Service with Pro or Premium licensing is simpler and cheaper.
You don't have development resources to build and maintain the embedding application. Embedded requires custom code (typically JavaScript/TypeScript with the Power BI REST API).
You have a small number of external users. If you're sharing reports with 20 partner contacts, giving them guest access via Azure AD B2B with Pro licences is simpler and cheaper.
Real-World Scenarios from Australian Businesses
Scenario 1 - Internal BI for a Mid-Sized Company
Situation: An Australian professional services firm with 300 employees wants company-wide analytics - financial reporting, project tracking, resource utilisation.
Recommendation: Power BI Pro for all 300 users at ~$4,530/month. Their datasets are under 1 GB, they don't need paginated reports, and 8 daily refreshes are sufficient.
Why not Premium? At 300 users, Pro is cheaper than a P1 capacity (~$7,200/month). They'd need approximately 475+ users for Premium to break even.
Scenario 2 - Large Enterprise with Heavy BI Usage
Situation: An Australian retailer with 2,000 employees, 800 of whom access Power BI reports. They have large datasets (15+ GB) and need row-level security across 60+ stores.
Recommendation: Power BI Premium Per Capacity (P1) at ~$7,200/month, with free Power BI licences for the 800 viewers. Only report builders need Pro licences (included for creators in Premium).
Why not PPU? 800 users x $30.20/month = ~$24,160/month. P1 is dramatically cheaper and handles the large dataset requirements.
Scenario 3 - SaaS Product with Customer Analytics
Situation: An Australian SaaS company wants to embed analytics into their platform. They have 5,000 customers who need to see dashboards showing their usage data and performance metrics.
Recommendation: Power BI Embedded with an A3 or A4 capacity ($4,400-$8,800/month depending on concurrent user load). The development team builds the embedding layer into their existing web application.
Why not Service? 5,000 external users x $15.10/month = $75,500/month. Embedded is an order of magnitude cheaper and doesn't require customers to have Microsoft accounts.
Scenario 4 - Partner Portal with Limited External Access
Situation: An Australian distributor wants to share sales analytics with 30 key supplier partners.
Recommendation: Power BI Pro with Azure AD B2B guest access. Invite partners as guest users in Azure AD and assign them Power BI Pro licences. Total cost: 30 x $15.10 = ~$453/month.
Why not Embedded? For 30 users, the development cost of building an embedded application far exceeds the licensing savings. B2B guest access is simple and cost-effective.
Hybrid Scenarios - Using Both
Some Australian organisations need both models. A common pattern:
- Power BI Service for internal employees (finance, sales, operations teams)
- Power BI Embedded for customer-facing analytics in their product or portal
Microsoft supports this. You can use the same Power BI reports and datasets for both internal and embedded scenarios, though the capacity management is separate.
Important consideration: If you're using Premium Per Capacity (P SKUs) for internal BI, you can also use that capacity for embedding - you don't need separate A SKUs. This can be more cost-effective if you have significant internal and external usage.
Common Licensing Mistakes We See
1. Buying Premium Too Early
Organisations buy P1 capacity (~$7,200/month) when they have 100 users. Pro licensing for 100 users costs ~$1,510/month. They're spending nearly 5x more than needed because someone told them they need "Premium features."
Fix: Start with Pro. Upgrade to Premium when you have 400+ users or genuinely need large datasets, paginated reports, or deployment pipelines.
2. Using Embedded for Internal Users
We've seen organisations try to use Embedded (A SKUs) for internal BI to avoid per-user licensing. This violates Microsoft's licensing terms and creates unnecessary technical complexity.
Fix: Embedded is for external users in your application. Internal users should use Power BI Service with appropriate per-user or capacity licensing.
3. Ignoring Microsoft 365 E5 Inclusions
Power BI Pro is included with Microsoft 365 E5. We've walked into client environments where the IT team was purchasing separate Pro licences for users who already had E5 subscriptions.
Fix: Audit your Microsoft 365 licensing before buying any Power BI licences. You might already have what you need.
4. Overprovisioning Embedded Capacity
Embedded capacity is based on concurrent usage, not total users. If you have 5,000 registered users but peak concurrent usage is 200, you don't need capacity for 5,000 simultaneous renders.
Fix: Start with a smaller A SKU, monitor actual usage, and scale up as needed. A SKUs can be scaled through the Azure portal, so you're not locked in.
How to Choose - Decision Flowchart
Step 1: Are your users internal employees or external (customers/partners)?
- Internal: Go to Step 2
- External: Go to Step 4
Step 2: How many internal users will consume Power BI content?
- Under 400: Power BI Pro (~$15.10/user/month)
- 400-500: Calculate whether Pro or Premium is cheaper
- Over 500: Power BI Premium Per Capacity (P1+)
Step 3: Do you need Premium features (large datasets, paginated reports, deployment pipelines)?
- Yes and under 200 users: Premium Per User ($30.20/user/month)
- Yes and over 200 users: Premium Per Capacity
- No: Pro is sufficient
Step 4: How many external users?
- Under 50: Azure AD B2B with Pro licences
- 50-500: Evaluate Embedded vs B2B based on development cost
- Over 500: Power BI Embedded (A SKUs)
Step 5: Are you also building a data platform?
- Yes: Consider Microsoft Fabric capacity (F SKUs) which includes Power BI Premium equivalent
Getting Licensing Right with Team 400
We're Power BI consultants who help Australian businesses choose and implement the right licensing model. Licensing decisions aren't just about cost - they affect your architecture, security model, and user experience.
As Microsoft AI and BI specialists, we understand the full Microsoft licensing ecosystem including Microsoft Fabric, Azure AI, and the broader Microsoft 365 ecosystem. We'll help you find the most cost-effective licensing structure for your actual needs - not the one that generates the highest licence revenue.
Need help figuring out the right Power BI licensing model for your organisation? Get in touch and we'll review your situation. No charge for an initial licensing consultation.
Explore our services or learn about our broader AI consulting offerings for Australian businesses.