← All free tools
Free · No signup · Client-side
Azure waste calculator.
Three inputs, defensible savings band across the three buckets that pay back fastest. Reservation coverage, idle cleanup, right-sizing. Math runs in your browser; nothing leaves the page.
Estimated month-1 savings band
$18,915 – $32,108
25% – 43% of your current monthly bill
- 1. Idle & orphan resource cleanup
- $7,313 – $10,688Stopped-but-billed VMs, unattached disks, idle public IPs, orphan load balancers, stale snapshots.
- 2. Reservation & savings-plan coverage
- $8,033 – $13,388One-year or three-year RI / savings plan on the long-running compute that remains after cleanup.
- 3. Right-sizing under-utilised VMs
- $3,570 – $8,033Move VMs at < 25% sustained CPU to the next SKU tier down. Defender for Cloud recommendation feed feeds the list.
Band reflects the spread we see across real engagements. Conservative end assumes minimal commitment; aggressive end assumes 3-year reservation coverage plus full cleanup. Numbers are estimates, not guarantees; the actual audit narrows them to a single figure with line items.
Questions
The four people ask first.
- Where do the savings bands come from?
- Anonymized data from Azure landing-zone engagements we ran between 2024 and 2026. The reservation-coverage band is calibrated against published Microsoft RI / savings-plan discount tables (28-40% for production, 5-12% for dev/test). The right-sizing and idle-cleanup bands are observed deltas from real engagements where finance signed off on the saving.
- Why an estimate, not a single number?
- Because we have not seen your tenant. A single number would be either too optimistic (every band at the top) or too conservative (every band at the bottom) for your specific environment. A defensible band lets you take it to finance without overselling. A real audit replaces the band with a single figure with line items.
- Is my input sent anywhere?
- No. The calculator runs entirely in your browser. There is no tracking pixel, no analytics call, no server hit. Refresh the page and your inputs are gone. View source to verify.
- Why is dev/test such a different number than production?
- Reservations require committed capacity 24/7 to be worth it. Dev/test workloads usually run office hours only, so RI math turns negative fast. Savings on dev/test come almost entirely from automated start/stop schedules, not commitments.
Want the band turned into a single number for your tenant?
Discovery call: thirty minutes, one senior engineer. We run the real audit against your subscriptions and quote a fixed fee for the landing-zone rebuild that captures the savings.