Platform Limits¶
Plan-specific limits relevant to .NET isolated worker apps.
flowchart TD
A[Configuration] --> B[Build]
B --> C[Deploy]
C --> D[Observe]Topic/Command Groups¶
| Limit | Consumption | Flex Consumption | Premium | Dedicated |
|---|---|---|---|---|
| Default timeout | 5 min | 30 min | 30 min | 30 min |
| Max timeout | 10 min | Unlimited | Unlimited | Unlimited |
| Scale out | Up to 200 (Windows), up to 100 (Linux) | Up to 1000 | Up to 100 | Tier based |
| VNet integration | No | Yes | Yes | Yes |
| Kudu/SCM site | Not available on Linux Consumption | Not available | Available | Available |
| Custom containers | Not supported | Not supported | Supported | Supported |
| Deployment slots | No | No | Yes | Yes |
Usage Notes¶
- Flex Consumption does not support Kudu/SCM endpoints.
- Flex Consumption does not support custom container images.
- Flex Consumption routes all traffic through the integrated VNet.
- Linux Consumption does not provide Kudu/SCM endpoints.
HTTP considerations¶
- Azure Load Balancer idle timeout is 230 seconds for HTTP clients.
- Use async status patterns for long-running work.
- Prefer Durable orchestration for workflows beyond request/response windows.