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
This article shows you how to configure *service update* settings (preview) in your API Management instance. Azure periodically applies service updates automatically to API Management instances, using a phased rollout approach. These updates include new features, security enhancements, and reliability improvements.
16
+
This article shows you how to configure *service update* settings (preview) in your API Management instance. Azure periodically applies service updates automatically to API Management instances by using a phased rollout approach. These updates include new features, security enhancements, and reliability improvements.
17
17
18
-
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group*(also called a *release channel*) for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
18
+
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group* for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
19
19
20
-
***Update group** - A set of instances that receive API Management service updates during a production rollout, which can take from several days to several weeks to complete.
20
+
## Update group
21
21
22
-
Choose from:
23
-
***Early** - Receive updates early in the rollout, for testing and early access to new features. This option is not recommended for production deployments.
24
-
***Default** - Receive updates as part of the regular release rollout. This option is recommended for most services, including production deployments.
25
-
***Late** - Receive updates later than the previous groups, typically weeks after the initial rollout. This option is recommended for mission-critical deployments only.
26
-
***AI Gateway Early** (GenAI release channel) - Get early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups. Receive other service updates as part of the **Late** rollout group.
22
+
An update group (also called a *release channel*) is a set of instances that receive API Management service updates during a production rollout, which can take from several days to several weeks to complete.
27
23
28
-
> [!NOTE]
29
-
> Azure deploys all updates using a [safe deployment practices (SDP) framework](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/). Updates released early in a rollout might be less stable and replaced later by stable releases. All instances are eventually updated to the most stable release builds.
24
+
| Update group | Description |
25
+
|--------------|-------------|
26
+
|**AI Gateway Early** (GenAI release channel) | Gets early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups.<br/><br/>Combines the most stable mainline service updates with the newest AI-specific features. Receives other service updates as part of the **Late** update group, enabling faster deployment of AI-related capabilities. |
27
+
|**Early**| Receives updates early in the rollout, for testing and early access to new features. This option isn't recommended for production deployments. |
28
+
|**Default**| Receives updates as part of the regular release rollout. This option is recommended for most services, including production deployments. |
29
+
|**Late**| Receives updates later than the previous groups, typically weeks after the initial rollout. This option is recommended for mission-critical deployments only. |
30
+
31
+
32
+
> [!NOTE]
33
+
> * Azure deploys all updates by using a [safe deployment practices (SDP) framework](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/). Updates released early in a rollout might be less stable and replaced later by stable releases. All instances are eventually updated to the most stable release builds.
34
+
> * All update groups can include features in preview. Preview features are clearly noted in the Azure portal and documentation.
35
+
> * Features propagate through update groups in this sequence: **AI Gateway Early** (AI features only) → **Early** → **Default** → **Late**.
36
+
37
+
For example, you might want to add a test instance to the **Early** update group. This instance receives updates before your production instances, which you put in the **Default** or **Late** update group. You can monitor the test instance for any issues caused by the updates before they reach your production instances. [Learn more about canary deployments](#canary-deployment-strategies) with API Management
30
38
31
-
For example, you might want to add a test instance to the **Early** update group. This instance receives updates before your production instances, which you put in the **Default** or **Late** update group. You can monitor the test instance for any issues caused by the updates before they reach your production instances. [Learn more about canary deployments](#canary-deployment-strategies) with API Management
39
+
## Maintenance window
32
40
33
-
***Maintenance window** - An 8-hour daily period when you want your instance to receive updates. By default, the maintenance window is 10 PM to 6 AM in the instance's timezone.
41
+
A maintenance window is an 8-hour daily period when you want your instance to receive updates. By default, the maintenance window is 10 PM to 6 AM in the instance's timezone.
34
42
35
-
Service disruptions are rare during an update, but you might want to reduce risk by selecting times of low service use. For example, for production instances, set a maintenance window during weekday evenings and weekend mornings.
43
+
Service disruptions are rare during an update, but you might want to reduce risk by selecting times of low service use. For example, for production instances, set a maintenance window during weekday evenings and weekend mornings.
36
44
37
45
## Configure service update settings
38
46
39
47
1. Sign in to the [Azure portal](https://portal.azure.com) and go to your API Management instance.
40
48
1. In the left menu, select **Deployment + infrastructure** > **Service update settings**.
41
49
1. Under **Update group**, review the current setting and select **Edit** to change it.
42
-
1. Under **Maintenance window**, review the current settings and select **Edit** to change them. For each day you can select the default window, a different standard window, or a custom window by day.
50
+
1. Under **Maintenance window**, review the current settings and select **Edit** to change them. For each day, you can select the default window, a different standard window, or a custom window by day.
43
51
44
-
## Know when your instances are receiving updates
52
+
## Know when your instances receive updates
45
53
46
-
Here's how to know about service updates that are expected or are in progress.
54
+
Here's how you can learn about service updates that are expected or are in progress.
47
55
48
56
* API Management updates are announced on the [API Management GitHub repo](https://github.com/Azure/API-Management/releases). Subscribe to receive notifications from this repository to know when update rollouts begin.
49
57
50
-
*Monitor service updates that are taking place in your API Management instance by using the Azure [Activity log](/azure/azure-monitor/essentials/activity-log). The "Scheduled maintenance" event is emitted when an update begins.
58
+
*Use the Azure [Activity log](/azure/azure-monitor/essentials/activity-log) to monitor service updates that take place in your API Management instance. The "Scheduled maintenance" event is emitted when an update begins.
51
59
52
60
:::image type="content" source="media/configure-service-update-settings/scheduled-maintenance.png" alt-text="Scheduled maintenance event in Activity log in the portal.":::
Copy file name to clipboardExpand all lines: articles/app-service/manage-automatic-scaling.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,10 @@ The `AutomaticScalingInstanceCount` metric reports the number of virtual machine
178
178
179
179
### How does ARR Affinity affect automatic scaling?
180
180
181
-
Azure App Service uses Application Request Routing cookies known as an ARR Affinity. ARR Affinity cookies restrict scaling because they send requests only to servers associated with the cookie, rather than any available instance. For apps that store state, it's better to scale up (increase resources on a single instance). For stateless apps, scaling out (adding more instances) offers more flexibility and scalability. ARR Affinity cookies are enabled by default on App Service. Depending on your application needs, you might choose to disable ARR affinity cookies when using automatic scaling.
181
+
> [!NOTE]
182
+
> When enabling Automatic Scaling on the App Service Plan, all pre-existing apps in the plan will automatically have ARR Affinity disabled.
183
+
184
+
Azure App Service uses Application Request Routing cookies known as an ARR Affinity. ARR Affinity cookies restrict scaling because they send requests only to servers associated with the cookie, rather than any available instance. For apps that store state, it's better to scale up (increase resources on a single instance). For stateless apps, scaling out (adding more instances) offers more flexibility and scalability. ARR Affinity cookies are enabled by default on App Service. However, when using automatic scaling, you should disable ARR affinity cookies to ensure proper scaling.
182
185
183
186
To disable ARR Affinity cookies: select your App Service app, and under **Settings**, select **Configuration**. Next select the **General settings** tab. Under **Session affinity**, select **Off** and then select the **Save** button.
title: Manage Azure Functions on Container Apps using Azure CLI
3
+
description: Learn how to deploy, configure, and manage Azure Functions on Azure Container Apps using the Azure CLI.
4
+
services: container-apps
5
+
author: craigshoemaker
6
+
ms.service: azure-container-apps
7
+
ms.topic: how-to
8
+
ms.date: 11/25/2025
9
+
ms.author: cshoe
10
+
---
11
+
12
+
# Manage Azure Functions on Container Apps using Azure CLI
13
+
14
+
This article shows you how to deploy and manage Azure Functions on Azure Container Apps by using the Azure CLI. You learn how to set up your environment, create the necessary Azure resources, and deploy function apps for managing function operations.
15
+
16
+
## Prerequisites
17
+
18
+
Before you begin, ensure you have:
19
+
20
+
- An Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/).
21
+
-[Azure CLI](/cli/azure/install-azure-cli) version 2.0.70 or later.
22
+
- A [Functions app](functions-usage.md) ready for containerized deployment
23
+
24
+
## Manage functions
25
+
26
+
You can manage your deployed functions within Azure Container Apps using the Azure CLI. The following commands help you list, inspect, and interact with the functions running in your containerized environment.
27
+
28
+
> [!NOTE]
29
+
> When dealing with multirevision scenarios, add the `--revision <REVISION_NAME>` parameter to your command to target a specific revision.
30
+
31
+
### List functions
32
+
33
+
View all functions deployed in your container app:
34
+
35
+
```azurecli
36
+
# List all functions
37
+
az containerapp function list \
38
+
--resource-group <RESOURCE_GROUP> \
39
+
--name <CONTAINER_APP_NAME>
40
+
```
41
+
42
+
### Show function details
43
+
44
+
Get detailed information about a specific function:
45
+
46
+
```azurecli
47
+
az containerapp function show \
48
+
--resource-group <RESOURCE_GROUP> \
49
+
--name <CONTAINER_APP_NAME> \
50
+
--function-name <FUNCTIONS_APP_NAME>
51
+
```
52
+
53
+
## Monitor function invocations
54
+
55
+
Monitoring your function app is essential for understanding its performance and diagnosing issues. The following commands show you how to retrieve function URLs, trigger invocations, and view detailed telemetry and invocation summaries by using the Azure CLI.
56
+
57
+
1. To view invocation traces, get detailed traces of function invocations.
58
+
59
+
```azurecli
60
+
az containerapp function invocations traces \
61
+
--name <CONTAINER_APP_NAME> \
62
+
--resource-group <RESOURCE_GROUP> \
63
+
--function-name <FUNCTIONS_APP_NAME> \
64
+
--timespan 5h \
65
+
--limit 3
66
+
```
67
+
68
+
1. View an invocation summary to review successful and failed invocations.
69
+
70
+
```azurecli
71
+
az containerapp function invocations summary \
72
+
--name <CONTAINER_APP_NAME> \
73
+
--resource-group <RESOURCE_GROUP> \
74
+
--function-name <FUNCTIONS_APP_NAME> \
75
+
--timespan 5h
76
+
```
77
+
78
+
## Manage function keys
79
+
80
+
Azure Functions uses [keys for authentication and authorization](/azure/azure-functions/function-keys-how-to). You can manage the following different types of keys:
81
+
82
+
- **Host keys**: Access any function in the app
83
+
- **Master keys**: Provide administrative access
84
+
- **System keys**: Used by Azure services
85
+
- **Function keys**: Access specific functions
86
+
87
+
The following commands show you how to manage keys for the host. To run the same command for a specific Functions app, add the `--function-name <FUNCTIONS_APP_NAME>` parameter to your command.
88
+
89
+
### List keys
90
+
91
+
Use the following commands to list host-level and function-specific keys for your Azure Functions running in Container Apps.
92
+
93
+
> [!NOTE]
94
+
> Keep a minimum of one replica running for the following keys management commands to work.
95
+
96
+
```azurecli
97
+
az containerapp function keys list \
98
+
--resource-group <RESOURCE_GROUP> \
99
+
--name <CONTAINER_APP_NAME> \
100
+
--key-type hostKey
101
+
```
102
+
103
+
### Show a specific key
104
+
105
+
Show the value of a specific host-level key for your function app with the following command:
106
+
107
+
```azurecli
108
+
az containerapp function keys show \
109
+
--resource-group <RESOURCE_GROUP> \
110
+
--name <CONTAINER_APP_NAME> \
111
+
--key-name <KEY_NAME> \
112
+
--key-type hostKey
113
+
```
114
+
115
+
### Set a key
116
+
117
+
Set a specific host-level key for your function app with the following command:
118
+
119
+
```azurecli
120
+
az containerapp function keys set \
121
+
--resource-group <RESOURCE_GROUP> \
122
+
--name <CONTAINER_APP_NAME> \
123
+
--key-name <KEY_NAME> \
124
+
--key-value <KEY_VALUE> \
125
+
--key-type hostKey
126
+
```
127
+
128
+
## Next steps
129
+
130
+
-[Learn about Azure Functions triggers and bindings](../azure-functions/functions-triggers-bindings.md)
0 commit comments