Forum Discussion
HTTP Custom Action in SharePoint and OneDrive
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?
- For 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
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.
- Gotcha on the HTTP Action, what probably will happen is that one will be marked as premium and the one that actually has the SharePoint badge will not.
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.
- The SharePoint HTTP custom action isn't part of the P1 requirement.
yeah I meant the HTTP Custom Action within a SharePoint Flow to call a function that resides in Azure, so it requires the "HTTP Custom Action" not the SP version of the same.
And I'm not sure that the whole Author/Run statements we're seeing on Twitter is correct. I've seen conflicting information now where one statement says that P1 is required to both Author and RUN the flows.
