Azure Functions Runtime Support
Track Azure Functions language runtimes, hosting plans, end-of-support dates, and deprecation timelines. Know when your serverless functions need updating before runtimes are dropped.
5
Languages
15
GA Runtimes
3
In Preview
6
EOL in 2026
Supported Language Runtimes
All runtimes on Azure Functions v4.x. Dates from Microsoft documentation.
.NET
Latest LTS. Recommended for new projects.
STS release, extended to 24 months. Last version for Linux Consumption plan.
LTS. In-process model ends Nov 10, 2026. Migrate to isolated worker.
Long-term .NET Framework support. Windows-only.
Java
Preview. EOL set when GA is declared.
LTS. Last version for Linux Consumption plan.
LTS. Widely deployed.
LTS. Still supported via Microsoft Build of OpenJDK.
Temurin support. Consider upgrading to 17 or 21.
Node.js
Current release. Preview on Azure Functions.
Active LTS. Last version for Linux Consumption plan.
Maintenance LTS. Approaching end of support.
Approaching end of support. Plan your upgrade now.
Python
Preview. Remote build support not yet available.
Current stable. Recommended for new projects.
Widely deployed.
Stable.
Approaching end of support.
PowerShell
LTS. Last version for Linux Consumption plan.
Hosting Plans
Compare Azure Functions hosting options: scaling, billing, and capabilities.
Scaling
Event-driven, up to 1,000 instances
Billing
Pay-as-you-go (per execution)
Memory
512 MB / 2 GB / 4 GB
Timeout
30 min (HTTP), unlimited (non-HTTP)
Recommended for new apps. Always-ready instances for reduced cold starts. Replaces Linux Consumption for new language versions.
Scaling
Event-driven, auto-scale
Billing
Pay-as-you-go (per execution)
Memory
1.5 GB
Timeout
5 min default, 10 min max
Linux Consumption frozen: no new features or language versions after Sep 2025. Windows Consumption unaffected. Migrate to Flex Consumption.
Scaling
Event-driven with pre-warmed workers
Billing
Per-second based on vCPU/memory
Memory
3.5 / 7 / 14 GB
Timeout
60 min default, unlimited
No cold starts. Custom Linux images. Best for continuous or near-continuous workloads.
Scaling
Manual or auto-scale rules
Billing
Standard App Service pricing
Memory
App Service plan-dependent
Timeout
Unlimited
Predictable billing. Run alongside web apps. Full compute isolation available.
Scaling
Event-driven via KEDA
Billing
Per-second based on vCPU/memory
Memory
Configurable
Timeout
Configurable
Run function apps as containers on Azure Container Apps. Microservices integration.
Deprecation Timeline
Upcoming end-of-support dates and required migration actions.
| Item | End of Support | Countdown | Action Required |
|---|---|---|---|
| Linux Consumption (new features) | 30 Sep 2025 | Ended 157d ago | New language versions on Flex Consumption only |
| Node.js 20 | 30 Apr 2026 | 2 months | Upgrade to Node.js 22 or 24 |
| Functions Runtime v1.x | 14 Sep 2026 | 6 months | Migrate to runtime v4.x |
| Python 3.10 | 1 Oct 2026 | 7 months | Upgrade to Python 3.11+ |
| .NET In-Process Model | 10 Nov 2026 | 8 months | Migrate to isolated worker model |
| PowerShell 7.4 | 10 Nov 2026 | 8 months | Await newer PowerShell support on Flex Consumption |
| .NET 8 LTS | 10 Nov 2026 | 8 months | Upgrade to .NET 10 |
| .NET 9 STS | 10 Nov 2026 | 8 months | Upgrade to .NET 10 |
| Java 8 (Temurin) | 30 Nov 2026 | 9 months | Upgrade to Java 17 or 21 |
| Linux Consumption (hosting) | 30 Sep 2028 | 2.6 years | Migrate to Flex Consumption plan |
Frequently Asked Questions
Common questions about Azure Functions runtimes, hosting, and migration.
Which Azure Functions hosting plan should I choose?
What happens when a language runtime reaches end of support on Azure Functions?
What is the difference between the in-process and isolated worker models for .NET?
Why is Linux Consumption plan being retired?
How do I migrate from Azure Functions runtime v1.x to v4.x?
Which language versions are the last supported on Linux Consumption?
Related Pages
Data sourced from Microsoft Azure Functions documentation. Last updated: 6 Mar 2026.