Platform upgrade for Azure Functions v2 apps coming in October 2020 #266
Description
If you received a notification email recently but have already made the change to your app, do note that we sent mails to all apps over the last 30-40 days. If you made the change after that time you can safely ignore
UPDATE (Oct 5 2020): To prevent existing applications from being impacted, we will begin the process of automatically opting out apps that are still at risk for breaking that have not either upgraded to v3 or opted out already. We will opt the apps out by changing the FUNCTIONS_EXTENSION_VERSION to ~2.0. It is worth noting by redeploying from something like an ARM template users may inadvertently opt back in if they change that setting.
On October 31, 2020, we will begin a platform upgrade for Azure Functions v2 apps that may impact your app. This upgrade will enable us to continue providing security patches at all layers of the application moving forward. The large majority of users will be unimpacted and don’t need to take any action, but a small set of apps may be using APIs in their code that will break as a result of this upgrade.
For apps that are written in Java, JavaScript, Python, and PowerShell1, there will be no impact on your application.
For the majority of applications in .NET, there will be no impact on your application. However, if you have a .NET Azure Functions v2 app with application code that leverages a .NET API that was deprecated or changed in .NET 3.1, your app will be impacted. You will need to choose to opt-out of the platform upgrade, meaning some aspects of the underlying runtime may no longer receive certain security patches after October 2020, or modify your application to be .NET Core 3.1 compatible.
We will be sending notices to subscriptions for applications that are using .NET APIs that are at risk for breaking with this platform upgrade.
If you wish to opt-out of this platform upgrade, you can do so and no changes to your application code would be required. This does mean future host releases and security patches would not be applied to these applications.
Information on how to upgrade your impacted applications or opt-out can be found here:
https://github.com/Azure/azure-functions-host/wiki/Platform-upgrade-from-Azure-Functions-runtime-v2-to-v3
If you have any questions, please use the following GitHub discussion:
Azure/app-service-announcements-discussions#175
1 If your PowerShell function is calling .NET libraries that are not .NET Core 3.1 compatible, it may be impacted.