If you have Azure functions running on .NET 6, it’s important to remember that support for .NET 6 ends on 12 November 2024 (details here). If your function is not many versions behind, the upgrade can be as easy as updating the function’s project target framework to .NET 8.
May need a little more than a target framework update (details here) but not as much as converting an in-process azure function to isolated.
The in-process model for .NET apps in Azure Functions will be retiring in November 2026 (details here), but if you have in-process functions running on .NET 6, you can consider eliminating two problems in one go now by converting it to isolated: Migrate .NET function apps from the in-process model to the isolated worker model | Microsoft Learn
Isolated is quite different. Not a harsh change but it is better to get used to it now than wait until the last minute.
Another exciting news is that the Azure function Flex Consumption preview is out. Flex may have what you need for a lower cost if you are hosting on premium or more power and features if your consumption host is not providing all you need. (details here)
Hosting on consumption flex is another reason to convert in-process to isolated. It is still in preview, but GA may be ready before November 26.
This is another article on Flex Consumption covering some performance testing. Glad Microsoft is providing articles like this to help understanding how Azure Functions perform: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/how-to-achieve-high-http-scale-with-azure-functions-flex/ba-p/4169736.
Leave a Reply