Find the Azure waste hiding in your cloud bill.

One of the most frequent surprises on a Microsoft Azure invoice is seeing ongoing compute charges for virtual machines that engineering teams believed were turned off. When you shut down a virtual machine from inside the guest operating system (such as initiating a shutdown command in Windows Server or Linux), Azure places the instance in a Stopped state rather than a Deallocated state.

In the Stopped state, Microsoft Azure continues to reserve the underlying physical host CPU cores and memory allocation exclusively for your virtual machine so it can start up instantly. Because that physical compute capacity remains locked to your tenant, Azure bills for the full hourly compute rate of the instance size, in addition to the provisioned OS and data disks.

WasteRadar queries Azure Resource Graph to evaluate the runtime power state across all connected subscriptions. When an instance is detected in the Stopped state without being deallocated, WasteRadar flags the ongoing monthly compute waste and provides the exact portal step or CLI command to transition the VM to the Deallocated state so compute billing drops to zero.

When a virtual machine in Microsoft Azure is deleted, Azure does not automatically delete the attached Managed Disks (the OS disk and attached data volumes) unless that deletion option was explicitly selected during initial deployment. Consequently, orphan Premium SSD, Standard SSD, and Standard HDD volumes frequently remain unattached in resource groups for months or years.

Azure Managed Disks are billed based on the total provisioned storage capacity on a monthly basis, not on the amount of actual data written to them. For instance, an unattached 128 GB Premium SSD continues to bill its full fixed monthly rate on every billing cycle even when zero read or write operations occur.

WasteRadar continuously scans subscription disk registries for Managed Disks that have no active virtual machine attachment. It calculates exact potential savings based on regional Azure retail storage meters and highlights unattached storage volumes lingering across production and development environments.

Engineering teams frequently provision oversized virtual machines for development, staging, testing, or internal tooling workloads that spend the vast majority of their lifecycle sitting idle. Maintaining continuous high-tier compute allocations for dormant workloads results in significant avoidable cloud spend.

WasteRadar evaluates rolling average CPU utilization telemetry directly from Azure Monitor platform metrics over multi-day evaluation windows. By analyzing historical utilization patterns at the cloud control-plane level without requiring invasive guest OS agents, WasteRadar distinguishes between temporarily quiet systems and chronically oversized instances.

Identified underutilized VMs are highlighted with actionable rightsizing recommendations, such as switching to cost-effective burstable B-series instances or configuring automated start/stop schedules during non-working hours.

Microsoft Azure applies an hourly reservation charge for Standard Public IPv4 addresses that are provisioned in a subscription but not associated with an active resource (such as a Virtual Machine network interface, Application Gateway, or Load Balancer).

In dynamic cloud environments—particularly those utilizing Kubernetes (AKS), Terraform, or automated CI/CD staging pipelines—public IP addresses are often created for temporary ingress controllers and forgotten when the underlying compute clusters are torn down.

WasteRadar inspects the IP configuration bindings across your Azure network topology. If a public IP has no active network interface or gateway mapping, WasteRadar surfaces the dormant asset and calculates the recurring annual savings achievable by releasing the address.

Azure Standard Load Balancers incur a fixed hourly base charge for the first configured load balancing rules, in addition to hourly data processing meters. When workloads are migrated, retired, or reconfigured, the load balancer resource is frequently left running in the resource group.

When a Standard Load Balancer has zero backend pool members or all backend virtual machines have been decommissioned, the load balancer continues to accrue its base hourly provisioning fee despite handling zero customer traffic.

WasteRadar evaluates the backend address pool collections across all load balancers in your subscriptions. When a load balancer is detected with no active backend pool targets, WasteRadar flags it as an idle asset with immediate monthly cost savings upon removal.

Azure Virtual Network NAT Gateways provide outbound internet connectivity for private subnets. Each provisioned NAT Gateway carries a continuous fixed hourly base rate in addition to outbound data processing meters.

When virtual network subnets are re-architected, migrated to alternative firewalls, or deleted, the NAT Gateway often remains provisioned in an unattached state. In this dormant state, the NAT Gateway continues to generate fixed monthly charges without providing any active network connectivity.

WasteRadar checks the subnet association status of every NAT Gateway in your subscriptions to instantly surface unattached gateways, allowing cloud administrators to remove them with zero impact on production traffic.

While empty resource groups in Microsoft Azure do not generate direct compute or storage costs on your bill, they represent significant governance debt. Abandoned resource groups clutter subscription management views, trigger false alarms in tagging audits, and confuse automated infrastructure-as-code pipelines.

When applications or temporary test environments are torn down, engineers often delete individual resources while leaving the parent resource group behind. Over time, an enterprise subscription can accumulate dozens of empty containers.

WasteRadar audits all resource groups across connected subscriptions and flags any container that contains zero active child resources. This enables FinOps and DevOps leads to maintain a clean, auditable, and well-governed Azure subscription hierarchy.