Skip to content

Commit 54eaef4

Browse files
committed
Clean-up the set version stuff
1 parent 0508b74 commit 54eaef4

8 files changed

+16
-21
lines changed

articles/azure-functions/functions-bindings-azure-data-explorer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Azure Data Explorer bindings for Azure Functions aren't available for the v3 ver
8282
## Functions runtime
8383

8484
> [!NOTE]
85-
> Python language support for the Azure Data Explorer bindings extension is available starting with v4.6.0 or later of the [Functions runtime](set-runtime-version.md#view-and-update-the-current-runtime-version). You might need to update your installation of Azure Functions [Core Tools](functions-run-local.md) for local development.
85+
> Python language support for the Azure Data Explorer bindings extension is available starting with v4.6.0 or later of the [Functions runtime](set-runtime-version.md#pin-to-a-specific-version-on-linux). You might need to update your installation of Azure Functions [Core Tools](functions-run-local.md) for local development.
8686
8787
## Install the bundle
8888

articles/azure-functions/functions-reference-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -415,7 +415,7 @@ Support for PowerShell 7.0 in Azure Functions has ended on 3 December 2022. To u
415415
416416
### Changing the PowerShell version
417417

418-
Support for PowerShell 7.0 in Azure Functions has ended on 3 December 2022. To upgrade your Function App to PowerShell 7.2, ensure the value of FUNCTIONS_EXTENSION_VERSION is set to ~4. To learn how to do this, see [View and update the current runtime version](set-runtime-version.md#view-and-update-the-current-runtime-version).
418+
Support for PowerShell 7.0 in Azure Functions has ended on 3 December 2022. To upgrade your Function App to PowerShell 7.2, ensure the value of FUNCTIONS_EXTENSION_VERSION is set to ~4. To learn how to do this, see [View and update the current runtime version](set-runtime-version.md#view-the-current-runtime-version).
419419

420420

421421
Use the following steps to change the PowerShell version used by your function app. You can do this either in the Azure portal or by using PowerShell.

articles/azure-functions/set-runtime-version.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -101,16 +101,21 @@ Replace `<FUNCTION_APP>` with the name of your function app and `<RESOURCE_GROUP
101101
::: zone pivot="platform-windows"
102102
## Change the runtime version
103103

104-
You can change the major version of the runtime used by your function app to another supported version. Because of the potential of breaking changes, you can only change the runtime version before you've created any functions in your function app.
104+
You can change the major version of the runtime used by your function app to another supported version. You can move forward to a later major version, downgrade to an earlier supported version, or temporarily pin your app to a specific minor version.
105105

106-
> [!IMPORTANT]
107-
> Although the runtime version is determined by the `FUNCTIONS_EXTENSION_VERSION` setting, when possible you should only 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.
108-
> When you need to temporarily pin your function app to a specific minor version, it's OK to set the specific minor version by directly changing the `FUNCTIONS_EXTENSION_VERSION` setting.
106+
When setting the runtime version, keep these considerations in mind:
107+
108+
+ Although the runtime version is determined by the `FUNCTIONS_EXTENSION_VERSION` setting, when possible you should only 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.
109+
+ When you need to temporarily pin your function app to a specific minor version, it's OK to set the specific minor version by directly changing the `FUNCTIONS_EXTENSION_VERSION` setting.
110+
+ Because of the potential of breaking changes, you can only downgrade the runtime version before you've created any functions in your function app.
109111

110112
### [Portal](#tab/portal)
111113

112114
[!INCLUDE [Set the runtime version in the portal](../../includes/functions-view-update-version-portal.md)]
113115

116+
3. To pin your app to a specific minor version or downgrade a new .NET function app to version 1.x, select **Application settings** > **FUNCTIONS_EXTENSION_VERSION**, change **Value** to your required minor version or `~1` for downgrade, and select **OK**.
117+
118+
4. Select **Save** > **Continue** to apply changes and restart the app.
114119

115120
### [Azure CLI](#tab/azurecli)
116121

@@ -122,7 +127,7 @@ az functionapp config appsettings set --name <FUNCTION_APP> \
122127
--settings FUNCTIONS_EXTENSION_VERSION=<VERSION>
123128
```
124129

125-
Replace `<FUNCTION_APP>` with the name of your function app and `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<VERSION>` with either a supported major version (`~4` or `~1`) or a specific minor version you temporarily need to target.
130+
Replace `<FUNCTION_APP>` with the name of your function app and `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<VERSION>` with either a supported major version (`~4` or `~1`—.NET-only) or a specific minor version you temporarily need to target.
126131

127132
Choose **Try it** in the previous code example to run the command in [Azure Cloud Shell](../cloud-shell/overview.md). You can also run the [Azure CLI locally](/cli/azure/install-azure-cli) to execute this command. When running locally, you must first run [`az login`](/cli/azure/reference-index#az-login) to sign in.
128133

@@ -142,7 +147,7 @@ Use the following script to change the Functions runtime:
142147
Update-AzFunctionAppSetting -Name "<FUNCTION_APP>" -ResourceGroupName "<RESOURCE_GROUP>" -AppSetting @{"FUNCTIONS_EXTENSION_VERSION" = "<VERSION>"} -Force
143148
```
144149

145-
Replace `<FUNCTION_APP>` with the name of your function app and `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<VERSION>` with either a supported major version (`~4` or `~1`) or a specific minor version you temporarily need to target. You can verify the updated value of the `FUNCTIONS_EXTENSION_VERSION` setting in the returned hash table.
150+
Replace `<FUNCTION_APP>` with the name of your function app and `<RESOURCE_GROUP>` with the name of the resource group for your function app. Also, replace `<VERSION>` with either a supported major version (`~4` or `~1`—.NET-only) or a specific minor version you temporarily need to target. You can verify the updated value of the `FUNCTIONS_EXTENSION_VERSION` setting in the returned hash table.
146151

147152
---
148153

includes/functions-dotnet-supported-versions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.author: glenga
1313
Versions of the Functions runtime support specific versions of .NET. To learn more about Functions versions, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). Version support also depends on whether your functions run in-process or isolated worker process.
1414

1515
>[!NOTE]
16-
>To learn how to change the Functions runtime version used by your function app, see [view and update the current runtime version](../articles/azure-functions/set-runtime-version.md#view-and-update-the-current-runtime-version).
16+
>To learn how to change the Functions runtime version used by your function app, see [view and update the current runtime version](../articles/azure-functions/set-runtime-version.md#view-the-current-runtime-version).
1717
1818
The following table shows the highest level of .NET or .NET Framework that can be used with a specific version of Functions.
1919

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,9 @@
11
---
2-
title: include file
3-
description: include file
4-
services: functions
52
author: ggailey777
63
ms.service: azure-functions
7-
ms.topic: include
8-
ms.date: 11/26/2018
4+
ms.date: 03/26/2024
95
ms.author: glenga
10-
ms.custom: include file
6+
ms.topic: include
117
---
128

139
Use the following procedure to view and update the runtime version currently used by a function app.
@@ -17,9 +13,3 @@ Use the following procedure to view and update the runtime version currently use
1713
1. 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 `~4`.
1814

1915
:::image type="content" source="./media/functions-view-update-version-portal/functions-view-runtime-version-4.png" alt-text="Screenshot showing how to view the runtime version." border="true":::
20-
21-
1. 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.
22-
23-
1. 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.
24-
25-
:::image type="content" source="./media/functions-view-update-version-portal/functions-restart-function-app.png" alt-text="Restart your function app." border="true":::
-143 KB
Loading

0 commit comments

Comments
 (0)