Azure cost optimisation for UK SMBs
Azure cost optimisation is the ongoing work of making sure your business pays only for the cloud resources it actually needs and uses. For most small and medium-sized businesses, the Azure bill does not rise because of one big mistake. It drifts upward quietly, through a handful of small and entirely recoverable leaks that nobody owns. This article sets out where that spend goes and the practical controls that bring it back, in plain English and without a lecture on architecture. As a Microsoft Direct Cloud Solution Provider, with a direct billing and support relationship with Microsoft rather than a distributor in the middle, Lanmark reviews and restructures Azure estates for UK SMBs so the monthly figure reflects what the business genuinely uses.
The aim here is not to talk you out of Azure. Used well, it is flexible, avoids large capital outlay, and scales with the business. The aim is to help you keep the bill honest, so the flexibility works for you rather than against you. If you are still deciding which platform to run in the first place, our comparison of AWS, Azure and Google Cloud for UK SMBs sets out where each one earns its place.
Why Azure bills drift upward
It helps to understand why cloud spend behaves so differently from the IT costs a business is used to. When you buy a physical server, the cost is fixed the day it arrives. It does the same job whether it is busy or idle, and the price does not change. Azure works the other way around. Almost every resource meters by the hour, so anything left running, over-sized, or forgotten keeps charging for as long as it exists.
That is the double edge of the cloud. The same flexibility that lets you spin up a resource in minutes also lets that resource keep billing long after anyone remembers why it was created. A virtual machine sized for a launch that has come and gone, a test environment nobody switched off, a disk left behind when its server was deleted: none of these announce themselves. They simply appear as a slightly larger number each month.
The drift is usually invisible month to month, which is exactly why it persists. A few pounds here and there rarely triggers a review. It is only when you look across a full year, or when a new budget forces the question, that the accumulated waste becomes obvious. By then it can be a meaningful share of the total.
Where Azure spend leaks, and the control that fixes each
This is the part worth keeping. Almost all recoverable Azure waste falls into a short list of leaks, and each one has a matching control. Read this as a checklist rather than a warning.
| Where the spend leaks | The control that fixes it |
|---|---|
| Over-provisioned virtual machines sized for a peak that never arrives, running well below capacity | Right-size against actual usage. Azure’s own recommendations show which machines are oversized. |
| Non-production resources running out of hours, dev and test environments charging 24/7 when they are used nine to five | Auto-shutdown schedules that switch them off overnight and at weekends. |
| No reserved-instance or savings-plan commitment, paying full pay-as-you-go rates on steady, predictable workloads | Commit the stable baseline to a one or three-year reservation or savings plan for a lower rate. |
| Orphaned and idle resources, unattached disks, unused IP addresses, old snapshots, empty resource groups, all still billing | A regular clean-up sweep to remove what nothing is using. |
| Storage on the wrong tier, cold and rarely accessed data sitting on hot, expensive storage | Lifecycle policies that tier data down automatically as it ages. |
| No budgets or alerts, so nobody knows until the invoice lands | Azure budget alerts set at sensible thresholds, flagging overspend as it happens. |
| No cost ownership, no single person or partner watching the trend | A monthly review rhythm so drift is caught early, not at year end. |
Taken together, these explain why an Azure estate that has never been optimised is almost always carrying waste. None of the fixes is exotic. They are ordinary housekeeping that simply needs someone to own it.
The tools Azure already gives you
One of the more useful things to know is that Microsoft provides the tools to do most of this at no extra charge. The gap for most SMBs is not the tooling, it is the time and ownership to act on what the tools already show.
Azure Cost Management and Billing gives you visibility of where the money goes, broken down by resource, and lets you set the budgets and alerts mentioned above. Azure Advisor sits alongside it and makes specific recommendations, flagging virtual machines that are oversized and workloads that would be cheaper on a reservation. Reservations and savings plans are the mechanism for committing steady workloads to a discounted rate. Microsoft documents all three in its Azure Cost Management guidance, which is worth a look if you want to see the raw figures for your own estate.
The point is that the information is usually already there. What turns it into a lower bill is someone reviewing it regularly and acting on it, which is the part that tends to fall between the cracks in a busy SMB.
How much can an SMB realistically save
It would be easy to quote a headline percentage here, and dishonest to do so, because the recoverable amount depends entirely on how the estate was set up and how long it has been left to drift. What can be said honestly is this.
The quickest wins are almost always auto-shutdown schedules on non-production workloads and a clean-up of orphaned resources, because both remove spend that delivers nothing at all. The largest structured saving usually comes from reservations on the steady baseline, where the discount against pay-as-you-go rates is substantial. Right-sizing and storage tiering sit in between, steady savings that add up.
For most SMBs that have never carried out a deliberate optimisation, the accumulated waste is meaningful, and the first review typically pays for itself several times over. The value is not only the one-off saving. It is putting a rhythm in place so the drift does not simply return over the following year.
How Lanmark approaches Azure cost optimisation
We treat Azure cost as a housekeeping discipline first and a technical exercise second, because that is where the savings actually come from.
Lanmark is a Microsoft Direct CSP partner, which means we hold a direct billing and support relationship with Microsoft rather than working through a distributor. We are also accredited with the Microsoft Support Service Designation, held by only a handful of partners worldwide, which gives us a direct line to Microsoft when an estate needs it. In practice, our approach is straightforward: review the current estate, apply the quick wins first (shutdown schedules and orphaned-resource clean-up), then make the structural changes (right-sizing, reservations, and storage tiering), and finally put a monthly review rhythm in place so spend stays controlled rather than drifting back.
Because a cost review is also the natural moment to check that Microsoft licensing is right, we often pair it with our free Microsoft 365 licence review, so you are not overspending on licences at the same time as overspending on cloud. If a cost review comes off the back of a wider cloud move, our guide to the hidden cost of a bad Microsoft 365 tenant migration covers the other half of the picture. The principle throughout is simple: pay for what you use, and keep someone watching the trend.
Frequently asked questions
What is Azure cost optimisation?
Azure cost optimisation is the ongoing work of making sure a business pays only for the cloud resources it needs and uses. It covers right-sizing over-provisioned resources, shutting down non-production workloads out of hours, committing to reservations on steady workloads, clearing orphaned resources, tiering storage correctly, and setting budget alerts. It is a rhythm, not a one-off exercise.
Why does my Azure bill keep going up?
Azure meters most resources by the hour, so anything left running, over-sized, or forgotten keeps charging. Bills usually drift upward through a handful of small leaks: over-provisioned virtual machines, dev and test resources running around the clock, orphaned disks and IP addresses, and no budget alerts to flag it. The rise is often invisible month to month and only obvious over a full year.
How can an SMB reduce its Azure costs?
Start with the quick wins: auto-shutdown schedules for non-production workloads and a clean-up of orphaned resources. Then take the structural steps: right-size virtual machines against actual usage, commit to reservations or a savings plan on steady workloads, and tier storage so cold data is not sitting on expensive hot storage. Finally, set budget alerts and a monthly review so the drift does not return.
What are Azure reserved instances and savings plans?
Both are ways to pay less by committing to use Azure for one or three years rather than paying pay-as-you-go rates. Reservations apply to specific resource types, while savings plans give a discounted hourly rate across a broader set of compute. For steady, predictable workloads they deliver the largest structured saving, often well below the on-demand price.
Do I need Azure Cost Management, and does it cost extra?
Azure Cost Management and Billing is built into Azure at no extra charge, alongside Azure Advisor, which recommends right-sizing and reservations. The tooling is free. The gap for most SMBs is not the tools but the time and ownership to act on what they show, which is where a managed partner helps.
Does Lanmark help with Azure cost optimisation?
Yes. Lanmark is a Microsoft Direct CSP partner accredited with the Microsoft Support Service Designation. We review an Azure estate, apply the quick wins first, then the structural changes such as right-sizing and reservations, and put an ongoing monthly review rhythm in place so spend stays under control.
Bring your Azure spend back under control
If your Azure bill has been drifting and nobody has had the time to ask why, that is the moment to look. Get in touch and we will review where your spend is going and what is realistically recoverable, in plain commercial terms. You can also read more about our wider Microsoft cloud services.
Lanmark is a Microsoft Direct CSP partner accredited with the Microsoft Support Service Designation, an accreditation held by only a handful of partners worldwide.