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?
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.