Shadow IT
Why bad tagging makes your cloud costs unmanageable
You’ve got AI agents, dashboards, and reports. You can see exactly what you’re spending on Azure each month. But the moment someone asks “who’s responsible for this cost?”, the room goes quiet. Not because the data isn’t there, but because the context is missing. In this blog, Henk van der Valk, co-founder of OptimaSure, explains how tagging makes the difference between paying blindly and steering deliberately.
Azure Cost Management gives you excellent numbers. You can see what you’re spending per day, per week, per month. But try zooming in. Where is that cost actually coming from? Which application is using these resources? Which team is responsible?
Without context, you hit a wall. You’ve got numbers, but no story. And an invoice with no story leads to meetings where everyone looks at each other and nobody can explain anything, while the real question is sitting right there on the table: is all of this cost actually necessary?
This is Cloud Burnout #6. A problem that rarely stands out right away, but that, in the meantime, causes chaos in your cost management, friction between IT and finance, and structurally inflated cloud costs.
This problem is almost never created on purpose. Most organizations actually start out reasonably tidy. The first resources go up, there’s a clear overview, and everyone still knows what’s running where.
But as the environment grows, it slips. New projects start. Teams work faster and more independently. Resources get spun up “just quickly.” And tagging? That can happen later.
Later never comes. What’s left is an environment where resources have no owner and tags haven’t kept pace with the organization. The original owners have left the company, moved to a different department, or cost centers have changed. Tags are missing entirely, and nobody knows what’s still relevant.
At first glance, bad tagging looks like an administrative detail, something that could be “tidier.” In reality, it strikes at the core of your cloud management.
Without tagging, you can’t see who’s using what, or why. Costs land nowhere in particular. And when costs land nowhere, nobody feels responsible for them. Nobody steers toward efficiency. Nobody actively optimizes.
The result: waste just keeps piling up. Not because people want it to, but because they can’t see it.
For SMEs just getting started, Azure offers several ways to set this up properly, automation through templates as part of Infrastructure-as-Code deployments, or governance through policies. But that quickly turns into an IT matter, even though the impact is organization-wide.
Tags are a good starting point for enabling cost management reporting, but they almost never deliver 100% coverage on their own. Without consistent management and periodic reviews, your data quickly becomes unreliable. Reports lose their value. Optimizations end up based on assumptions instead of facts. And every report needs to be double-checked.
Once tagging is properly set up, the conversation shifts. From “cloud costs are higher than expected again” to “Team X used more this month because of workload Y.”
Suddenly you get transparency: everyone can see what’s happening. Ownership: costs belong to teams. Steering: decisions get made deliberately. That’s FinOps in practice.
Tagging isn’t a goal in itself. It makes what’s happening in your cloud environment visible, but on its own it doesn’t fix anything. The value only appears once you translate that insight into ownership.
That’s where cost allocation comes in. Tagging brings structure to your data. Cost allocation makes sure costs actually land with the right teams. Without tagging, you can’t allocate. Without allocation, behavior doesn’t change. Want to go deeper on this? Read our blog on Cloud Burnout #4: cost allocation.
A lot of organizations underestimate that tagging isn’t a one-time action. It’s not a checklist item you tick off and forget.
Figure 1. The number of untagged cloud resources can grow fast.
It starts with a clear standard, think tags like owner, environment (prod, test, dev), cost center, MaxBudget, and application. Next, you need to enforce tagging, for example through Azure Policy, so resources can’t be created without tags in the first place. And after that, keep monitoring, cleaning up, and improving. Only then does it actually work.
At OptimaSure, we see tagging as the foundation for control over cloud costs. Without structure, you can’t steer.
We start with insight: where is tagging missing, where is it going wrong, and what does that mean for your costs. Then we set up a workable structure that fits your organization. And we make sure it keeps working, with policies, automation, and continuous monitoring.
Tagging seems small, but the impact is big. Without tags, you see the total cost, but not what’s behind it. And as long as you don’t know that, you can’t steer.
The good news: this problem is relatively easy to fix once you approach it the right way. Does this sound like your Azure environment? Then you’re probably paying more than you need to.
Want the complete approach right away? Download our free “12 Cloud Burnouts” whitepaper and see every pitfall eating into your cloud budget, including concrete action plans for each burnout.