The Webinar version of the live talk on Licensing updated to reflect latest information and comments from the licensing article recently posted and in progress in SP Docs
<THIS FILE HAS BEEN UPDATED. PLEASE LOOK FOR THE LATEST PRESENTATION WITH THIS NAME THANKS>
https://www.slideshare.net/RalphRivas2/understanding-power-platform-licensing-march-2020-webinar/RalphRivas2/understanding-power-platform-licensing-march-2020-webinar
2. 2
»Session Goals
› Understand the cost nuances in the various scenarios and combinations
› Apply what we learned (select scenarios on the webinar)
»What Is in Scope
› Power Apps, Power Automate (core)
› Power Virtual Agents (new)
About this session
3. 3
»Ralph Rivas
› Microsoft Aficionado since 198<redacted>
› MCP 1613
› Consultant since 2000, Magenic since 2002
› Accidental SharePoint Guy since 2003
› Solution Architect by Day, Dad/Entertainer by night
› Collaboration Evangelist (read Office 365 Fan)
› On the Mentoring path …
About Your Speaker
4. 4
How about you …?
Where you are coming and what you want
from this session makes a difference
5. 5
» Official License information from Microsoft
itself is the baseline
› For Power Automate (formerly Flow)
− https://us.flow.microsoft.com/en-
us/pricing/
› For Power Apps (formerly Power
Apps)
− https://powerapps.microsoft.com/e
n-us/pricing/
› For Power Virtual Agents (new!)
− https://powervirtualagents.microso
ft.com/en-us/
› The Key document is a PDF
Download
− https://go.microsoft.com/fwlink/?lin
kid=2085130
First let Microsoft speak …
6. 6
»Pricing is separate from the licensing information
› Not meant to confuse you or force you to look at several places but …
› … allows for pricing to be targeted to its region
»The main pricing links hide the nuances
› … and there are many so understand before selecting
»Pricing can also be found in your Office Admin site
› https://admin.microsoft.com/Adminportal/Home#/catalog (and search “Power”)
› The result may not match the documentation exactly!
− Older plans are represented (for now)
− There may be regional nuances
− Always make sure you check your regular licenses to see what you already have included
About these links and the document
7. 7
»What is your License program or …
»How do you buy Power Platform services?
»Do you know your TAM or Microsoft Rep?
Before diving in, things to look at
8. 8
»Volume
› EA
› EAS
› Service and Cloud Enrollment (SCE)
› Education (EES)
»Other
› MO Government
› MPSA
› MOSPWeb Direct
› Region specific programs
»Who’s your Rep?
Licensing Program Options – which one do
you have?
11. 11
Power Apps – What you get
»“Run Single Apps” – Per User/Per App/Per Month at $10
› Individual users run specific applications
› Considered the “Standalone” license
»“Run Unlimited Apps” – Per User/Per Month $40
› Users can run unlimited apps
»Seeded Power Apps – Bundled with Office 365 and Dynamics 365
› No extra cost but there are limits on the Power Automate side
› For Customizing or Extending Office 365 and Dynamics 365
− E.G. Provisioning SharePoint Online Sites or Lists
12. 12
Power Apps Per App Plan – What else do you get for $10 extra
a month
This is considered the “low entry point” for limited users and apps
13. 13
Power User Plan – What else do you get for $40 extra a month
Remember this is for “unlimited” custom applications
14. 14
Power Apps with Dynamics 365 – an overlap flavor
Unlike the previous ones, this is for accessing capabilities in Dynamics 365 only!
16. 16
Power Apps incl. with Office 365 – what’s out of box!
In the same spirit as Dynamics 365, these would be for working with Office 365 Apps, e.g. SharePoint, Teams
17. 17
What counts as O365 Licenses which get the “free” Power Apps
ability
18. 18
The Connectors – Appendix B calls out recent changes to
Premium!
Let’s look at those connectors: https://us.flow.microsoft.com/en-us/connectors/?filter=&category=all
If you must have a Premium Connector, you will need a Per App or Per User Plan (and this is a big
deal!)
19. 19
»A recent Power App resource with licensing much like a web portal
application
»This is not a SharePoint Web Site and it is its own system
»Quick Survey – do we want to see what you get with this?
› Let’s just see it in the document either here together and quickly discuss or
you can review directly
What about that Power App Portal
23. 23
Power Automate – What you get
»“Per User Plan” – Per User/Per Month at $15
› Individual users CREATE unlimited flows
› Considered the “Standalone” license
»“Per Flow Plan” – 5 Flows Per Month $500 ($100 for each addl.)
› Implement(!) Flows with “reserved capacity”
› Serve “unlimited users” (this is in bold in the document!)
› Also considered a “Standalone” license
»Seeded Flow – Bundled with Office 365 and Dynamics 365
› No extra cost but limits discussed previously
› For Customizing or Extending Office 365 and Dynamics 365
− E.G. Provisioning SharePoint Online Sites or Lists
24. 24
»Limits
› Older plans had monthly limit
while the new plan is about daily
limits
› Both allowed for “additional
capacity” to be added but in the
former, it was for the month
while in the latter it is for the day
»The price
› New “entry” point is $15
› Promotes Heavy use, penalizes
casual use
Some differences from Last Year’s plans
Old Plans
26. 26
»Important for the Per Flow plan
»Flows that count:
› Scheduled flows
› Automated flows
› Instant flows
› Business process flows
»Remember it is $100 per additional Unit in the Per Flow Plan
»Purchasing “units” is not the same as purchasing capacity” which is
available as an add on cost
»Child Flows are those triggered by another flow does NOT need
additional licenses!
Concept: Enabled Top Level Flows
27. 27
What do you get for $15/$500 per month plans
Note the connectors, CDS and Daily Limits versus the difference in “Basics”
28. 28
»In the old way, the Power Apps license effectively included the Flow
license though not the other way around. You paid for things “once” if
the starting point is Power Apps
»In the new way, the only “Free” use of Power Automate (flows)
consists of:
› Flows that are limited to the context of the Power App e.g. Built in Power App
Trigger/action to send the app a push notification
› Flows that are completely unrelated to the app (e.g. updates to a DB, does not
talk back to the app, etc.) require the Power Automate license …
− … unless that flow is included in the context of Office 365 or Dynamics
»As long as it runs in the context, a lot can be done
Power Automate with Power Apps
30. 30
»This works in the exact same way as within Power Apps but where
the context is Dynamics 365 which we looked at earlier.
Power Automate and Dynamics 365
31. 31
»There is an important distinction here from the previous plans and
bundles in that Office 365 capabilities are very basic and leave out
major components that may force the purchase of the per user or per
app plans
Power Automate and Office 365
32. 32
»Automated Flow Trigger
› Triggered by webhook or polling event
› Examples: SharePoint created/updated; Exchange email received.
»Instant Flow Trigger
› Triggered by the “current user”
› Examples: "Flow Button“; "Power Apps Trigger“; "SharePoint For Selected
Item"
Usage Guidance – Understanding Trigger
Types
33. 33
»Use Standard Connectors whenever possible
»Automated Triggers
› Flow Owner gets full license (service account or Flow Bundle)
› Watch Number of Runs (API capacity purchases possible)
»Instant Triggers
› Each user needs a license
› Seeded apps (Office 365 of Dynamics) do NOT need a license
› Power App Trigger would need a license for itself and negate need for Flow
license
Usage Guidance – Flow
37. 37
»$1,000 a month whether you use it or
not.
»“Unlimited Flows” – as with the
previous cases in Power Automate,
these are only for flows triggered by
PVAs
»2,000 Chat Sessions – Each time
someone “talks” to the Bot, counts as
one session.
› More on this coming up
»May be stacked (by more “capacity” at
$1k per license)
Power Virtual Agents (PVAs) – What you get
38. 38
»A session is an interaction between the customer and the bot and
represents one unit of consumption.
»The session begins when an authored topic is triggered.
»These sessions are referred to as ‘billed sessions’ in the product.
»Sessions are deducted for both testing and production usage.
»A session ends in one of the following scenarios:
› When all the customer's questions are answered
› When a customer intentionally ends or closes a chat session
› When a bot is unable to answer adequately, and the interaction is escalated to
a live agent
What is a Session? (According to the doc …)
39. 39
»As discussed earlier, there is the ability to “add on” to gain Capacity.
»For Power Apps
› Portal Login – 100 daily logins per month @ $200
› Portal Page Views – 100,000 Page views per month @ $100
› AI Builder – Each “Unit” at $500 per month
− https://powerapps.microsoft.com/en-us/ai-builder/
− Unit = 1 million service credits
− Also an Add-on to Power Automate
Add-ons
* Service Credits is a “currency” that is deducted at different rates for various scenarios
(e.g. Forms processing, prediction, etc.) . Without a rate sheet, it is a case of seeing how
much you use during a trial or pilot to determine how many “units” to get
44. 44
»Start simple to learn …
»5000 people and a SharePoint List
› Trigger is automated (approval flow)
› Connector used is Premium (Call to Graph API)
»How many licenses do we need?
»Just 1 premium license!
Time to look at a scenario
45. 45
»Individual Citizen Developer makes two Flows
»Office 365 E3
»20 users have permissions to use the form
»SharePoint form triggers Flow 1
»Flow 1 calls Flow 2 (talks again to GRAPH API REST e.g. HTTP)
»How many licenses do we need?
»Again Just 1 premiumfull license
»Can also be a “Service Account” for the license.
Look at another one to learn from
46. 46
»Office 365 Freebie
› Last year dozens of people out of a 10k sized org made flows and apps to
their hearts content (power users)
› 100’s of Flows
› Few of them ever ran so never hit the 750 Runs max capacity
› None of the apps where promoted to others in any formal fashion and it is
mostly just personal productivity at the time
Let’s apply what we know so far … another
case
47. 47
»The Flow Runner – critical business application
› Last year had only 3 flows but they ran heavily requiring them to have Plan 2
for capacity
› Would sometimes hit the daily or monthly limit requiring purchase of additional
capacity (but only on peak periods)
› Connected to A SQL Database for updates etc.
› Hundreds of users all over the globe using it daily
How about yet another …
48. 48
»The One App Shop
› Status Reporting App talked to a Database because the creator who is also a
former developer understood SQL better than SharePoint
› Inconsistent use of between 20 and 40 Project managers at any time, once a
week
› 1000 people in the tenant who are mostly unaware that Power Apps or Power
Automate even exist
› Developers use actual Azure AI for bots (PVA just out) in Teams built during
quiet times or special initiatives
»Got one to share? There is an article you can contribute to!
› https://github.com/bigpix2000/microsoft-365-
community/blob/master/Community/powerplatformlicensingforcitizendeveloper
.md
OK, one more and then …
49. 877.277.1044 / magenic.com // 49
THANK YOU
Ralph Rivas
Principal Consultant/Architect
Collaboration Evangelist
SAFe 4 certified
https://www.cloudtalkshowcom
Chicago Power Platform User Group
Twitter: @bigpix2000
https://www.linkedin.com/in/ralphrivas/
Hinweis der Redaktion
If possible, an online survey otherwise quick discussion on perspectives
As a money person
As the “IT” person
As a citizen developer
As the businessperson in charge of it all (but is it not about the money)
PVA too new to have its own pricing page --- Live Demo to visit these pages and open the document. Note the date of the PDF!
The costs could be whole different or potentially capabilities not available. If there is interest, discuss Service Levels (SL’s!!) and Multiplexing issues where some people ask if a flow is scaled out on multiple devices etc. OR if licenses are needed when talking to SQL server, etc. (CALs)
These can make a difference and note you may have other
Using the varying definitions of things in the document when you see Quotes
THIS IS RUN SPECIFIC APP not CREATE APP … so someone else makes an app for you to use you will pay to RUN IT!
Watch time on this slide!
TAKE CARE HERE NOT TO SPEND MORE THAN 2 MINUTES! RIGHT AWAY CLICK FOR THE ARROWS TO SHOW HIGHLIGHT ITEMS.
Take a Moment to explain what the items here are e.g. what is a PORTAL, what is a Canvas versus Model Driven App, What is a Standard versus Premium Connector, What is the Common Data Service and then discuss the “footnotes” 1, 2, 3 1 - An entity within Common Data Service becomes restricted only if the Dynamics 365 application is installed on a given environment 2 - Service limits are published at http://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits 3 - Common Data Service database and file capacity entitlements are pooled at the tenant level Note: • Embedded canvas apps within a model-driven app will not count towards the two-app limit. • A single user might be covered by multiple ‘per app’ licenses to allow the user to use multiple solutions targeted at various business scenarios, without requiring a per-user license • Once a pool of Power Apps per app licenses are purchased, individual licenses need to be assigned to specific environments and to individual users (i.e. if the same app exists in two environments, a user would require two per app SLs to access both). • The Power Apps Per App plan is available to education customers under faculty and student pricing. Since these licenses are sold as tenant level capacity and not assigned to users in active directory, customers and partners will be responsible for ensuring that student pricing is only being applied to students. This means that when licenses are purchased with student pricing, the number of app licenses assigned to non-students (i.e. faculty) in the product may not exceed the number of faculty licenses purchased as this would indicate that student licenses have been assigned to faculty.
1 - An entity within Common Data Service becomes restricted only if the Dynamics 365 application is installed on a given environment
2 - Service limits are published at http://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits
3 - Common Data Service database and file capacity entitlements are pooled at the tenant level
Watch time on this slide! (2 minutes MAX) Explain Blank in apps cell 1 with footnote 1 items quickly!
1 - Dynamics 365 Sales Professional, Dynamics 365 Customer Service Professional, Dynamics 365 Team Members, Dynamics 365 Operations – Activity, Dynamics 365 Human Resources Self Service, Dynamics 365 Business Central Team Members 2 - Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Commerce, Dynamics 365 Human Resources, Dynamics 365 Business Central 3 - Power Apps and Power Automate usage will count against the API request limits provided by the Dynamics 365 license Service limits are published at http://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits
A slide for Appendix B Coming up and stand by because this is what makes it either great or a great pain!
Notice all the blanks!!
Notice the Model Driven App is NOT included!!
No portals, no CDS!
1 - Common Data Service database and file capacity entitlements are pooled at the tenant level
2 - Reference http://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
Calling out SQL server which I see most often used and now will cost
Show premium versus standard from the drop down .
If you need a premium you MUST get a per app or per user plan!!!!
Notice they are calling it “Flow”
It’s not a case of running here but the case of CREATING them!
Microsoft says the former when applied through the whole org (yikes, $15 additionally for everyone) will mean near zero admin overhead (but headache for the license folks paying) … The latter is where a “power user” is designated to create the flow and “shares” to a designated group such that a regular user could not trigger a flow by accident.
The point here is there is a perception that it is “better” in the new way because you have more power daily and you will not hit your limits during the month when you may need it the most. If you are high volume, you would have had to buy extra capacity often.
1 - Reference http://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
2 - Additional Common Data Service Database/File/Log capacity can be purchased in increments of 1GB. Common Data Service Database and File capacity are pooled tenant wide.
Note, scheduled flows may be configured to trigger every minute, irrespective of license type. There are no limits on the frequency of flow runs beyond what the connector supports.
1 - Power Automate use needs to map to the context of the embedding Power Apps applications 2 - Power Automate usage counts against the service limits associated with the embedding Office 365 license. Please review http://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits
Note the limitations
Notice they are calling it “Flow”
Discuss the use cases integrating with Apps (Canvas in progress) and Flow (connectors already there but not part of this talk)
Get these in the Admin Center
SHOW OFF VERY QUICKLY CHAT SESSION WITH SALES PDF!
Simply put, if 5000 people write to a SharePoint list and there is a SharePoint automated trigger that runs a premium flow license, only 1 premium license is required on that flow.
In one more example, given that a citizen developer creates two Flows (Flow 1 and Flow 2) in an Office 365 E3 environment using a SharePoint form to trigger the first flow (Flow 1) and given that the flow uses the HTTP connector to trigger the second flow (Flow 2 e.g. Graph API REST call) where there are 10 users with permissions to run the form, only the author of the flow needs to have the premium\full license rather than a license for each of the 10 SharePoint form users. It this was an approval workflow where a step included approvals, the people approving would also not need licenses as the flow is considered a single instance through its completion and is, in effect, already paid for.
Minimize Time here (2 minutes max!)
Minimize time here and focus on add-on costs being the equalizer
Minimize time here and get to user scenarios OR jump straight if time is less than 5 minutes!!!
