An Azure bill increasing every month is usually not Microsoft putting its prices up. Most of the time it is something inside your own tenant: autoscale settings that never scale back down, virtual machines sized for a workload that no longer exists, reservations paid for but not used, data sitting in expensive storage tiers, and resources left behind when projects finished.

In other words, the bill grows because nobody owns it. Finance sees a line rising without explanation. IT sees a platform that technically works. The money disappears in the gap between the two.

This guide is for both of you. You might be the Finance Director or Managing Director closing out the year and questioning a cloud cost that has grown unchallenged. Or you might be the IT lead who inherited an Azure environment and knows it has accumulated clutter. Either way, every cause below is identifiable, measurable and fixable. Here is where to look.

The Line Item Nobody Owns

The real problem is accountability, not technology. Ask finance teams about cloud costs and the same frustrations come up. The bill rises without explanation. Nobody can say exactly what the business is paying for. Nothing visibly changes to justify the increase.

Azure makes it effortless to create resources and silent about forgetting them. There is no renewal meeting, no purchase order and no invoice that forces a decision. The spend simply compounds.

The wider data points the same way. In Flexera’s 2026 State of the Cloud Report, organisations estimated that 29% of their infrastructure and platform cloud spend is wasted, the first rise in five years. That is a global survey of 753 cloud decision-makers, most of them in the US, but the causes it points to apply to any Azure tenant. By the time Finance challenges the number, usually at year-end budget setting, the environment holds months or years of drift that no single person can explain.

How to Stop Your Azure Bill Increasing: The Five Hiding Places

Stopping an Azure bill increasing starts with knowing where unmanaged spend hides. Across the education, construction and professional services environments we look after, the same five culprits come up again and again.

1. Autoscale settings that never scale back

Autoscale only works in both directions if it is told to. A minimum instance count raised for a busy period months ago keeps capacity running that nobody needs. So does a scale-out rule with no matching scale-in rule, which Microsoft’s own guidance warns against. The setting was right when it was made. Nobody went back to change it.

2. Oversized Azure VMs

Machines were provisioned generously at migration to be on the safe side, and never right-sized against actual utilisation. A VM using a fraction of its CPU and memory for six months is paying for capacity it never touches.

3. Azure reserved instances unused

Reservations bought against workloads that have since changed shape mean you pay twice: once for the reservation, and again at full rate for the replacement workload. It is the one hiding place where you can be charged twice for the same job. The timing matters too. From 1 February 2027, new reservations for virtual machines, App Service and several database services can no longer be exchanged. A mismatch bought after that date is locked in for the full term.

4. Storage tier drift

Data that should have moved to cool, cold or archive tiers is still sitting in hot storage. It accrues premium rates for files nobody has opened in a year. Nothing flags it, because nothing is broken.

5. Orphaned Azure resources

Plenty of leftovers keep billing after the work they supported has finished: unattached disks, unused static public IP addresses, load balancers with rules still configured, and test environments from projects that finished long ago. VMs shut down from inside the operating system, rather than deallocated in Azure, keep billing for compute too. None shows up as a single obvious cost. Together they can account for a large share of the drift.

If your organisation spends tens of thousands of pounds a month on Azure and the bill keeps climbing, book a free Azure cost review with DMS. Whether or not you can explain the increase, we’ll show you where your setup could be costing more than it needs to, with no obligation.

What the Drift Actually Costs

Here is an illustration of what the Flexera figure means against a real budget. Suppose an organisation spends £20,000 a month on Azure and its waste matches the industry estimate of 29%. It would be paying roughly £5,800 a month, or around £69,600 a year, for capacity nobody is using. That is a senior hire or a significant security investment, spent on nothing.

Your own number may be lower or higher. The point is that it is knowable in an afternoon, and it has probably never been calculated.

There is also a timing reason not to wait. Microsoft does adjust its prices, and older virtual machine series are likely to become more expensive to run, not less. On top of that, from 1 February 2027 Microsoft is ending reservation exchanges for virtual machines, App Service and several database services. Waste carried into next year is likely to cost more and will be harder to correct.

Cloud Cost Governance: Keeping Spend Down After the Cleanup

A one-off cleanup without cloud cost governance simply resets the clock. Governance means putting rules in place so spend cannot drift silently again:

• Resource tagging, so every item has a named owner and a cost centre.
• Budgets and alerts in Microsoft Cost Management, so anomalies surface within days rather than at year-end.
• A policy that nothing is deployed without an expiry or review date.
• One named person who owns the monthly bill and reports on it in business terms, not technical ones.

The same discipline applies to Microsoft 365. Licences still assigned to leavers, and tiers that no longer match what users need, drift in exactly the same way. A joined-up review of Azure and Microsoft 365 managed services usually finds savings in both.

This is where most internal efforts stall, because governance is ongoing work rather than a project.

Step by Step: Running Your Own Azure Cost Health Check

