Skip to content

Commit b14dc11

Browse files
integrate feedback
1 parent fabcb43 commit b14dc11

File tree

2 files changed

+27
-5
lines changed

2 files changed

+27
-5
lines changed

articles/container-apps/functions-overview.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,21 +5,41 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: how-to
8-
ms.date: 03/25/2025
8+
ms.date: 03/31/2025
99
ms.author: cshoe
1010
---
1111

1212
# Azure Functions on Azure Container Apps overview
1313

14-
Azure Functions allows you to run small pieces of code (functions) without worrying about application infrastructure. When you combine Azure Functions with Azure Container Apps, you get the best of both worlds: the simplicity and event-driven nature of Functions with the containerization and advanced deployment capabilities of Container Apps.
14+
Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on Azure Container Apps. Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs.
15+
16+
Container Apps hosting lets you run your functions in a fully supported and managed, container-based environment with built-in support for open-source monitoring, mTLS, Dapr, and Kubernetes Event-driven Autoscaling (KEDA).
1517

1618
This article shows you how to create and deploy an Azure Functions app that runs within Azure Container Apps. You learn how to:
1719

1820
- Set up a containerized Functions app with preconfigured auto scaling rules
1921
- Deploy your application using either the Azure portal or Azure CLI
2022
- Verify your deployed function with an HTTP trigger
2123

22-
By running Functions in Container Apps, you benefit from automatic scaling based on HTTP traffic, easy configuration, and a fully managed container environment—all without having to manage the underlying infrastructure yourself.
24+
By running Functions in Container Apps, you benefit from automatic scaling, easy configuration, and a fully managed container environment—all without having to manage the underlying infrastructure yourself.
25+
26+
## Event-driven scaling
27+
28+
All Functions triggers are available in your containerized Functions app. However, only the following triggers can dynamically scale (from zero instances) based on received events when running in a Container Apps environment:
29+
30+
- Azure Event Grid
31+
- Azure Event Hubs
32+
- Azure Blob Storage (event-based)
33+
- Azure Queue Storage
34+
- Azure Service Bus
35+
- Durable Functions (MSSQL storage provider)
36+
- HTTP
37+
- Kafka
38+
- Timer
39+
40+
Azure Functions on Container Apps is designed to configure the scale parameters and rules as per the event target. You don't need to worry about configuring the KEDA scaled objects. You can still set minimum and maximum replica count when creating or modifying your function app.
41+
42+
You can write your function code in any language stack supported by Azure Functions. You can use the same Functions triggers and bindings with event-driven scaling.
2343

2444
## Scenarios
2545

articles/container-apps/functions-usage.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: how-to
8-
ms.date: 03/25/2025
8+
ms.date: 03/31/2025
99
ms.author: cshoe
1010
zone_pivot_groups: azure-cli-or-portal
1111
---
@@ -76,7 +76,9 @@ This article shows you how to create an [Azure Functions app in Azure Container
7676
| Registry login server | Enter **mcr.microsoft.com** |
7777
| Image and tag | Enter **azure-functions/dotnet8-quickstart-demo:1.0** |
7878

79-
1. For *Development stack*, select **.NET**
79+
1. For *Development stack*, select **.NET**.
80+
81+
This value is required since the sample container image is implemented in .NET.
8082

8183
1. Select **Next > Ingress** to switch to the Ingress section and enter the following values.
8284

0 commit comments

Comments
 (0)