How to target Azure Functions runtime versions

A function app runs on a specific version of the Azure Functions runtime. There are three major versions: 1.x, 2.x, and 3.x. By default, function apps are created in version 3.x of the runtime. This article explains how to configure a function app in Azure to run on the version you choose. For information about how to configure a local development environment for a specific version, see Code and test Azure Functions locally.

Automatic and manual version updates

Azure Functions lets you target a specific version of the runtime by using the FUNCTIONS_EXTENSION_VERSION application setting in a function app. The function app is kept on the specified major version until you explicitly choose to move to a new version. If you specify only the major version, the function app is automatically updated to new minor versions of the runtime when they become available. New minor versions shouldn't introduce breaking changes.

If you specify a minor version (for example, "2.0.12345"), the function app is pinned to that specific version until you explicitly change it. Older minor versions are regularly removed from the production environment. After this occurs, your function app runs on the latest version instead of the version set in FUNCTIONS_EXTENSION_VERSION. Because of this, you should quickly resolve any issues with your function app that require a specific minor version, so that you can instead target the major version. Minor version removals are announced in App Service announcements.


If you pin to a specific major version of Azure Functions, and then try to publish to Azure using Visual Studio, a dialog window will pop up prompting you to update to the latest version or cancel the publish. To avoid this, add the <DisableFunctionExtensionVersionUpdate>true</DisableFunctionExtensionVersionUpdate> property in your .csproj file.

When a new version is publicly available, a prompt in the portal gives you the chance to move up to that version. After moving to a new version, you can always use the FUNCTIONS_EXTENSION_VERSION application setting to move back to a previous version.

The following table shows the FUNCTIONS_EXTENSION_VERSION values for each major version to enable automatic updates:

3.x ~3
2.x ~2
1.x ~1

A change to the runtime version causes a function app to restart.

View and update the current runtime version

You can change the runtime version used by your function app. Because of the potential of breaking changes, you can only change the runtime version before you have created any functions in your function app.


Although the runtime version is determined by the FUNCTIONS_EXTENSION_VERSION setting, you should make this change in the Azure portal and not by changing the setting directly. This is because the portal validates your changes and makes other related changes as needed.

From the Azure portal

Use the following procedure to view and update the runtime version currently used by a function app.

  1. In the Azure portal, browse to your function app.

  2. Under Settings, choose Configuration. In the Function runtime settings tab, locate the Runtime version. Note the specific runtime version. In the example below, the version is set to ~3.

    View the runtime version.

  3. To pin your function app to the version 1.x runtime, choose ~1 under Runtime version. This switch is disabled when you have functions in your app.

  4. When you change the runtime version, go back to the Overview tab and choose Restart to restart the app. The function app restarts running on the version 1.x runtime, and the version 1.x templates are used when you create functions.

    Restart your function app.


Using the Azure portal, you can't change the runtime version for a function app that already contains functions.

From the Azure CLI

You can also view and set the FUNCTIONS_EXTENSION_VERSION from the Azure CLI.


Because other settings may be impacted by the runtime version, you should change the version in the portal. The portal automatically makes the other needed updates, such as Node.js version and runtime stack, when you change runtime versions.

Using the Azure CLI, view the current runtime version with the az functionapp config appsettings set command.

az functionapp config appsettings list --name <function_app> \
--resource-group <my_resource_group>

In this code, replace <function_app> with the name of your function app. Also replace <my_resource_group> with the name of the resource group for your function app.

You see the FUNCTIONS_EXTENSION_VERSION in the following output, which has been truncated for clarity:

    "slotSetting": false,
    "value": "~2"
    "slotSetting": false,
    "value": "dotnet"
    "slotSetting": false,
    "value": "8.11.1"

You can update the FUNCTIONS_EXTENSION_VERSION setting in the function app with the az functionapp config appsettings set command.

az functionapp config appsettings set --name <function_app> \
--resource-group <my_resource_group> \

Replace <function_app> with the name of your function app. Also replace <my_resource_group> with the name of the resource group for your function app. Also, replace <version> with a valid version of the 1.x runtime or ~2 for version 2.x.

You can run this command from the Azure Cloud Shell by choosing Try it in the preceding code sample. You can also use the Azure CLI locally to execute this command after executing az login to sign in.

Next steps