From 63cb801b67f41f2c532f4d5532f2e50086beb850 Mon Sep 17 00:00:00 2001 From: AnkushRaj15 Date: Mon, 1 Sep 2025 17:32:19 +0530 Subject: [PATCH] Adding missing info (cooldown period clarification) Hi, I'm an app services support engineer in Microsoft CSS. Received a customer case where they were anxious and confused about the cool down period behavior causing unexpected scaling actions (2508220050001316). Adding this clarification to the Microsoft docs will help prevent such confusion and support requests by clearly explaining when and how the cool down period works in Azure Container Apps scaling. --- articles/container-apps/scale-app.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/articles/container-apps/scale-app.md b/articles/container-apps/scale-app.md index 1803679cdf044..9225e1f84931c 100644 --- a/articles/container-apps/scale-app.md +++ b/articles/container-apps/scale-app.md @@ -317,6 +317,8 @@ Not supported in the Azure portal. Use the [Azure CLI](scale-app.md?pivots=azure You can create a custom Container Apps scaling rule based on any [ScaledObject](https://keda.sh/docs/latest/concepts/scaling-deployments/)-based [KEDA scaler](https://keda.sh/docs/latest/scalers/) with these defaults: +**Note:** The KEDA cooldownPeriod only applies when scaling down to 0 instances and is not enforced for scale-down operations where the number of replicas decreases from N to a value greater than 0; whereas scaling up from 1 to N replicas is managed by the Kubernetes Horizontal Pod Autoscaler. + | Defaults | Seconds | |--|--| | Polling interval | 30 |