Managed functions that run on triggers for event-driven, short-lived workloads.
| Hosting model | FaaS |
|---|---|
| Container support | Container-compatible |
| Minimum nodes | Serverless |
| State management | Stateless or stateful (with Durable Functions) |
| Web hosting | Not applicable |
| Autoscaling | Built-in service |
| Load balancer | Integrated |
| Scale limit | 200 instances (Consumption); 1,000 (Flex Consumption) |
| Multiregion | Single region only — external router plus multiple host instances |
| Virtual network integration | Supported (App Service plan, Premium, or Flex Consumption plan) |
| Hybrid connectivity | Supported (Premium or Flex Consumption plan) |
| GPU support | Not supported |
| TLS | Supported |
| Architecture styles | Microservices, event-driven architecture |
| Required skills | Event-driven programming, serverless patterns |
| Operational overhead | Very low — serverless management |
| Best for teams | Developers who build event-driven solutions |
This is one candidate from the Azure compute decision guide. The right choice depends on your full requirements — evaluate scaling, cost, and operational fit before committing.
Browse all tools →