VMSS Autoscale Setting Not Configured
The scale set never changes size on its own, so it cannot absorb load and holds peak capacity through every quiet hour.
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: Configure autoscale on VM scale set.
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
- Navigate to the VMSS in the Azure Portal.
- Select Scaling under Settings.
- Choose Custom autoscale.
- Configure a scale-out rule (e.g., CPU over 70% for 5 min) and scale-in rule (e.g., CPU under 30% for 10 min).
- Set appropriate minimum, maximum, and default instance counts.
- Save and monitor scaling events in the Activity Log.
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-002- Full reference
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.