Forum Discussion
HTTP Custom Action in SharePoint and OneDrive
I've just seen Chris McNulty's blog post around the licensing changes coming to Flow in Feb 2019 and am a little confused by one of the statements in the post.
Effective February 1, 2019, the following capabilities will only be available with PowerApps and Flow Plan 1 and Plan 2:
- Creation and publication of custom connectors in PowerApps and Microsoft Flow
- HTTP custom actions integrated into Flow outside SharePoint and OneDrive
- Integration of on-premises data through the on-premises data gateway
Does this mean that if I author a Flow that is triggered from/by a SharePoint library by clicking the flow link in the library, then the HTTP Custom Action is available to call any webservices (including my own Azure functions) or is it just the HTTP request into SharePoint that will be available to use SharePoint REST services?
Tagging Jon Levesque
- Brian CaauweIron Contributor
I'm pretty sure that is not the case. I believe the specific call out for SharePoint and OneDrive is because there is a native action called "Send an HTTP request to SharePoint". This action is NOT going to require P1/P2 licensing but the generic HTTP action will require additional licensing from what I understand.
- Yes, Brian is correct, the Http stand alone connector is going to turn premium. They did state however that you only need to be licensed for the flow creator and anyone using the flow itself doesn't need to be licensed so that's a relief cause if anyone using it needed P1 that would frustrating :).
I guess I'd have liked to see greater clarity in the original blog post around that point, perhaps by calling the action out by name. I know there's a lot of clients using flow today that have fallen back on the HTTP Custom Action for SharePoint to call an PowerShell code in an Azure Function specifically to address areas that Flow was/isn't able to do.
To do this going forward we'll need to ensure those people creating the Flow have the P1, so not a major problem but clients will ask why are we being charged for this now?
- Brian CaauweIron ContributorFor Azure Functions you should look at using a queue trigger instead of an HTTP trigger as that works without the HTTP action, and using Azure Automation actions for PowerShell anyway