SOURCED · published-list estimate · runs in your browser
Azure Cost Optimization Calculator
Model Azure Reservation, rightsizing, managed disk, and bandwidth savings on retail pricing. Published-list estimate only. The math runs in your browser — your numbers never leave this page.
rates verifiedPublished-list scenario. Not your bill, not a quote, not financial advice.verified —view sources ↓
▮ Assumptions
🔒Computed on your device. No accounts, no bill upload, nothing sent to a server or any vendor.
▮ Scenario result
Decision guidance
Azure cost decisions this calculator can test
This scenario models East US Linux virtual machines, managed disks, provisioned performance, bandwidth, and Azure Reservation coverage as separate billable meters. The sequence reduces removable usage before it applies a long-term commitment.
Questions it answers
How much virtual-machine spend remains after rightsizing before Azure Reservation coverage is considered?
Does moving a managed disk tier or reducing separately provisioned performance actually change the storage invoice?
How much bandwidth spend changes after the free allowance and tiered rates are recalculated?
When it returns zero or refuses a claim
Unknown VM sizes and disk products are not silently mapped to a similar SKU; the estimate is suppressed.
A disk migration cannot claim savings for capacity that is not present, and a more expensive target is rejected.
Reservation savings are calculated from the rightsized compute baseline so removed capacity is not committed for one or three years.
Verify against your invoice
Reconcile VM family, size, count, and running hours against Cost Management exports.
Check managed-disk capacity and any separately billed performance against the disk invoice lines.
Verify bandwidth by billing zone and size Reservation coverage only after operationally safe rightsizing has been completed.
The calculator remains a published-list scenario, not a quote or your actual bill. Use the source links and invoice lines below before acting.
Representative published-list prices, re-verified on a freshness schedule. When a rate goes stale or a resource is not in the verified table, the total is suppressed rather than guessed.