Azure Functions 4.0 and .NET 6 support are now generally available

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

The Azure Functions team is excited to announce the general availability (GA) of Azure Functions 4.0. This is the latest release of Azure Functions that supports: .NET 6, Node.js 14, Python 3.7-3.9, Java 8 & 11, PowerShell 7.0, and other languages and runtimes using custom handlers.

 

The rollout of Azure Functions 4.0 GA is underway. See the end of this post for progress updates.

 

General availability of .NET 6 support

 

Today is the GA release of .NET 6. The .NET 6 support in Azure Functions 4.0 is also generally available today.

 

Azure Functions joins Azure Web Apps and Azure Static Web Apps who also announced .NET 6 support today.

 

For .NET, Azure Functions supports both in-process and isolated (out-of-process) execution models. Choose in-process if you are upgrading from .NET Core 3.1 Azure Functions or if you are looking for features, such as Durable Functions, that are currently only available to in-process apps. Isolated function apps provide more control of the function worker process and greater compatibility with libraries. For more information and to learn more about the .NET roadmap for Azure Functions, read our blog post from earlier this year.

 

To learn more, join our session at .NET Conf—"Serverless .NET 6 with Azure Functions"—streaming live on November 10 at 20:30 UTC (12:30 PST) and available on-demand following the conference!

 

Try Azure Functions 4.0 today

 

To deploy a new Azure Functions 4.0 app, try a quickstart for your favorite language in Visual Studio Code or Visual Studio 2022.

 

To migrate an existing app and learn what’s new, see the Azure Functions documentation.

 

Azure Functions 4.0 availability and known issues

 

Azure Functions 4.0 is generally available in all regions on Linux.

 

For Windows, deployment is underway and is expected to complete by the end of this week. For deployment progress and known issues, please refer to this wiki.

 

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.