App settings reference for Azure Functions
App settings in a function app contain global configuration options that affect all functions for that function app. When you run locally, these settings are in environment variables. This article lists the app settings that are available in function apps.
There are several ways that you can add, update, and delete function app settings:
The Application Insights instrumentation key if you're using Application Insights. See Monitor Azure Functions.
Optional storage account connection string for storing logs and displaying them in the Monitor tab in the portal. The storage account must be a general-purpose one that supports blobs, queues, and tables. See Storage account and Storage account requirements.
For performance and experience, it is recommended to use APPINSIGHTS_INSTRUMENTATIONKEY and App Insights for monitoring instead of AzureWebJobsDashboard
true means disable the default landing page that is shown for the root URL of a function app. Default is
When this app setting is omitted or set to
false, a page similar to the following example is displayed in response to the URL
true means use Release mode when compiling .NET code;
false means use Debug mode. Default is
A comma-delimited list of beta features to enable. Beta features enabled by these flags are not production ready, but can be enabled for experimental use before they go live.
The path to the root directory where the host.json file and function folders are located. In a function app, the default is
Specifies the repository or provider to use for key storage. Currently, the supported repositories are blob storage ("Blob") and the local file system ("Files"). The default is blob in version 1 and file system in version 2. Note that in version 1 file system will only work for functions running in an app service plan.
The Azure Functions runtime uses this storage account connection string for all functions except for HTTP triggered functions. The storage account must be a general-purpose one that supports blobs, queues, and tables. See Storage account and Storage account requirements.
Path to the compiler used for TypeScript. Allows you to override the default if you need to.
Valid values are "readwrite" and "readonly".
The version of the Functions runtime to use in this function app. A tilde with major version means use the latest version of that major version (for example, "~2"). When new versions for the same major version are available, they are automatically installed in the function app. To pin the app to a specific version, use the full version number (for example, "2.0.12345"). Default is "~2". A value of
~1 pins your app to version 1.x of the runtime.
The language worker runtime to load in the function app. This will correspond to the language being used in your application (for example, "dotnet"). For functions in multiple languages you will need to publish them to multiple apps, each with a corresponding worker runtime value. Valid values are
For consumption plans only. Connection string for storage account where the function app code and configuration are stored. See Create a function app.
For consumption plans only. The file path to the function app code and configuration. Used with WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. Default is a unique string that begins with the function app name. See Create a function app.
The maximum number of instances that the function app can scale out to. Default is no limit.
This setting is a preview feature - and only reliable if set to a value <= 5
Default is "8.11.1".
Enables your function app to run from a mounted package file.
Valid values are either a URL that resolves to the location of a deployment package file, or
1. When set to
1, the package must be in the
d:\home\data\SitePackages folder. When using zip deployment with this setting, the package is automatically uploaded to this location. In preview, this setting was named
WEBSITE_RUN_FROM_ZIP. For more information, see Run your functions from a package file.