You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-versions.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,19 +69,14 @@ Any function app pinned to `~2.0` continues to run on .NET Core 2.2, which no lo
69
69
70
70
Azure Functions version 4.x (Preview) is highly backwards compatible to version 3.x. Many apps should be able to safely upgrade to 4.x without any code changes. Be sure to run extensive tests before changing the major version in production apps.
71
71
72
-
To migrate an app from 3.x to 4.x:
72
+
To migrate an app from 3.x to 4.x, set the `FUNCTIONS_EXTENSION_VERSION` application setting to `~4` with the following Azure CLI command:
73
73
74
-
- Set the `FUNCTIONS_EXTENSION_VERSION` application setting to `~4` with the following Azure CLI command:
74
+
```bash
75
+
az functionapp config appsettings set --settings FUNCTIONS_EXTENSION_VERSION=~4 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
75
76
76
-
```bash
77
-
az functionapp config appsettings set --settings FUNCTIONS_EXTENSION_VERSION=~4 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
78
-
```
79
-
80
-
- For Windows functionapps, the runtime requires .NET 6.0 to be enabled with the following Azure CLI command:
81
-
82
-
```bash
83
-
az functionapp config set --net-framework-version v6.0 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
84
-
```
77
+
# For Windows function apps only, also enable .NET 6.0 that is needed by the runtime
78
+
az functionapp config set --net-framework-version v6.0 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
79
+
```
85
80
86
81
### Breaking changes between 3.x and 4.x
87
82
@@ -97,6 +92,13 @@ The following are some changes to be aware of before upgrading a 3.x app to 4.x.
97
92
98
93
- Default and maximum timeouts are now enforced in 4.x Linux consumption function apps.
99
94
95
+
- Application Insights is no longer included by default in 4.x. It is now available as a separate extension.
96
+
- For in-process .NET apps, add the [Microsoft.Azure.WebJobs.Extensions.ApplicationInsights](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ApplicationInsights/) extension package to your function app.
97
+
- For isolated .NET apps:
98
+
- Add the [Microsoft.Azure.Functions.Worker.Extensions.ApplicationInsights](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.ApplicationInsights/) extension package to your function app.
99
+
- Update the [Microsoft.Azure.Functions.Worker](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker/) and [Microsoft.Azure.Functions.Worker.Sdk](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk/) packages to the latest versions.
100
+
- For other languages, a future update to [Azure Functions extension bundles](functions-bindings-register.md#extension-bundles) will include the Application Insights extension. Your app will automatically use the new bundle when it is available.
0 commit comments