In this blog post, we are outlining and describing a comprehensive guide to understand the Power Platform licensing and make it more approachable. I spent a lot of time dissecting the licensing details, trying to provide some common use cases and decision points. I hope you will find this guide useful.
This guide is updated as of November 2020, including the latest announcements and changes coming from the PowerApp for Teams (Formerly known as Project Oakdale, now Dataverse for teams).
As is the case with Microsoft licensing, you often need a Ph.D. in quantum physics to make sense of this maze of products and the interaction between products. Many readers may think PowerApps and PowerAutomate are part of Office 365 and, therefore, free to use. While this is true for some scenarios, it isn’t if you want to take advantage of the numerous advanced features of the platform. This blog post is based on the Microsoft Power Platform licensing guide, which you can find at this link. (Warning, it is about 28 pages). To better understand the licensing and its complexity, it is essential to remember that the Power Platform originated from the Microsoft Dynamics product group and was later adapted and integrated into Microsoft Office 365. A good history of the capabilities and how it became the Power Platform can be found in this blog post from James Phillips, President of Microsoft Business Applications.
The Power Platform is Microsoft’s low code, no code platform that answers the need to rapidly create powerful business applications, analyze data, automate processes and create virtual agents all in one platform to meet today’s business challenges. At the core of the platform are several products:
Microsoft’s strategy for Office 365 has always been to provide a comprehensive platform to allow ease of use and customization. As a result, Microsoft includes as part of Office 365, some of the capabilities found in the Power Platform. If you are licensed for Office 365 (Business or Enterprise plan), you get the following capabilities included as part of your license.
Most of you may ask, why would I need more? This depends on your needs. You will often require additional licenses if you need to use an App or Flow that requires a premium connector. Since 2019, Microsoft reclassified the connectors, and now most of the more advanced connectors have been classified as Premium. (Example: includes any connection that requests an API or call to a web service, SQL connectors, Dynamics connectors and Azure connectors). So how do you decide? If your Application or Flow needs to connect to data stored in Office 365, in most cases, you will be ok with the seeded licenses. Still, any time you will need to connect to a system outside of Office 365, you will need to consider purchasing additional licenses (more to come below).
There is, however, one exception, if you are building an app with the new Dataverse for Teams, calling API from this app is now included.
So, when you find yourself needing more, below is a guide to more advanced scenarios.
Power BI licensing, unlike the other component of the Microsoft Power Platform, is straightforward. Power BI comes in 3 editions:
PowerApps licensing has changed many times over the past three years. Unfortunately, it is more complicated than ever. So PowerApps comes with three distinct user interfaces:
So, if you are in need to buy licensing for PowerApps because you need larger capacity, require a premium connector, need to build a model driven application (instead of just Canvas apps), need to build a portal or just a more complex application, you must purchase PowerApps licensing. PowerApps premium licenses are available in 2 versions.
Like PowerApps, you may find yourself needing more than the seeded use rights you get with Office 365. Power Automate can be extended to add more capacity, higher limits, and access to premium connectors. Here is how it works:
But hang-on, how about an application built with PowerApps that triggers a flow. Microsoft has a solution for this, and in this case, licensing PowerApps allows the use of a flow as long as the flow is executed in the context of the application. (Don’t ask me what this means because I am not quite sure how this is going to be enforced). This is covered in more detail in the Power Automate Licensing guide on Page 13 – Power Automate user rights included in Power Apps licenses.
So, when do you need per attended with attended RPA? This is only required if you plan to leverage the new UI Flows, aka Robotic Process Automation flow that leverages the new Power Automate Desktop (formerly known as WinAutomation).
Lastly, regarding building flow, there is also another option in leveraging Azure Logic Apps; few of you may know that Azure Logic Apps share the same engine in the backend and, for the most part, have the same capabilities. Except Logic Apps only costs you on a per consumption basis, which depending on your flow, maybe very cost-efficient (Note: you can export a Flow from Power Automate to Logic Apps and vice versa).
Power Virtual Agent, “PVA,” does have a seeded version for Office 365 users except for Dataverse for Teams, which includes the right for PVA. If you want to use Power Virtual Agent, be aware of the licensing requirements. It comes in 2 editions:
AI Builder is a great service component that allows infusing AI into your Applications and Flows. AI Builder is included in the Power Automate with attended RPA flow or can be purchased additionally.
While you think we are done, there are a few more things to cover.
If your organization is licensed for Dynamics 365, there is some good news. Dynamics 365 comes with user rights for Power Automate and Power Apps; this means you can potentially build additional applications and complex flows without the need to purchase additional licenses and even deploy a portal as long as the applications are created within the context (again, don’t ask me what this means and how this is enforced) of the Dynamics application and located in the same environment.
I am a big fan of the Microsoft Power Platform. Over the past few years, I have helped countless organizations leverage this platform’s power to deliver rapid and innovative applications that drive better business outcomes. To ensure that you aren’t surprised, I recommend that you first gain a deep understanding of your needs and business objectives before jumping and building your applications – this may save you some surprises at the end that may drive up the cost.
Stay tuned for my next post, where I will expand on the capabilities of Microsoft Dataverse for Teams.