Skip to content

Commit dd8c8be

Browse files
Update articles/azure-functions/migrate-version-3-version-4.md
Co-authored-by: Glenn Gailey <[email protected]>
1 parent 110eb71 commit dd8c8be

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/migrate-version-3-version-4.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Azure Functions version 4.x is highly backwards compatible to version 3.x. Most
1616
>
1717
> After the deadline, function apps can be created and deployed from your CI/CD DevOps pipeline, and all existing apps continue to run without breaking changes. However, your apps are not eligible for new features, security patches, and performance optimizations. You'll get related service support once you upgraded them to version 4.x.
1818
>
19-
>End of support for these runtime versions is due to the ending of support for .NET Core 3.1, which is required by these older runtime versions. This requirement affects all Azure Functions runtime languages (e.g .NET, Python, node.js, PowerShell etc).
19+
>End of support for these runtime versions is due to the ending of support for .NET Core 3.1, which is required by these older runtime versions. This requirement affects all [languages supported by Azure Functions](supported-languages.md).
2020
>
2121
>We highly recommend you migrating your function apps to version 4.x of the Functions runtime by following this article.
2222
>

0 commit comments

Comments
 (0)