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're using the Consumption plan, instances of the Azure Functions host are dynamically added and removed 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. To avoid disruptions, migrate your existing Consumption plan apps that run on Linux to the Flex Consumption plan before that date. Apps running on Windows in a Consumption plan aren't affected by this change. For more information, see the Linux Consumption plan retirement notice.
The Consumption plan scales automatically, even during periods of high load. When running functions in a Consumption plan, you're charged for compute resources only when your functions are running. On a Consumption plan, a function execution times out after a configurable period of time.
Tip
The Flex Consumption plan is now the recommended serverless hosting plan for Azure Functions. It offers faster scaling, reduced cold starts, private networking, and more control over performance and cost. For more information, see Flex Consumption plan.
Billing
Billing is based on number of executions, execution time, and memory used. Usage is aggregated 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.
Create a Consumption plan function app
When you create a function app in the Azure portal, the Consumption plan is the default. When using APIs to create your function app, you don't have to first create an App Service plan as you do with Premium and Dedicated plans.
In Consumption plan hosting, each function app typically runs in its own plan. In the Azure portal or in code, you might also see the Consumption plan referred to as Dynamic or Y1.
Use the following links to learn how to create a serverless function app in a Consumption plan, either programmatically or in the Azure portal:
You can also create function apps in a Consumption plan when you publish a Functions project from Visual Studio Code or Visual Studio.
Multiple apps in the same plan
The general recommendation is for each function app to have its own Consumption plan. However, if needed, function apps in the same region can be assigned 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.