1. Find the fastest-growing costs. Open Microsoft Cost Management in the Azure portal and view costs by resource group for the last six months. Identify the three groups with the steepest growth, because that is where your effort pays back fastest.
2. Check reservation utilisation. Look under the Reservations blade. Any reserved instance running below full utilisation is money committed but not consumed. Exchanges are still available for now. From 1 February 2027, Microsoft is ending them for reservations covering VMs, App Service and several database services. Existing reservations keep one final exchange after that date, so decide how you would use it before you need it.
3. List orphaned resources. Look for unattached managed disks, static public IP addresses with nothing associated, and VMs that are stopped but not deallocated. These bill continuously whether or not anything uses them. Even a deallocated VM still incurs charges for its disks.
4. Review VM sizes. Compare sizes against actual CPU and memory use in Azure Advisor. Advisor looks back seven days by default, so change the lookback period to 30 days or more in Advisor’s configuration for a fairer picture. Flag anything consistently running well below capacity as a right-sizing candidate. Note any VMs running on older series while you are there, as these are candidates for moving to a current series at the same time.
5. Audit storage accounts. Find data in the hot tier with no recent access, and apply lifecycle management rules to move it to cool, cold or archive tiers.
6. Set up ongoing control. Set a budget with alert thresholds in Cost Management (Microsoft’s tutorial takes ten minutes). Document every finding with an owner and a decision date. Book a recurring monthly review so the drift cannot restart.

What to Watch Out For

• Buying reservations before right-sizing. Committing to one or three years of an oversized VM locks the waste in rather than removing it. This matters even more from February 2027, when new reservations can no longer be exchanged.
• Deleting orphaned resources without checking dependencies. A disk that looks abandoned may belong to a backup or disaster recovery process.
• Moving data to cheaper tiers without checking the small print. Cool, cold and archive tiers charge an early deletion fee if data is moved or deleted within 30, 90 and 180 days respectively. Archived data is offline and must be rehydrated before it can be read, which can take hours. Frequently used data belongs in hot storage.
• Treating the exercise as a one-off project. Without ongoing governance, the drift returns within months.
• Letting Finance and IT run separate reviews. Each sees half the picture, and the savings sit in the overlap.

Quick Checklist

• Pull your last six months of Azure invoices and chart the trend before any meeting.
• Assign a named owner for the Azure bill, with a monthly reporting duty.
• Run the Azure Advisor cost recommendations report today. It is free and takes minutes.
• Check reservation utilisation and note anything below full use.
• Identify any VMs running on older series and plan their move to current ones.
• Tag every resource group with a cost centre and project owner.
• Set budget alerts in Microsoft Cost Management at sensible thresholds.
• Schedule orphaned resource sweeps quarterly, with findings logged.
• Put an Azure cost review in the 2027 budget planning calendar.

Frequently Asked Questions

How do I find orphaned resources in Azure?

In the Azure portal, filter managed disks by unattached status, list static public IP addresses with no associated resource, and identify VMs that are stopped but not deallocated. Azure Advisor and Azure Resource Graph queries will surface most of them. Always confirm with the resource owner before deleting, as some apparently idle items support backup or recovery processes.

Should I buy Azure reserved instances to reduce spend?

Only after right-sizing your workloads, because a reservation locks in whatever size you commit to. Reservations suit stable, predictable workloads that will run continuously for the term. Azure savings plans for compute give more flexibility where workloads change. From 1 February 2027, new reservations for virtual machines, App Service and several database services can no longer be exchanged, so the commitment needs to be right first time.

What is Azure storage tier drift?

Storage tier drift is when data remains in expensive hot storage long after anyone stops accessing it, because nobody set lifecycle rules to move it to cool, cold or archive tiers. It accumulates silently and often accounts for a meaningful share of unexplained bill growth. Lifecycle management policies fix it automatically once configured.

How often should we review our Azure costs?

Monthly at minimum, with budget alerts running continuously in between. A deeper structured review covering reservations, VM sizing and orphaned resources works well quarterly and should always align with annual budget setting. Year-end is the natural moment for a first full review if you have never done one.

What does an Azure cost review with DMS actually involve?

A structured review audits your tenant for the main causes of unmanaged spend: scaling configuration, VM sizing, reservation utilisation, storage tiers, orphaned resources and governance gaps. You receive clear findings and recommended actions, explained in business terms.

A Number You Chose, or a Number That Happened to You

You now know why the bill is rising and where the money is hiding. The question is who acts on it before the 2027 budget is signed off.

If the Azure line goes into next year’s budget unchallenged, the drift is funded for another twelve months and the conversation gets harder, not easier. A few hours of structured review now decides whether next year’s cloud spend is a number you chose or a number that happened to you.

DMS has been a Microsoft partner since 2005, and bringing structure to Azure tenancies that have grown without it is a large part of what we do. We can help you sort it, and we will keep you informed throughout.

Find out where your Azure spend could be working harder before budget season closes. If you spend tens of thousands a month on Azure, book your free Azure cost review. Otherwise, book a free 15-minute call or contact the team on 01322 420140, and go into 2027 with a cloud budget you’ve actually checked.