Preparing this Costframe view
Preparing this Costframe viewCostframe field guide
Right-sizing an Azure VM means selecting a SKU that meets observed and expected workload demand with acceptable headroom. Low CPU is only a candidate signal. Review memory, disk and network throughput, latency, burst behavior, licensing, architecture constraints, availability, and planned demand before changing production.
Framework
Use at least 30 days when it captures normal cycles; extend it for month-end, quarterly, or seasonal workloads.
Sustained low CPU may start review, but no universal percentage proves a VM is oversized.
The target SKU must satisfy memory, disk limits, network limits, accelerators, architecture, region, availability, and licensing.
Monthly saving = current net monthly cost − target net monthly cost, adjusted for commitments and dependent costs.
Implementation playbook
Inspect percentile and maximum CPU, available memory where instrumented, disk IOPS/throughput, network, latency, and restarts.
Filter regional SKUs by required features and limits before comparing price.
Benchmark in a safe environment, define success and rollback thresholds, then use the normal change process.
Compare service indicators and billed cost across a representative post-change window.
Worked example
Thresholds are illustrative, not universal production rules.
Evidence standard
Costframe separates observed evidence from inference. Every finding can show what was checked, what was unavailable, why confidence may be lower, and whether the action still needs approval.
Decision tree
If source data is missing or stale, record the limitation before quoting impact.
If no team owns the resource, assign ownership before opening a change.
Treat the number as estimated until follow-up billing evidence supports it.
Failure modes
FAQ
Use it as an operating framework, then verify the resource, owner, evidence freshness, and billing basis before approving work.
Reject or park the estimate when provider data is incomplete, confidence is low, ownership is unclear, or the action conflicts with migration, resilience, or compliance plans.
Document the evidence source, net/list basis, assumption, owner, approval state, and how follow-up cost sync will verify the result.
Put the framework to work
Costframe connects read-only, records the evidence behind each finding, and keeps list-price estimates separate from net savings.