Skip to main content

MS Flow and PowerApps Licensing changes

Licensing for MS Flow and PowerApps changed on October 1st. I was not sure how my clients are going to be affected by the changes and had to do a little digging. These changes were apparently discussed during Inspire 2019, back in July 2019.

 The licensing page previously displayed the version packaged with Office 365 E3/E5 license and the Plan 1 and Plan 2. If you go to the plan page now (https://flow.microsoft.com/en-us/pricing/), you will not see the version packaged with Office 365. There is no longer Plan 1 and Plan 2 either. Instead there is Per User Plan and Per Flow Plan. Per User Plan starts at $15/user/month while the Per Flow Plan starts at $500/month (for 5 flows). It appears pretty steep especially if you were using Plan 1 previously. 

 The Flow and Power Apps that we used to have as part of Office 365 licensing is, thankfully, still intact. The pricing site does not mention that though. This "Microsoft PowerApps and Microsoft Flow Licensing Guide" (PDF download) mentions the version included under "Seeded flow" through Office 365. The good part with this change is that there are no longer any limits such as maximum number of runs per month, or Maximum Flow frequency etc. There are limits in the form of Daily API Requests which are maxed to 2000. This 2000 limit is across Flow and PowerApps. If you are using PowerApps and Flow extensively, you need to be wary of this limit now. There is also limits on CDS (Common Data Service) capacities. Connectors are limited to Standard Connectors, which includes Office 365, SharePoint Exchange, Box etc, which should be sufficient for most scenarios. However, if you are connecting to on-premises sources (custom connectors), then you need to upgrade to Per User or Per Flow license. See the table below, a copy/paste from the download:

Flow use rights included with Office 365 licenses

Office 365 licenses include Flow use rights for the purpose of customizing and extending Office 365 applications. 
Flow use within Office 365 is limited to the context of the embedding Office 365 application. For both triggers and actions, Flows included within the Office 365 application can connect to:
•       Any data source within the use rights of the Office 365 application
•       Directly with the Office 365 application (via built in trigger/action)

If the embedded Flow is not within the context of the Office 365 application or if the embedded Flow needs to connect to a premium on-premises or custom data source standalone Flow licenses will need to be purchased. 

Summary of Flow use rights with Office 365 licenses

Plans and capabilities

Flow use rights within  Office 365 licenses
Execute Flows1
Workflows
Unlimited1
Business process flows
-
Connect to your data
Standard connectors
⚫
Premium connectors
-
On-premises data gateway
-
Custom connectors
-
Store and manage data
Common data service use rights
-
Per license capacity
Daily API Requests1
2,000

1 Usage capacity is across both PowerApps and Flow; “PowerApps and Flow capacity add-on” can be purchased to increase daily service limits. More details at http://aka.ms/platformlimits

I am not really sure if this simplifies any more than what was in place before. As I read the licensing guide, I have a lot of questions. Maybe some of them will be answered during Ignite. There sure will be some ruckus there though. I have seen people not liking this new model. Those who were using Plan 1 will be affected. Those who were using Plan 2, will not feel much from the change. There is a FAQ for the licensing, PowerApps and Microsoft Flow licensing FAQs, which might help.

 For your benefit, including the pictures below of the new licensing model followed by the old licensing model:


Pic 1: New MS Flow licensing model



Pic 2: Old MS Flow licensing model

Comments

Post a Comment

Popular posts from this blog

AADConnect: Attribute-based Filtering

As a hands-on practice area lead, I get to deliver projects both directly as an architect, and indirectly as an Engagement Manger. In one recent project, one of my Higher Ed clients wanted to setup attribute-based filtering. The matter got escalated to me and I helped the client in setting this up. I documented the process to my client and thought there may be others who may find this helpful as well. In this article I will not be going into what  AADConnect  is and how to deploy the same. I will assume that you already know about  AADConnect  and possibly have deployed the same as well. One of the features of  AADConnect  is the ability to filter objects that are synched to Azure AD. The default and the recommended configuration are to sync all objects in all domains in the configured forest. There are cases, however, that requires us to filter the objects to be synched.  AADConnect  provides the following filtering options: Group-base...
Post a Comment
Read more

Office 365 access: Enforcing VPN with ADFS

Recently, I was asked for possible solutions to enforce VPN connection to access Office 365. This seems odd at first, for this is against one of the tenets of Office 365, accessing service from anywhere and on any device. But then there is always a certain use case that needs to be addressed. In this case, the customer had deployed Office 365 and federated using ADFS, a textbook deployment with 2 ADFS server farm, and 2 WAPs in the DMZ. Within the Microsoft 365 world, Intune and Conditional access would enable for enforcing policies. However, that will also require the customer to acquire additional licenses beyond O365 E3, which my customer did not want to do. I compiled some of the possibilities with ADFS to enforce VPN connectivity. Although I do not recommend anyone to bypass the features, I want to share this out to get some feedback from the community, to see if this is such a common scenario, or if anyone implemented any of these or other cost-effective solutions...
Post a Comment
Read more

Promoted Links - Wrap and size tiles with Client Side Rendering

SharePoint 2013 introduces Promoted Links list and the web part is unbelievable hit with my client users. Anyone who has seen it wants it in their team/portal sites. With increase in usage comes new requirements. And so the requirement did come, for reducing the size of promoted link tiles just so it fits into a web part zone of a custom page layout that was being used. User was adding 3 tiles and the third tile was displayed only partially and a header with scroll buttons was displayed for navigation. Users would prefer to see full 3 tiles in the row. If there are more than 3 items in the list, then they would prefer that the tiles be wrapped to the next row.    Picture below shows out of the box Promoted Links output. There are 6 items in the list. Notice that the Green tile is truncated: To display the 3 full tiles in a row within the web part zone required that the tile size be reduced. Promoted links are rendered using Client Side Rendering ...
10 comments
Read more