Azure Functions: Java 25 end of support

Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.

• Notification phase: the Functions team emails you about retirements that affect your function apps.
• Retirement phase, after the end-of-life date: apps on Java 25 can still be created and deployed, and they continue to run.
• They get no new features, security patches, or performance optimizations until upgraded.
• If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.
• Apps on an unsupported version must upgrade before receiving support.

1. Follow Update language stack versions in Azure Functions. The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must migrate to the isolated worker model.
2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.
3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.
4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See Migrate your apps to the Flex Consumption plan. The update article also states that you can't change the Python version when the function app runs in a Consumption plan.
5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.
6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.