Azure Cost Optimization
OhChimp cuts your Azure bill: deallocate stopped VMs, rightsize by CPU, delete unattached disks, fix Reserved Instances, and modernize Premium SSD disks.
What OhChimp optimizes for Azure
Some of the cost levers OhChimp checks for Azure. Each one becomes a reviewable plan you approve before anything changes.
Stopped-but-not-deallocated VMs
A VM stopped from inside the guest keeps billing full compute. Azure only stops the meter when you deallocate. OhChimp catches VMs in the stopped power state and writes a plan to deallocate them so the charges actually stop.
Over-provisioned VMs by CPU
OhChimp pulls each running VM's average CPU from Azure Monitor over the last 7 days. When a VM that costs more than the floor sits under 10 percent CPU, it becomes a plan to resize toward a smaller size. It also folds in Azure Advisor's own cost recommendations and skips any VM it already flagged so savings are not double counted.
Reserved Instance coverage
Steady VMs on pay-as-you-go leave money on the table. OhChimp groups your running VM sizes, reads your existing reservation orders, and shows where a 1-year (about 37 percent off) or 3-year (about 57 percent off) Reserved Instance beats on-demand for sizes you run at least twice.
Unattached disks and idle public IPs
Managed disks keep billing after their VM is gone. A static public IP with nothing attached charges by the hour for nothing. OhChimp lists both and writes a plan to delete the unattached disks and release the unassociated IP addresses.
Premium SSD v1 to v2 disks
Premium SSD v2 has a lower per-GB rate plus a free 3,000 IOPS and 125 MB/s baseline. OhChimp finds attached Premium v1 data disks below the size cutover and writes a snapshot-and-recreate plan with rollback. It skips OS disks and any disk already provisioned above the free baseline, since moving those would regress performance or add paid IOPS the savings model never subtracts.
AKS node pool sizing
OhChimp maps every AKS cluster's node pools with their size, autoscaler config, and Spot usage. It flags large fixed-size pools that should enable the cluster autoscaler, pools pinned at a high minimum count, and single-node pools with no high availability. It also points out user pools that could run interruptible Spot nodes.
Azure cost optimization FAQ
How does OhChimp connect to my Azure subscription?
With a service principal you grant the Reader role on the subscription. OhChimp gets a token from Microsoft Entra ID and reads resource and billing metadata over Azure Resource Manager to find waste. It never stores your application data, secrets, or workload contents.
Does OhChimp need write access or see my data?
No. The service principal needs only the read-only Reader role. OhChimp reads metadata like VM power states, CPU metrics, disk and IP inventory, AKS pools, and Advisor recommendations. It does not read application data or workload contents.
What Azure costs does OhChimp actually reduce?
Stopped VMs still billing full compute, over-provisioned VMs flagged by low CPU and Azure Advisor, weak Reserved Instance coverage, unattached managed disks, idle public IPs, Premium SSD v1 disks that should move to v2, and over-provisioned or fixed-size AKS node pools.
Who applies the changes, and can I roll back?
You do. Every fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and you are always the one who clicks. The Premium disk migration, for instance, snapshots first so you can restore.
How do I know the savings are real, and what does it cost?
OhChimp checks your actual Azure bill after you apply a plan. Savings are marked VERIFIED only after 7 or more days, a drop of at least 10 percent, and 3 consecutive positive checks. Otherwise the plan is flagged "not implemented." Pricing is flat monthly, and OhChimp never takes a cut of your savings. A year-one ROI guarantee refunds your subscription fees if it does not pay for itself in the first 12 months on a paid plan.
Why a stopped-but-not-deallocated VM keeps billing: Azure VM stopped vs deallocated: stopped still bills.
The Premium SSD v1 to v2 lever, start to finish: Azure Premium SSD v1 to v2: cut disk costs 21-73%.
Related integrations
Teams running Azure usually run these too. OhChimp finds the waste in each and proves it on the bill.
DigitalOcean
Oversized Droplets, Spaces storage, idle nodes
Google Cloud
Idle VMs, disk tiers, committed-use discounts
Linode
Oversized instances and idle compute