Azure Functions
Plan
Overview
| Option | Benefits |
|---|---|
| Consumption plan | Pay for compute resources only when your functions are running (pay-as-you-go) with automatic scale. |
| Flex Consumption plan | Get high scalability with compute choices, virtual networking, and pay-as-you-go billing. |
| Premium plan | Automatically scales based on demand using prewarmed workers, which run applications with no delay after being idle, runs on more powerful instances, and connects to virtual networks. |
| Dedicated plan | Run your functions within an App Service plan at regular App Service plan rates. Best for long-running scenarios where Durable Functions can't be used. Consider an App Service plan in the following situations: |
| Container Apps | Create and deploy containerized function apps in a fully managed environment hosted by Azure Container Apps. Use the Azure Functions programming model to build event-driven, serverless, cloud native function apps. Run your functions alongside other microservices, APIs, websites, and workflows as container-hosted programs. |
| ### Timeout |
| Plan | Default timeout | Max Timeout |
|---|---|---|
| Consumption plan | 5 | 10 |
| Flex Consumption plan | 30 | Unbounded2 |
| Premium plan | 304 | Unbounded2 |
| Dedicated plan | 304 | Unbounded3 |
| Container Apps | 30 | Unbounded4 |
| ### Scale | ||
| Plan | Scale out | Max # instances |
| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Consumption plan | Event driven. Scales out automatically, even during periods of high load. Functions infrastructure scales CPU and memory resources by adding more instances of the Functions host, based on the number of incoming trigger events. | Windows: 200 Linux: 100 |
| Flex Consumption plan | Per-function scaling. Event-driven scaling decisions are calculated on a per-function basis, which provides a more deterministic way of scaling the functions in your app. With the exception of HTTP, Blob storage (Event Grid), and Durable Functions, all other function trigger types in your app scale on independent instances. All HTTP triggers in your app scale together as a group on the same instances, as do all Blob storage (Event Grid) triggers. All Durable Functions triggers also share instances and scale together. | Limited only by total memory usage of all instances across a given region. For more information, see Instance memory. |
| Premium plan | Event driven. Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding more instances of the Functions host, based on the number of events that its functions are triggered on. | Windows: 100 Linux: 20-100 |
| Dedicated plan3 | Manual/autoscale | 10-30 100 (ASE) |
| Container Apps | Event driven. Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding more instances of the Functions host, based on the number of events that its functions are triggered on. | 300-1000 |
| ## References | ||
| - https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale |