Direct naar content

You are overpaying for Azure

Not because it got more expensive, but because it was never priced right to begin with

Gerard Zuidweg studied Financial Business Administration and spent years at ABN AMRO before co-founding OptimaData and OptimaSure. One thing he learned in banking: the most expensive mistakes aren’t the ones you make, they’re the ones you never see. It’s a principle he runs into daily at OptimaSure. Organizations that stay “within budget,” while month after month they’re paying for resources nobody uses, tiers nobody needs, and features nobody ever asked for. Not because something went wrong. Simply because nobody zoomed in. In this blog, Gerard explains why “managed” isn’t the same as “optimized” and what you can do about it.

Gerard Zuidweg

Managing Partner
Gerard Zuidweg - Managing Partner
Je betaald teveel voor Azure. Niet omdat het meer wordt, maar omdat het nooit goed stond.

“Within budget” isn’t the same as “priced right”

What still surprises me at OptimaSure: how little organizations worry about what they’re actually paying for their cloud environment. I understand why. There’s a budget agreed on, the invoice stays neatly under it, so what’s the problem?

The problem is that it’s easy to stay under budget when the budget itself was set too generously. Meanwhile, month after month, you’re paying for resources you don’t use, tiers you don’t need, and features nobody ever asked for.

I recognize that reflex from banking. A loan that’s been overpriced for years attracts far less attention than a bill that suddenly spikes. It costs you just as much. Often more.

“We’re on Azure SQL, that’s managed, so it must be fine”

It’s an assumption we run into all the time at OptimaSure. Understandable, cloud marketing is crystal clear about what the service does. Automatic backups, patching, high availability. It’s all right there on the sales page. What isn’t there:

Nobody tunes your queries. A poorly written query runs just as inefficiently on a Premium tier as on a Basic tier, it just costs you more. Nobody right-sizes your instances based on your actual usage. Azure’s default recommendation is rarely the cheapest option. Nobody tells you that you’re paying for Enterprise features you’re not even using. And nobody at Microsoft calls you up to say: “You could save 30% here.”

That’s not a criticism. It’s simply not their business model. Cloud providers get paid per resource used, not per euro they save you.

“Managed” isn’t the same as “optimized”

That’s the core problem. The cloud manages the infrastructure. Your configuration, your workload sizing, your cost structure, those are, and remain, your responsibility. It’s called the shared-responsibility model, and it’s spelled out right there in the fine print of every cloud contract.

What we see in practice: database instances set up years ago based on an expected peak load, a peak load that was never actually reached, and that have just kept running on that tier ever since. Nobody adjusts it, because the database “still works, doesn’t it.”

On average, 30 to 40% of cloud spend gets lost to exactly this kind of waste. Not because of a mistake. Simply because nobody steps in.

Insight without action is just an expensive report

Plenty of organizations already have a cost dashboard by now. Azure Cost Management, a BI tool, something from a third party. They see the numbers. But who translates those numbers into an actual change in the database configuration? Who decides whether a General Purpose tier really justifies a Business Critical tier for this workload? Who tests whether downscaling causes performance problems?

Dashboards give you insight. You only get control once someone actually acts on it.

At OptimaSure, we combine CloudXcellence tooling (connected to your Azure environment within a day, first recommendations within 24 hours) with hands-on expertise that actually implements those recommendations. No report that disappears into a drawer. Just: see it, understand it, fix it.

What does it deliver?

Clients who, after an Azure Cost Scan, discover they’ve been paying for years for instances two or three tiers too high, for features with no users, for resources that stopped being active long ago but were still quietly running. Structural savings of 20 to 30% aren’t the exception, they’re the starting point.

Not because the costs went up, but because they were never right to begin with.

Curious what this looks like in your own Azure environment? We start with a no-obligation Azure Cost Scan and show you within 30 days exactly where the money is going and what you can do about it. No commitment, just concrete numbers.

Start your Azure Cost Scan | Download the “12 Cloud Burnouts” whitepaper

Other blogs

FinOps blog
Secret Link