Your Azure bill has three levers, and you're probably not using any of them

Almost every cloud bill we review has the same profile: machines running at pay-as-you-go rates, at the size they were migrated with, with licenses the company already paid for under another agreement and that nobody applied. It isn't negligence. It's that the three levers that move the cost live in different places in the portal, and none of them turns on by itself.

Lever 1 · Azure Hybrid Benefit: stop paying twice

If your company has Windows Server or SQL Server licenses with Software Assurance, you can apply them to the machines running in Azure. Without that, the hourly rate includes the licensing again: you pay for the operating system in your licensing agreement and pay for it again on your consumption bill.

It's the fastest lever because it doesn't require touching the architecture: it's a per-machine option, and the savings show up in the next billing cycle. What it does require is an inventory, because you need to know which licenses you have, how many cores they cover, and which environments qualify.

Lever 2 · Reserved instances, but in tranches

A reservation is a one- or three-year consumption commitment in exchange for a discount on the standard rate. For compute, a three-year reservation can reach a 62% discount. The question isn't whether it makes sense: it does. The question is how much to reserve and when.

This is where most people get it wrong. Buying a single reservation, for your total current consumption and the day after migrating, freezes a snapshot of something that is still moving. What we do is different: reserve in staggered tranches. First the stable baseline—what you know will stay on no matter what—and then, every quarter, a new tranche on the consumption that has already proven to be permanent.

That way the discount still applies, but the company isn't locked into a size that will change once the machines are rightsized, which is precisely the next lever.

Lever 3 · Rightsize by machine type and disk type

An honest migration is done first and optimized afterward. That means machines arrive in the cloud at the size they had in the data center, sized for a peak that may happen twice a year, and with disks chosen out of habit.

Rightsizing isn't just “going down a size.” It's choosing the right family—there are families optimized for memory, for compute, or for input/output—and the right disk type, because storage performance and cost vary a lot between options. For a client that ran the application and the database on a single 64-core machine, splitting them into two tiers and sizing each one for its own workload, with Hybrid Benefit and reservations, cut the cost by 60% compared with the pay-as-you-go rate.

All three together, and in this order

1. Rightsize first, or you'll reserve a size you don't need.
2. Apply Hybrid Benefit to what remains, which is immediate and commits you to nothing.
3. Reserve afterward, in tranches, on the consumption that has already stabilized.

And then, the boring part: reviewing it

An optimization without follow-up lasts one quarter. That's why consumption is reported every month in the service report and analyzed in depth every quarter, with a six-month projection and recommendations by environment. It's the difference between savings announced once and a cost that is actually managed.

Two details worth being clear about from the start: cloud services consumption is excluded from VAT (IVA)—managed services are subject to it—and, if we are your partner, the invoice reaches you in Colombian pesos, billed monthly in arrears, at the day's TRM (official exchange rate) stated on the document.

Want to know how much is on the table in your case? Write to us and we'll look at it with your real consumption, not with a brochure estimate.