馃攳
How to choose your Power Automate license - YouTube
Channel: Microsoft Power Platform
[5]
in this video
[6]
we will review the various power
[8]
automate license entitlements
[10]
the different types of power automate
[12]
licenses and how to choose the right
[14]
license
[16]
let's first go over the different power
[18]
automate license entitlements
[20]
connectors represent the app or service
[22]
that you want to connect to like
[24]
sharepoint teams or onedrive
[28]
connectors are categorized by standard
[30]
or premium
[32]
standard connectors are included in
[33]
office 365 subscriptions
[36]
an additional license is required for
[38]
premium connectors
[41]
custom connectors allow you to
[43]
communicate with apps or
[44]
services that do not already have a
[47]
pre-built connector
[49]
the on-premise gateway allows power
[52]
automate to reach back to an on-premise
[54]
resource
[55]
like microsoft sql servers in your
[57]
organization
[58]
to support hybrid integration
[62]
another license entitlement is business
[64]
process flows
[66]
which guide your users through a
[68]
multi-stage business process
[70]
flow they provide a streamlined user
[73]
experience to help ensure that data is
[75]
captured consistently
[77]
and at the same steps are followed each
[80]
time
[82]
some licenses grant access to dataverse
[85]
a low code no code
[87]
data platform designed for the power
[90]
platform
[91]
other licenses grant access to ai
[94]
builder
[94]
to train and configure ai for your flows
[98]
and robotic process automation to
[101]
automate
[102]
your repetitive desktop processes
[105]
finally all licenses grant a number of
[108]
api requests per day
[110]
for each user api requests are made when
[113]
using connectors
[115]
http actions and using built-in actions
[118]
like variables
[121]
now let's take a look at the different
[123]
types of power automate licenses
[125]
and what power automate entitlements
[127]
other office 365 licenses will grant you
[132]
power automate per flow enables
[134]
organizations to implement flows with
[137]
reserved capacity that serve teams
[139]
departments
[141]
or the entire organization without
[143]
having to license
[144]
each end user instead of
[147]
licensing the flow the power automate
[150]
per user license
[151]
equips a user to run an unlimited number
[154]
of flows
[156]
for users that need ai builder and
[158]
robotic
[159]
process automation there is the power
[161]
automate per
[162]
user with a tended rpa plan
[167]
for those that need additional api
[169]
requests each day
[171]
use the power automate capacity add-on
[176]
now power automate rights are seated
[178]
with other microsoft licenses that you
[180]
may already own
[181]
for example all office 365 licenses
[185]
allow flows that use standard connectors
[188]
these same rights are also granted to
[190]
non-business
[191]
microsoft accounts such as those ending
[193]
with outlook.com
[197]
dynamics includes the following power
[200]
automate license entitlements
[202]
but only in the context of a dynamics
[204]
application
[205]
this is also true for power app license
[208]
plans
[209]
both dynamics and powerapp licenses
[212]
grant rights to build flows
[214]
but those flows must relate back to the
[217]
app
[218]
covered by the dynamics or powerapps
[220]
license
[222]
for example a user is accessing an app
[225]
that has a dynamics or powerapp license
[227]
the application is using
[230]
a sql database if the user creates a
[235]
flow
[235]
using that sql database the flow will
[238]
require
[239]
a premium connector the dynamics or
[243]
powerapp license grants the user the
[245]
rights to use
[246]
the premium flow connector since the sql
[249]
database is being used by the app
[252]
now if the same user wants a flow
[255]
to an oracle database that is unrelated
[259]
to dynamics or the power app
[261]
then they are not licensed they'll need
[264]
a power automate per user or
[266]
per flow plan so how do you choose
[269]
between the power automate per user
[271]
and per flow licenses you need to look
[275]
at how the flow
[276]
is triggered scheduled licenses
[280]
run in the context of the flow's owner
[282]
so
[283]
only the owner of the flow needs to be
[286]
licensed
[288]
automated flows also work the same way
[290]
only the
[291]
owner of the flow is required to have a
[294]
license
[295]
a common example of an automated flow
[297]
are flows triggered by a sharepoint list
[301]
only the flow owner needs the license
[305]
for flows that are called from another
[308]
flow
[309]
the child flow will draw its licensing
[311]
from the parent
[312]
so in this example the child flow is
[315]
using a
[316]
premium connector since the parents flow
[318]
owner has a power automate per user
[321]
license
[322]
the child flow is licensed
[326]
instant flows require a power automate
[330]
per
[330]
user license for each user that triggers
[333]
the flow
[334]
in such cases instead of licensing each
[337]
user
[338]
it's sometimes easier and more cost
[341]
effective to license the flow
[343]
with a power automate per flow license
[347]
now that we've reviewed the various
[349]
power automate license entitlements
[351]
the different types of licenses and how
[353]
to choose the right license
[355]
you can start leveraging power automate
[357]
to eliminate manual processes
[359]
boost efficiency and focus attention
[362]
where it's needed most
[370]
you
Most Recent Videos:
You can go back to the homepage right here: Homepage