Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
When you use the Consumption plan, the Azure Functions host dynamically adds and removes instances based on the number of incoming events.
Important
After 30 September 2028, the option to host your function app on Linux in a Consumption plan is retired. Apps running on Windows in a Consumption plan aren't affected by this change.
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
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.
Multiple apps in the same plan
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.