You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/functions-usage.md
+67-15Lines changed: 67 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,38 @@
1
1
---
2
2
title: Create an Azure Functions app with auto scaling rules on Azure Container Apps
3
-
description: Learn to create an Azure Functions app pre-configured with auto scaling rules in Azure Container Apps.
3
+
description: Learn to create an Azure Functions app preconfigured with auto scaling rules in Azure Container Apps.
4
4
services: container-apps
5
5
author: craigshoemaker
6
6
ms.service: azure-container-apps
7
7
ms.topic: how-to
8
-
ms.date: 03/19/2025
8
+
ms.date: 03/25/2025
9
9
ms.author: cshoe
10
10
zone_pivot_groups: azure-cli-or-portal
11
11
---
12
12
13
13
# Use Azure Functions in Azure Container Apps
14
14
15
-
you can create your container app pre-configured with auto-scaling rules fine-tuned for Azure Functions.
15
+
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.
16
16
17
-
TODO
17
+
This article shows you how to create and deploy an Azure Functions app that runs within Azure Container Apps. You'll learn how to:
18
+
19
+
- Set up a containerized Functions app with pre-configured auto scaling rules
20
+
- Deploy your application using either the Azure portal or Azure CLI
21
+
- Verify your deployed function with an HTTP trigger
22
+
23
+
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
+
25
+
## Scenarios
26
+
27
+
Azure Functions in Container Apps provides a versatile combination of services to meet the needs of your applications. The following scenarios are representative of the types of situations where paring Azure Container Apps with Azure Functions gives you the control and scaling features you need.
28
+
29
+
-**Line-of-business APIs**: Package custom libraries, packages, and APIs with Functions for line-of-business applications.
30
+
31
+
-**Migration support**: Migration of on-premises legacy and/or monolith applications to cloud native microservices on containers.
32
+
33
+
-**Event-driven architecture**: Supports event-driven applications for workloads already running on Azure Container Apps.
34
+
35
+
-**Serverless workloads**: Serverless workload processing of videos, images, transcripts, or any other processing intensive tasks that required GPU compute resources.
18
36
19
37
## Prerequisites
20
38
@@ -65,9 +83,9 @@ TODO
65
83
66
84
1. Under the *Container details* section, enter the following values.
67
85
68
-
| Property |value|
86
+
| Property |Value|
69
87
|---|---|
70
-
| Name | This box is pre-filled with your selection in the last section. |
88
+
| Name | This box is prefilled with your selection in the last section. |
71
89
| Image source | Select **Docker Hub or other registries**|
72
90
| Subscription | Select your subscription |
73
91
| Image type | Select **Public**. |
@@ -76,8 +94,27 @@ TODO
76
94
77
95
1. For *Development stack*, select **.NET**
78
96
97
+
1. Select the **Ingress** to switch to the Ingress section and enter the following values.
98
+
99
+
| Property | Value |
100
+
|---|---|
101
+
| Ingress | Select the checkbox to enable ingress. |
102
+
| Ingress traffic | Select **Accepting traffic from anywhere**. |
103
+
| Ingress type | Select **HTTP**. |
104
+
| Target port | Enter **80**. |
105
+
79
106
1. Select **Review + Create**.
80
107
108
+
1. Select **Create**.
109
+
110
+
1. Once the deployment is complete, select **Go to resource**.
111
+
112
+
1. From the *Overview* page, select the link next to *Application URL* to open the application in a new browser tab.
113
+
114
+
1. Append `/api/HttpExample` to the end of the URL.
115
+
116
+
A message stating "HTTP trigger function processed a request" is returned in the browser.
117
+
81
118
:::zone-end
82
119
83
120
:::zone pivot="azure-cli"
@@ -125,7 +162,7 @@ To sign in to Azure from the CLI, run the following command and follow the promp
125
162
1. Create environment variables.
126
163
127
164
```bash
128
-
GROUP_NAME="my-aca-functions-group"
165
+
RESOURCE_GROUP_NAME="my-aca-functions-group"
129
166
CONTAINER_APP_NAME="my-aca-functions-app"
130
167
ENVIRONMENT_NAME="my-aca-functions-environment"
131
168
LOCATION="westus"
@@ -135,26 +172,41 @@ To sign in to Azure from the CLI, run the following command and follow the promp
0 commit comments