Azure VM High CPU, Upsize Recommendation
The VM is running at its ceiling, so requests queue and latency climbs before anything reports an outright failure.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
What we would change and why, with no savings claim and no policy behind it.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Increase VM size.
Fix
After a guided review, where you confirm the change, ZopNight stops it, resizes it to the recommended tier, and starts it again, then checks the change took.
- Applies to
- Virtual Machines on Azure
- The fix, by hand
- Review 14-day CPU + memory metrics in Monitor → Metrics (memory requires the Azure Monitor Agent).
- Identify the next larger SKU within the same family, or pivot to a memory-optimized family (Esv5, Edsv5) if the bottleneck is memory.
- If a reservation covers the current size, exchange it to the new size first to avoid double-paying.
- Stop (deallocate) the resource → Size → pick the target SKU → Resize → Start.
- Validate latency, error rate, and resource utilisation for 48 hours.
- If the larger size still saturates, escalate to a different VM family rather than continuing to step up sizes.
ZopNight does this for you after a guided review.
- Category
- Performance. A measured bottleneck worth clearing: throttled operations, undersized tiers, a workload near its limit.
- Where it appears
- The Advisory tab of Recommendations, with every affected resource listed.
- Rule ID
RC-262- Full reference
Related checks
See the performance 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.