The moment usually arrives in a finance meeting, not an engineering review. Someone pulls the monthly cloud bill and the number is larger than anyone expected. The IT lead reaches for an explanation: some migration activity last quarter, a couple of project environments that hadn’t been wound down, the usual peaks. The CFO wants specifics. The IT lead doesn’t have them. The finance director asks whether this level of spend is normal, and the honest answer — which rarely gets said aloud — is that nobody is entirely sure what “normal” should look like.
That moment, and the uncomfortable silence that follows it, is more common in Australian enterprise environments than most organisations would care to acknowledge. And it is not primarily a technical problem. It is a governance problem wearing a technology costume.
Cloud Waste Is a Structural Problem, Not a Hygiene Issue
The prevailing narrative around cloud waste centres on idle resources: forgotten development environments left running over a long weekend, zombie virtual machines consuming compute nobody is using, storage volumes attached to workloads that were decommissioned months ago. These things are real, and any competent cloud audit will find them. But they are the visible, scannable surface of a much deeper problem — and organisations that treat cloud waste as a hygiene issue to be cleaned up periodically are missing the point.
The majority of cloud waste in mature enterprise environments is structural. It is the compounding cost of architectural decisions made under pressure, often years ago, that have never been revisited. It is the lift-and-shift migration that moved on-premise inefficiency into the cloud at cloud-scale prices. It is the compute capacity provisioned for peak loads that materialise a few days per year, paid for at full rate for the other 363. It is the multi-cloud footprint that grew organically as individual teams made independent platform choices, creating redundant capability across providers that nobody is actively rationalising. It is the auto-renewing SaaS licences that finance processes without question because the amounts sit below approval thresholds, and the storage tiers that were set at migration and never adjusted as data access patterns changed.
None of these are accidents. Each one was, at some point, a reasonable decision made with the information available. The problem is that the information environment has changed — workloads have evolved, usage patterns have shifted, pricing models have matured — and the architectural decisions have not kept pace. In a traditional data centre environment, that gap creates technical debt. In the cloud, it creates a running invoice.
The Numbers Are Large Enough to Matter
The scale of cloud waste across enterprise environments has been consistent enough across independent research that it should be treated as a structural feature of the market, not an outlier.
Evidence Snapshot
Twenty-seven percent of cloud spend across enterprise environments is estimated to be wasted — a figure that has remained stubbornly persistent despite years of FinOps investment and tooling adoption. (2025, Flexera State of the Cloud Report)
Organisations consistently exceed their cloud budgets, with the average overrun sitting at 17% above forecast — meaning teams are not just losing money to waste, they are also consistently underestimating the cost of the cloud they intend to use. (2025, Flexera State of the Cloud Report)
Workload optimisation and waste reduction remain the single top priority for FinOps practitioners globally — ahead of forecasting, governance, and AI cost management — confirming that even organisations with dedicated FinOps functions have not resolved the problem. (2026, FinOps Foundation State of FinOps Report)
Only 14.2% of organisations have reached “Run” maturity in their FinOps practice — the level at which optimisation becomes systematic and self-sustaining — while more than half remain at the intermediate “Walk” stage, with significant capability gaps across most cost management disciplines. (2026, FinOps Foundation State of FinOps Report)
For an organisation spending $5 million per year on cloud, a 27% waste rate represents $1.35 million in unrecovered spend. At $20 million in annual cloud expenditure, the number becomes $5.4 million. These are not rounding errors. They are budget lines that could fund headcount, capability uplift, or strategic investment — and they are currently disappearing into infrastructure that is either idle, over-provisioned, or simply never rationalised.
The FinOps Gap Is Real and Measurable
The discipline of FinOps — cloud financial management applied as a cross-functional practice — exists precisely because cloud cost accountability is structurally difficult. In a cloud environment, the people who make the decisions that drive cost (engineers, architects, platform teams) are not the people who pay the bill (finance) and are often not the people who feel accountable for it (operations leadership). That diffusion of accountability is not a cultural failure; it is a predictable consequence of how cloud environments are architected and governed.
Most Australian enterprise IT teams do not have a dedicated FinOps function. Cloud cost accountability tends to be distributed across engineering, finance, and operations, with no single owner who has both the visibility and the authority to act. The result is that cloud spend grows faster than cloud value, optimisation decisions get deferred in favour of delivery priorities, and EOFY becomes the moment when finance asks questions that IT cannot answer precisely.
The research is consistent on this: even organisations that have invested in FinOps tooling and established FinOps teams remain predominantly at early or intermediate maturity levels. Visibility is achieved, but the translation from visibility to action — the engineering decisions, the architectural reviews, the licence rationalisation cycles — lags behind. Dashboards are not the same as accountability, and accountability is not the same as outcomes.
The lift-and-shift problem is worth examining specifically, because it is the single most common source of structural cloud waste in Australian enterprise environments. When organisations migrate on-premise workloads to the cloud on a “move first, optimise later” basis — which was the pragmatic, often correct approach during the initial wave of cloud adoption — they carry the inefficiencies of their on-premise architecture into a billing model that charges for every idle cycle. Later never reliably arrives. The pressure to maintain production stability means that right-sizing reviews sit permanently below the line of acceptable risk, and the architectural debt compounds, quarter after quarter.
May Is the Right Time to Act, Even If It Feels Late
The instinct, when confronted with a structural problem that has been building for years, is to treat it as too large and too embedded to address before financial year end. That instinct is usually wrong, and in the context of cloud waste, it is worth examining carefully.
A pre-EOFY cloud audit is a finite, defined piece of work. It does not require a multi-year FinOps transformation programme. What it requires is a systematic review of cloud spend against actual utilisation — identifying workloads that are over-provisioned relative to observed usage, storage tiers that have never been rationalised, licence commitments that auto-renew without review, and environments that exist without clear ownership or active use. That work can be scoped, executed, and acted upon within a financial quarter.
The savings from that work reduce the final quarter’s cloud bill. More importantly, the process of doing it establishes the visibility and the governance habits that make FY27 materially more controlled than FY26. Organisations that run a pre-EOFY cloud audit in May are not just recovering sunk cost; they are installing the foundation for an accountable cloud posture going forward.
The alternative — deferring until after June 30, planning a proper review for the new financial year — is a choice that has been made, on average, several years in a row in most enterprise environments. The bill reflects that.
In the environments I work with at Orro, the gap between what organisations believe they are spending efficiently and what the audit reveals is consistently larger than expected — and the source of the gap is rarely the zombie instances. It is the workloads that were migrated and never right-sized, the licence commitments that were commercially sensible at signing and have since been superseded by usage changes, and the multi-cloud sprawl that nobody has a complete map of. The organisations that find this uncomfortable are the ones who act on it. The ones that find it surprising are the ones who wait.
If you want to start with a structured self-assessment, the EOFY Technology Audit Checklist: 40 Questions to Ask Before You Sign Anything covers cloud waste identification as one of its five audit domains — it is a practical starting point for any organisation that wants to run its own review before June 30. For the broader strategic picture on EOFY technology investment, the CFO’s Technology ROI Guide: Making Smarter Decisions in the Final Quarter provides a framework for connecting cloud financial management to board-level investment decisions.
Orro helps Australian organisations get control of their cloud environments — from cost visibility and FinOps advisory through to managed cloud, security, and infrastructure optimisation. To speak with our team about a pre-EOFY cloud review, visit orro.group/contact or reach out to your Orro account manager directly.
Further Reading
- Are You Overpaying for Your Microsoft Licensing? — Explores the hidden cost of Microsoft licence sprawl and how organisations can recover value from their existing commitments.
- ValidPro® — Orro’s procurement validation service, relevant to the licence renewal and auto-renewal waste arguments in this article.
- Orro Managed Cloud — Overview of Orro’s managed cloud services, including FinOps advisory and cloud cost optimisation.
- Trust & Security — Orro’s certifications and security posture, for readers who want to understand Orro’s governance credentials as a managed cloud partner.
