Found the issue. For anyone who runs across this or similar problem with an HTTP-Triggered Azure function in the future it may be because you are running the function in isolated worker mode. If so you must change the footprint of the function to look for an HttpRequestData object rather than an HttpRequest object in the Run parameters and return a HttpResponseData object like this:
[Function(nameof(myHttpTriggeredFunction))]
public static HttpResponseData Run([HttpTrigger(AuthorizationLevel.Anonymous, "post")] HttpRequestData req, FunctionContext executionContext)
{
// processing code here
}
There are no solutions, only trade-offs.
- Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes)