Action recommended: Update your Azure Functions apps to use runtime version 4.x

Question

Action recommended: Update your Azure Functions apps to use runtime version 4.x

MikeUrnun 9,777 Moderator

Following the retirement of .NET 3.1 on 3 December 2022, Azure Functions runtime versions 2.x and 3.x will go out of support on the same date.

After that date, your applications that are hosted on Functions will continue to run and your existing workloads will not be affected. However, we'll no longer provide patches or customer service for applications running on runtime version 2 or 3. Update your Functions applications to runtime version 4.x.

Upgrading to runtime version 4.x provides these benefits:

Security updates to your Functions applications
Support for the latest programming languages e.g. .NET 6 and Node 16

Accepted answer

2 additional answers

Your answer

Answer 1

MughundhanRaveendran-MSFT 12,506

Recommended action:

To avoid potential service disruptions or security vulnerabilities, update your Functions applications to runtime version 4.x, before 3 December 2022.

Help and support:

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, please create a support request:

Under Issue type, select Technical.
Under Subscription, select your subscription.
Under Service, select My services.
Under Service type, select Function App.
Under Resource, select your application.
Under Summary, type a description of your issue.
Under Problem type, select Configuring and Managing Function Apps.
Under Problem subtype, select Updating Function App Language Version.

Sebastian Rodales 6 Reputation points

2022-06-13T21:01:24.973+00:00

Hi,

I don't see runtime version 4, only see 3 in my Functions.

What can I do to make it appear?

Thanks.
Michael Enright 1 Reputation point Microsoft Employee

2022-06-13T21:35:27.987+00:00

Hello,

I received this notice for my Azure subscription, but I do not have any Azure Function apps in that subscription. Therefore I am not sure what action I need to take. Is there a way I can determine which specific resources are flagging as out of compliance so that I can take the appropriate action?

Thanks
(adm) PROETI NUNES Thiago 1 Reputation point

2022-06-13T22:36:39.803+00:00

Hello,

I received this communication

"On 3 December 2022, .NET Core 3.1 will be retired. As a result, Azure Functions runtime versions 2.x and 3.x, which use .NET Core 3.1, will also be retired on that date."

Can you please clarify? These Azure Functions will be retired as well or only be unsupported?

Thanks,
Thiago Proeti Nunes 6 Reputation points

2022-06-13T22:42:50.89+00:00

Hello colleagues,

I received this communication

"On 3 December 2022, .NET Core 3.1 will be retired. As a result, Azure Functions runtime versions 2.x and 3.x, which use .NET Core 3.1, will also be retired on that date."

"Your Functions applications that use runtime version 2.x or 3.x will continue to run and your existing workloads won't be affected. "

Can you please clarify? These Azure Functions will be retired as well or only be unsupported?

Thanks,
Jack C Tang (RD-TW) 1 Reputation point

2022-06-14T07:25:20.357+00:00

Hi,
Does the change affect Linux premium and consumption based function apps? If so, should we specify LinuxFxVersion for using 4.x runtime by following this section: https://learn.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal#manual-version-updates-on-linux? Currently we're using "PYTHON|3.8" for "LinuxFxVersion" and please would you let us know what value should we use for 4.x runtime? Thanks.
Stefanus Hinardi 16 Reputation points

2022-06-14T16:35:41.62+00:00

Hello,

To update to V4, FUNCTIONS_EXTENSION_VERSION app setting should be set to ~4 and you can set LinuxFxVersion to the same value as before.

Thanks
Stefanus Hinardi 16 Reputation points

2022-06-14T16:38:39.13+00:00

Hello,

You should expect that the app will still run but won't be eligible for new features, security patches, and performance optimizations.

-Stefanus
Stefanus Hinardi 16 Reputation points

2022-06-14T16:38:54.807+00:00

Hello,

You should expect that the app will still run but won't be eligible for new features, security patches, and performance optimizations.

-Stefanus
Thiago Proeti Nunes 6 Reputation points

2022-06-14T19:32:54.26+00:00

Thank you for clarifying this Stefanus.
test-se 6 Reputation points

2022-06-15T02:42:20.99+00:00

＠StefanusHinardi-3920

Let me ask you a question.

We are using Java, not .NET Core 3.1.
We would like to check if we need to update to version 4.x even if we are using Java.

Am I correct in assuming that Java will continue to support new features, security patches, and performance optimizations in version 2.x and version 3.x?
Jack C Tang (RD-TW) 1 Reputation point

2022-06-15T07:12:30.893+00:00

Hi,

But in this document: https://learn.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal#view-and-update-the-current-runtime-version, it says "This section doesn't apply when running your function app on Linux." So I thought changing "FUNCTIONS_EXTENSION_VERSION" is not for Linux?
Stefanus Hinardi 16 Reputation points

2022-06-15T16:29:53.247+00:00

@test-se ,

Unfortunately, you still need to update. The function runtime host is written in .NET 3.1, which reaching its EOL in December. So, even for the java apps, it is highly recommended to update to v4.

-Stefanus
Stefanus Hinardi 16 Reputation points

2022-06-20T23:54:08.73+00:00

Hello,

It seems that the doc is not clear for Linux vs Windows. I am working on an update to clarify,

But overall, in order to upgrade to v4 and not "pin" the app to a specific runtime minor version i.e. 4.0.4, Linux app needs to update the value of "FUNCTIONS_EXTENSION_VERSION" to "~4". By doing this, the runtime would always up to date to the latest minor version of v4.

However, if you want to "pin" to a specific minor version of the runtime version, you would need to use the LinuxFxVersion.

-Stefanus

Answer 2

Here's a script to list all function apps under your subscriptions along with their runtime versions; to help folk figure out where upgrades may be required:

   powershell  
   #Requires -Modules @('Az')  
     
    # open the browser for you to authenticate  
   Connect-AzAccount  
     
   # Loop through subscriptions listing all functions under those.  Outputs to console (change `ft -AutoSize` to `export-csv -Path 'c:\temp\azFunctions.csv' -Delimiter ',' -Encoding utf8` or `out-gridview` for CSV or a more interactive output format).  
   Get-AzSubscription | Where-Object{$_.State -eq 'Enabled'} | ForEach-Object{ Set-AzContext -SubscriptionId $_.Id | Out-Null; Get-AzFunctionApp | Select-Object Name, @{N='Version';E={$_.ApplicationSettings.FUNCTIONS_EXTENSION_VERSION}}, ID, OSType, Runtime} | Sort-Object Version | Format-Table -AutoSize

Answer 3

Sebastian Rodales 6

Hello partners,

I recive the same communication in reference to my Azure Suscription, the problem is that I don't see the version ~4 to set in my Azure Functions.

If Microsoft can clarify this be excellent for all of us.

Thanks in advance.

Stefanus Hinardi 16 Reputation points

2022-06-14T18:55:08.573+00:00

Hello,

What is the current language and language version that your app is using? It might be the case that the version is only supported in V3 and V4?
Sebastian Rodales 6 Reputation points

2022-06-14T20:15:11.47+00:00

Hello.

Sorry but I'm not a programmer, I'm only in charge of the infrastructure, when I received this email I commented on this change to the programmers, there the problem arose that they did not see the value 4 to make the change.

If you can guide me where I can look at these data that you ask me, I would appreciate it.

Thanks.

Share via

Action recommended: Update your Azure Functions apps to use runtime version 4.x

2 additional answers

Your answer