Scenario：
I want to embed content for customer with embed tokens, is there a limit to the number of embed tokens?
Analysis:
Embed for your customers can get an access token without Power BI account. If the users in your company have no Power BI account or they do not want to sign in with Power BI account, you can choose Embed for your customers.
Embed tokens with Pro or Premium Per User (PPU) license are intended for development testing, so a Power BI master account or service principal can only generate a limited number of tokens. You need to purchase a capacity to embed content in a production environment. There is no limit to the number of embed tokens you can generate when you purchase a capacity.
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.
The SKUs we usually mention are divided into three types: A SKU, EM SKU and P SKU. All of them support publishing embedded Power BI content. The A SKU provides embed capacity，EM and P SKU provide Premium capacity. However, they have big differences in payment, usage scenarios, SKU memory and computing power, etc.
The A SKU (A is for Azure) is a Platform-as-a-Service and set of APIs for those ISVs who are developing an application to enter the market. These ISVs choose Power BI as the data visualization layer of that application to add value to their own application. You can use A SKU in the following ways:
- Enable embedding of Power BI in third party applications.
- Test Premium functionality before you buy a P SKU.
- Create development and test environments alongside a production environment that uses P SKU.
You can purchase A SKU in Microsoft Azure. Additionally, Power BI Embedded can scale up and down as needed to accommodate the requirements of the ISV business model as the vendor’s application grows. The premise is that you must have capacity admin permissions in Power BI.
EM SKU covers everything contained in the Power BI Embedded A SKU. It also offers the ability to share Power BI reports within an organization through content embedding. Currently, this can be accomplished through the usage of the SharePoint Power BI web part for modern pages, or through tabs using Microsoft Teams.
There are three EM SKUs, and while the largest, EM3, can be purchased through Office 365 monthly, the smaller two (EM1 and EM2) must be purchased through Volume Licensing.
The P SKU is for Power BI Premium. Power BI Premium offers greater scale and performance for Power BI content in your organization. It offers everything that is available with Power BI, which includes everything available in the A and EM SKUs. You can embed Power BI content such as reports, dashboards and tiles, into your application. P SKUs allow free Power BI users to consumer Power BI apps and shared content, in the Power BI service. But EM Premium SKUs do not support unlimited content sharing, though they do support embedding in applications.
You can purchase P SKU in Microsoft 365 admin center, the premise is that you must be a Global administrator or Billing administrator.
The following tables display the difference between A SKU & EM SKU & P SKU.
Payment and Usage
|
|
A SKU |
EM SKU |
P SKU |
|
Offer |
Azure |
Office |
Office |
|
Billing |
Hourly |
Monthly |
Monthly |
|
Commitment |
None |
Yearly |
Monthly or yearly |
|
Usage |
1. Embed Power BI content, such as reports, dashboards and tiles, into your application. 2. Azure resources can be:
|
Embed in apps, and in Microsoft applications |
1.Embed in apps, and in Power BI service 2. Publish report, dashboards and other contents in Premium. |
Scenario
|
|
A SKU |
EM and P SKUs |
|
Embed for your customers (app owns data) |
Yes |
Yes |
|
Embed for your organization (user owns data) |
No |
Yes |
|
Microsoft 365 apps (formerly known as Office 365 apps)
|
No |
Yes |
|
Secure URL embedding (embed from Power BI service) |
No |
Yes |
SKU memory and computing power
|
Capacity Nodes |
Total v-cores |
Backend v-cores |
Frontend v-cores |
DirectQuery/Live Connection (per sec) |
Model Refresh Parallelism |
RAM (GB) |
|
EM1/A1 |
1 |
0.5 |
0.5 |
3.75 |
1 |
2.5 |
|
EM2/A2 |
2 |
1 |
1 |
7.5 |
2 |
5 |
|
EM3/A3 |
4 |
2 |
2 |
15 |
3 |
10 |
|
P1/A4 |
8 |
4 |
4 |
30 |
6 |
25 |
|
P2/A5 |
16 |
8 |
8 |
60 |
12 |
50 |
|
P3/A6 |
32 |
16 |
16 |
120 |
24 |
100 |
|
P4/A7 |
64 |
32 |
32 |
240 |
48 |
200 |
|
P5/A8 |
128 |
64 |
64 |
480 |
96 |
400 |
From the three tables above, we can see the obvious differences between SKUs. So when purchasing capacity, it is very important to distinguish their differences.
Conclusion：
The number of free embed tokens is limited, so you need purchase capacity to get more embed tokens without limitation. You can purchase the corresponding capacity according to your needs through these links below.
How to purchase Power BI Premium
Reference：
Capacity and SKUs in Power BI embedded analytics
Author: Ye Tao
Reviewer: Ula Huang, Kerry Wang
Be the first to comment