Unexpected Charges in azure function app

Question

Hi, Our team encountered an unexpected charge issue while using Function App.

We are using D4 workload with minimum and maximum instance limits configured as 0–4.

On February 2, we increased the functionAppScaleLimit from 4 to 16 (resulting in a cost of 9k INR for that day), and at the end of February 3, we reduced it back to 4 (resulting in a cost of 10k INR for that day).

However, from February 4 to February 9, the costs remained high (still around 10k INR per day). When we investigated the cause on February 10, we found that 15 instances were still running, which does not match expectations because we had already lowered the functionAppScaleLimit to 4 by the end of February 3.

Please reply to us soon and explain the reason for this, and we would like to request a refund for the unreasonable charges from February 4 to February 9.

Answer 1

I might be wrong, but lowering the scaleLimit on Feb 3 while the instance count. stayed elevated through Feb 9 usually indicates the scale‑down evaluator never fired. I think that support can confirm this from the instance‑level runtime stamps and refund the excess usage.