Azure Functions Consumption plan hosting
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. The Consumption plan is the fully serverless hosting option for Azure Functions.
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.
For a comparison of the Consumption plan against the other plan and hosting types, see function scale and hosting options.
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 the Azure Functions pricing page.
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 may also see the Consumption plan referred to as
Use the following links to learn how to create a serverless function app in a Consumption plan, either programmatically or in the Azure portal:
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 is a limit to the number of function apps that can run in a Consumption plan. Function apps in a given plan are all scaled together, so any issues with scaling can affect all apps in the plan.