Expose Azure Function via API Management

When exposing an Azure Function via API Management, the most important thing to remember is that each function has a function key that can be dynamically retrieved via function listsecrets. To make the function deployment work, you will have to add an application Setting AzureWebJobsSecretStorageType=Files to your FunctionApp.

Azure Function Update

When using an old version of Azure Functions, you might run into an issue like “The WebHook verification request must contain a ‘code’ query parameter”. This means you can’t call the functionsfrom your logic app anymore. Upgrade to the latest version of Azure Functions and redeploy your logic apps. I’m not entirely sure, but things should work again.

Remote debugging Azure Functions

In a previous post we talked about debugging an Azure function in Visual Studio. You can also debug a function deployed to Azure, ie. remote debugging. There’s a few points to note: For remote debugging to work, we will have to deploy the function container in Debug mode. Next open the Azure Portal. In the Application…

Debug Azure Functions

Since July I’m doing an assignment where Azure functions are intensively used. The functions are developed in Visual Studio, which has many advantages over developing functions in the Azure Portal. In Visual Studio you have intellisense, functions can be brought under source control and you can easily debug function execution. When you develop a Http…

The ‘code’ query parameter provided in the HTTP request did not match the expected value

Occasionally I have an issue when I call an azure function from a logic app. This is the error: { “statusCode”: 400, “headers”: { “Pragma”: “no-cache”, “Cache-Control”: “no-cache”, “Date”: “Thu, 24 Nov 2016 00:32:40 GMT”, “Server”: “Microsoft-IIS/8.0”, “X-AspNet-Version”: “4.0.30319”, “X-Powered-By”: “ASP.NET”, “Content-Length”: “103”, “Content-Type”: “application/json; charset=utf-8”, “Expires”: “-1” }, “body”: { “Message”: “The ‘code’ query…