| title | Azure Functions Consumption plan hosting (legacy) | |
|---|---|---|
| description | Learn about Azure Functions Consumption plan hosting, a legacy serverless hosting option. We recommend the Flex Consumption plan for new serverless function apps. | |
| ms.date | 03/13/2026 | |
| ms.topic | concept-article | |
| ms.custom |
|
[!INCLUDE functions-consumption-legacy-banner]
When you use the Consumption plan, the Azure Functions host dynamically adds and removes instances based on the number of incoming events.
[!INCLUDE functions-linux-consumption-retirement]
The Consumption plan automatically scales, even during periods of high load. When you run functions in a Consumption plan, you pay for compute resources only when your functions are running. On a Consumption plan, a function execution times out after a configurable period of time. The Consumption plan is currently the only serverless hosting option that supports Windows.
Billing is based on the number of executions, execution time, and memory used. The system aggregates usage across all functions within a function app. For more information, see Azure Functions pricing.
To learn more about how to estimate costs when running in a Consumption plan, see Understanding Consumption plan costs.
The general recommendation is for each function app to have its own Consumption plan. However, if needed, you can assign function apps in the same region to the same Consumption plan. Keep in mind that there's a limit to the number of function apps that can run in a Consumption plan. Function apps in the same plan still scale independently of each other.
If you have existing function apps running on the Consumption plan, migrate them to the Flex Consumption plan. The Flex Consumption plan provides faster scaling, reduced cold starts, virtual network integration, and configurable instance sizes. Because the Flex Consumption plan is Linux-only, Windows Consumption plan apps must also migrate to Linux as part of this process. For step-by-step instructions, including Windows-specific guidance, see Migrate Consumption plan apps to the Flex Consumption plan.