Known issues

List of current known issues and limitations

Retrieving keys for HTTP triggered functions

Currently, it's not possible to retrieve your function's keys from the portal. As a temporary workaround, use the Azure CLI to retrieve the key:

az functionapp function keys list -g $RESOURCE_GROUP_NAME -n $FUNCTION_APP_NAME --function-name $FUNCTION_NAME -o json

Mitigating cold start

Currently, there is some cold start impacts when running .NET isolated functions in the consumption plan. To minimize cold start, deploy your app to Linux consumption.

We are working on improving cold starts for .NET isolated function apps on both Windows and Linux.

.NET Core 3.1 dependency

When targeting Azure Functions 3.0, by default, the .NET Core 3.1 SDK is required on the machine building the project. In scenarios where the underlying Azure Functions extension does not have a dependency on native libraries or platform specific assets, and this dependency is undesirable, you can change this behavior by defining the following project property: <_FunctionsExtensionTargetFramework>netstandard2.0</_FunctionsExtensionTargetFramework>