Forum Discussion
HTTP Custom Action in SharePoint and OneDrive
Fair point and an approach I'd use now to create separation. A lot of early samples were showing the use of the HTTP Custom Action to trigger the functions.
As far as the flow, it seems that way too because when you run a flow to accept the connectors or user your user context for them etc. you would think at that point it would check if your are P1 or not. Guess we will see more clarification on this soon.
This seems a little bit of a stretch in my opinion for a basic function. Especially when we already make significant investments in higher tiered licensing packages like E5. I'm all for monetizing services, but it just seems like there are better ways to distinguish Flow services and capabilities.
I've been working to kill a 3rd party that provides similar capabilities, but this just wiped that out. To give the same capabilities (just a silly HTTP call for workflows) to our users would cause us to quadruple the investment that we are making in our 3rd party tool. Or maybe I'll dust off some SPD2013 capabilities for a while when this goes into effect.
I'd rather see it take on something like an Azure Function type model where you pay for what you use other than forcing users to pay for a "Cable" model of 100's of "premium" channels that you'll never watch when you only really want the one channel.
Also, you kinda already did a good job of "distinguishing" between services if you look at your pricing page https://flow.microsoft.com/en-us/pricing/
Dont get greedy.
Hi,
I asked the question if all users need a paying license if we are using this functionality. And the answer is YES, all users in the O365 subscription need to be in the same plan. So, ready to calculate what the cost is, and compare this to third party products that were rejected first before this was changed.
Answer I received is here https://powerusers.microsoft.com/t5/General-Flow-Discussion/Flow-licensing-question/m-p/188199#M18225
Marc
- Have you tried Azure Logic Apps?
