Capacity and SKUs in Power BI embedded analytics

When moving to production, Power BI embedded analytics requires a dedicated capacity (A, EM, or P SKU) for publishing embedded Power BI content.

Capacity is a dedicated set of resources reserved for exclusive use. It enables you to publish dashboards, reports, and datasets to users, without having to purchase per-user licenses. It also offers dependable, consistent performance for your content.

Note

For publishing, you'll need one Power BI Pro account.

What is embedded analytics?

Power BI embedded analytics includes two solutions:

  • Power BI Embedded - Azure offering
  • Embedding Power BI as part of Power BI Premium - Office offering

Power BI Embedded

Power BI Embedded is for ISVs and developers who want to embed visuals into their applications.

Applications using Power BI Embedded allow users to consume content stored on Power BI Embedded capacity.

Power BI Premium

Power BI Premium is geared toward enterprises who want a complete BI solution that provides a single view of its organization, partners, customers, and suppliers.

Power BI Premium is a SaaS product that allows users to consume content through mobile apps, internally developed apps, or at the Power BI portal (Power BI service). This enables Power BI Premium to provide a solution for both internal and external customer facing applications.

Capacity and SKUs

Each capacity offers a selection of SKUs, and each SKU provides different resource tiers for memory and computing power. The type of SKU you require, depends on the type of solution you wish to deploy.

Before deciding which SKU to buy, review the information in this section.

Power BI Embedded SKUs

Power BI Embedded is shipped with an A SKU.

Power BI Premium SKUs

Power BI premium offers two SKUs, P and EM.

Which SKU should I use?

This table provides a summary of features, the capacity they require, and the specific SKU that is required for each one.


Feature

Power BI Embedded

Power BI Premium

What is consumed?

What is consuming?

A SKUs
(Azure)

EM SKUs
(Office)

P SKUs
(Office)

Embed artifacts from a Power BI workspace
Power BI reports An embedded application for your organization
(user owns data)
An embedded application for your customers
(app owns data)
Power BI content
(with a free Power BI license)
Power BI service
Power BI mobile
MS Office apps

Capacity considerations

The table below lists payment and usage considerations per capacity.


Power BI Embedded

Power BI Premium

Offer

Azure

Office

SKU

A

EM

P

Billing

Hourly Monthly Monthly

Commitment

None Yearly Monthly or yearly

Usage

Azure resources can be:
- Scaled up or down
- Paused and resumed
Embed in apps, and in
Microsoft applications
Embed in apps, and
in Power BI service

SKU memory and computing power

The table below describes the resources and limits of each SKU.

Capacity Nodes Total v-cores Backend v-cores RAM (GB) Frontend v-cores DirectQuery/Live Connection (per sec) Model Refresh Parallelism
EM1/A1 1 0.5 2.5 0.5 3.75 1
EM2/A2 2 1 5 1 7.5 2
EM3/A3 4 2 10 2 15 3
P1/A4 8 4 25 4 30 6
P2/A5 16 8 50 8 60 12
P3/A6 32 16 100 16 120 24
P4 64 32 200 32 240 48
P5 128 64 400 64 480 96

Next steps