Scaling Cooldown Too Short
The group reacts again before the last change has taken effect, so it over-scales and then over-shrinks instead of settling.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Lengthen the autoscale cooldown.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- VM Scale Sets on Azure
- The fix, by hand
- Review the autoscaling cooldown period for this resource.
- Increase the cooldown from the current value to 300 seconds (recommended).
- A longer cooldown prevents rapid oscillations between scale-out and scale-in.
- Monitor scaling events to verify stable behavior after the change.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-ASC-006
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.