Autoscale Threshold and Cooldown Logic

When designing rules, set appropriate thresholds and time durations to avoid overly sensitive scaling that could cause instability, known as flapping. A good practice is to scale out when average CPU usage is above 70% for 10 minutes and scale in only when it falls below 30% for a similar period. Always define sensible instance limits: a minimum to ensure availability, a maximum to control costs, and a default number of instances to use if metrics are unavailable.

After configuring autoscale, monitor its operations using Azure Monitor logs and the activity log to verify that scaling actions trigger correctly and to identify any failures. Set up alerts to be notified of significant autoscale events. Test scaling rules under different load conditions to ensure they behave as expected before relying on them in production.