📢 Important: Native Azure Functions Support Now Available
Azure Functions now offers native integration with Azure Container Apps (see announcement). This is the recommended hosting method for most new workloads, combining the full capabilities of Azure Container Apps with the simplicity of the Functions programming model and auto-scaling.
📚 Learn more: Native Azure Functions Support in Azure Container Apps
🔧 Sample template: main.bicep
Note: Always refer to the official documentation for the latest information.
Azure Functions on Container Apps enables you to build event-driven, cloud-native applications with unprecedented flexibility. Run your functions alongside other microservices, APIs, websites, workflows, or any containerized program—all within a unified platform.
- Leverage the Functions programming model with your preferred language or framework
- Zero infrastructure management - Built on Azure Kubernetes Service with Dapr and KEDA
- Unified platform for all your microservices with consistent networking, observability, and scaling
- Seamless tooling across Azure Portal, Azure CLI, and CI/CD pipelines (Azure DevOps, GitHub Actions)
Easily integrate mixed workloads in a single environment:
- Azure Functions
- Azure Container Apps
- Azure Spring Apps
- APIs, websites, and custom containers
- Unified networking, observability, and configuration across all services
Built-in integration with enterprise-grade technologies:
- KEDA for event-driven autoscaling
- Dapr for distributed application runtime
- Envoy for advanced networking
- Service discovery and native container support
- Consistent development experience across all Azure Functions hosting options
- Simplified client tooling and DevOps integration
- Inner loop and outer loop development support
- Runtime flexibility with full Functions programming model
- Scale to zero during idle periods
- Scale to 1000s of containers under high load
- Event-based scaling with platform-managed triggers
| Scenario | Description |
|---|---|
| Event Processing | React to events from HTTP, Kafka, Event Hubs, Service Bus, or Storage Queues and invoke other services |
| Web Services & APIs | REST API backends with event-based execution and authentication workflows |
| Data Ingestion | Event-based data quality checks for e-commerce, retail, and travel applications with ML workflow integration |
| Mixed Microservices | Seamlessly integrate different application types in a single environment |
| IoT & Edge Computing | Process events from IoT devices, point-of-sale systems, and edge locations |
| Version | Type | Description | Recommendation | Additional Information |
|---|---|---|---|---|
| V2 | kind=functionapp |
Native integration with full Container Apps features. • Direct Container Apps resource creation • Full access to all Container Apps capabilities • No separate Azure Functions resource needed |
✅ Recommended for new workloads | Learn more about V2 |
| V1 | Legacy | Original hosting model. • Creates Azure Functions resource • Provisions Container Apps resources in read-only platform-managed resource group • Limited Container Apps feature access |
Learn more about V1 |
- V2 (Native Integration): You create Container Apps directly with
kind=functionapp, providing full control and access to all Container Apps features without requiring a separate Azure Functions resource. - V1 (Legacy): Creates an Azure Functions resource that additionally provisions Container Apps resources under a read-only, platform-managed resource group with limited feature access.
Azure Functions on Container Apps is available in all Container Apps supported regions.
- Consumption plan: Pay-per-use model
- Dedicated plan: Reserved compute capacity
Choose right workload profile type as per your needs.
Learn more: Azure Container Apps pricing
- Create Azure Functions on Container Apps V2 (kind=functionapp) - ✅ Recommended
- Create Azure Functions on Container Apps V1
⚠️
Submit an issue or feature request to the Azure Container Apps GitHub repository. Add the functions on aca label to help expedite issue triage.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.