Next in our PowerPlatform Licensing simplification
We tackle the various “capacity based” licenses and “add-ons” of our Lowcode Platform.
Next in our #PowerPlatform #Licensing simplification effort; we tackle the various “capacity based” licenses and “add-ons” of our #Lowcode Platform.
Open Diagram
Open Post:
Kym Dupuis on LinkedIn: Power Platform Licensing Simplified - Capacity and Add-Ons | 23 comments
If you missed Monday’s post, the link in the first comment.
I often refer to the Power Platform as an hybrid between #SaaS and #PaaS. While most people are familiar with assigning a SaaS user license to individual employees (Like #Office365 and #Dynamics365), there are many situations where a capacity based model typically found in PaaS (like the #Azure #Cloud) brings additional flexibility to larger scale initiatives or when sharing common resources like #AI and #Storage is needed.
More over, it allows #IT and #Business decision makers to better manage their initial investment in a new platform and add capacity when needed or even switch business model entirely as #adoption grows in the organization. We will look at how to leverage the the various licensing model and maximise ROI next week.
So about the chart below; a lot has been left out for simplicity sake. Summarizing products with so many differences in their capabilities and business models is challenging. A link to the full licensing guide is included at the top for reference.
The #PowerApps per App plan is often a good option for organizations where adoption is still low and/or in areas of the business where there is a lot of employee turnaround or seasonality (retail and manufacturing first line workers). It’s a capacity that is allocated per environment and does not require #ITadmins to manage individual user licenses in the Office 365 portal. Once a user opens the app, he only consumes 1 capacity. After 30 days, the capacity is returned to the environment for the next user.
#PowerAutomate per #Flow is a good fit for departmental flows where the process is identical for all users but where assigning a per user license to each employee becomes prohibitive or adds management complexity (Expense reports, Employee Onboarding, Vacation requests, ITSM, etc). Many flows I observe in production in customer environments should run on this model instead of the seeded and per user models as it does not impact the flow owner Daily Platform Requests Capacity it also augments the Tenant Platform Requests Daily Capacity. It’s a 2 birds on stone options that saves money and virtually eliminate any risk of a flow to throttle.