[MUSIC]
>> Module 8, Power BI Embedded Analytics Licensing.
Hello, I'm Peter Myers, the course developer.
>> I am Alon Baram, a senior product manager.
>> In this video, we will describe
Power BI Embedding Analytics Licensing.
We'll compare products and
provide you with licensing guidance.
>> Licensing to embed Power BI
content depends on the scenario.
Those scenarios are "For
your organization" and "For your customer".
>> When working with the "For your organization" scenario,
all end users have a Power BI Pro license or
they have a Power BI Premium Per User (PPU) license.
The workspace must be assigned to
a capacity which is a P SKU.
>> When working with "For your customers" scenario,
the workspace is assigned to a capacity,
either P or A SKU.
For developers, it's important to
understand the trial embed tokens are
generated using Power BI Pro
or Power BI Premium Per User license,
provided strictly for evaluation or development purposes.
Trial embed tokens are not permitted
to be used for production workloads.
It is possible to use
the Power BI REST API to determine usage percentage.
>> Great. Well, now let us describe to
you the P SKU in more detail.
Power BI Premium is
a capacity-based license and there's
the one product known as the P SKU.
It includes the flexibility
to publish reports broadly across
an enterprise without requiring
recipients to be licensed individually per user.
It also delivers greater scale and performance
from a capacity in the Power BI service,
and the ability to maintain BI assets
on-premises with the Power BI Report Server.
What matters most to us in this course, though,
is that we've got this one
API surface and a consistent set of
capabilities, and access to
the latest features for embedded analytics.
>> Azure Power BI Embedded,
also known as A SKUs,
are targeted at ISVs or developers who are
building apps and want to embed visuals in those apps.
It's just the one product: A SKU.
But there are limitations.
Capacity content cannot be
consumed in the Power BI service.
Capacity content cannot be consumed by
a Power BI Free licensed user.
Capacity content cannot be shared through one click
publish to web or one click publish to SharePoint.
No license for Power BI Report Server.
The resource is managed through
Azure portal or PowerShell.
You can scale up or down.
You can have capacity admins, you can pause,
resume the service.
It's very flexible.
There is also integration with Azure Analytics.
Analyze diagnostics events to understand root causes.
>> There are six different node types,
each with their respective resources and throughput.
A1, A2, A3, A4, A5, A6.
Do note that P1, P2,
P3 are equivalent in resources in
throughput to A4, A5, A6.
We see from a virtual cores perspective is that it
ranges anywhere from one virtual core through to 32,
and they split evenly between
front-end and back-end cores.
Importantly, memory when you have
large datasets that you're hosting,
can range anywhere from 2.5
gigabytes all the way through to 100 gigabytes.
For DirectQuery and live connection throughput,
it can range from 3.75 per
second all the way through to 120 per second,
supporting much higher concurrency.
For refresh parallelism,
anywhere from one through to 24,
and this is important when you've got
import data that needs to be refreshed,
the more parallelism, the more
refreshing or the longer
refreshed durations can be supported.
Alon, well, now let's compare the A and P SKUs.
>> Let's start with A SKU.
Remember, this is the Power BI Embedded product.
You can purchase them in the Azure portal,
and it's for embedding content in apps.
The billing is hourly,
there's no commitment,
this is very important,
and it provides a unique offering,
full elasticity, scale-up, scale-down, pause,
resume, and automate everything
with ARM API using PowerShell.
>> To compare it to the P SKU,
this is the Power BI Premium product,
which is purchased in the Office 365 portal.
Its use cases extend well
beyond embedding content in apps with
the ability to share content with free users and
widely to embed in other SaaS applications,
and also to share content with Power BI
free users through the Power BI service.
It's different from the A SKU because its billing is
monthly and its commitment is monthly and yearly.
Its unique offerings include
the ability to combine embedding and apps that use
the Power BI service in the same capacity
and the Power BI Report Server license is included.
>> Let's now conclude in providing
you with licensing guidance.
Typically, enterprises buy
Power BI Premium and ISVs buy Azure Power BI Embedded.
However, there are no restrictions
on which product the customer buys.
For example, enterprises may
decide to use A SKUs if they're
only interested in building line of
business apps and embedding analytics in them,
and are not interested in
using the prepackaged Power BI service,
and we have many, many enterprises, for example.
ISVs, typically GISVs, large ISVs,
may want to use a P SKU to get
the additional benefits of
the pre-packaged Power BI service
within their organization,
as well as embed in their apps.
>> Some final guidance.
We think A1 is a good choice for many reasons.
It's competitively priced at one dollar per hour,
which could come to $720 per month.
It's ideal for evaluation, development, and test.
It's ideal to establish benchmarks when capacity sizing.
It may be suitable for apps with
small or ad hoc workloads.
It can be programmatically scaled up or
down according to known usage patterns,
and it can be paused if the app has offline periods,
in which case billing ceases.