Azure Cost Management Tips for NHS Organisations: Cut Cloud Spend by 30% in 2026
The real cost of Azure overspend in the NHS
Most NHS organisations don't realise they're burning money on Azure until it's too late. A healthcare trust running 50 virtual machines, databases and app services across Azure can easily rack up £15,000 to £25,000 per month in charges. When you're already stretched for budget, that's a ward's worth of equipment, or training for a team of IT staff.
The problem isn't Azure itself. The platform is genuinely cost-effective when managed properly. The real issue is that many NHS IT teams inherit cloud infrastructure without proper governance, or they provision resources for peak demand and never scale them back down. A test environment spins up. A development database gets left running. Reserved instances expire and services revert to on-demand pricing at double the cost.
This article walks through five concrete strategies that NHS organisations are using right now to cut Azure costs by 25 to 35% without reducing capability.
1. Right-size your compute instances
This is the quickest win. Most NHS trusts overprovision virtual machines by 30 to 50%.
A typical scenario: IT provisions a Standard_D4s_v3 instance (4 cores, 16GB RAM) for an internal application, because "we might need headroom". In reality, the application uses 40% CPU and 25% memory on its busiest days. Over a year, that's roughly £3,500 wasted on unused capacity.
Azure's built-in Advisor service flags these machines automatically. It runs a free analysis across your entire subscription and recommends downsizing opportunities.
How to action this:
For an NHS trust with 40 overprovisioned VMs, this alone typically saves £3,500 to £5,000 monthly.
2. Use reserved instances for predictable workloads
This is where you get the biggest leverage.
Azure Reserved Instances (RIs) are a commitment to use specific compute resources (virtual machines, databases, storage) for 1 or 3 years, in exchange for a 30 to 65% discount on the on-demand price. For NHS organisations running stable systems like patient records databases, appointment management systems, or core business applications, this is almost always the right move.
A Standard_D4s_v3 instance costs roughly £0.40 per hour on-demand in UK regions. With a 1-year reserved instance, you pay around £0.26 per hour (35% discount). Over 12 months of continuous use, that's a saving of about £1,250 per VM.
The smart approach for NHS trusts:
For an NHS organisation currently spending £40,000 per month on Azure, a balanced mix of right-sizing and reserved instances typically cuts costs to £27,000 to £30,000 within 3 months.
3. Implement proper resource tagging and cost allocation
You cannot manage what you don't measure.
Most NHS IT teams know their total Azure bill, but they have no idea which department (Cardiology, Emergency, Finance, IT itself) is driving the cost. This makes it impossible to justify cloud spend to budget holders or to spot which teams are wasting resources.
Azure tags are free metadata labels you attach to resources. A single virtual machine might be tagged:
Once resources are tagged consistently across your subscription, you can generate cost breakdowns by department, application, or cost-centre in the Azure Cost Management tool. Suddenly, IT can show the Emergency Department exactly what their cloud spend is, and where it's going.
How to make tagging stick:
Tagged costs also help NHS procurement teams understand cloud spending across the organisation, and support business cases for Azure migration when you can prove ROI by application or department.
4. Enable auto-shutdown for non-production environments
Development and test environments in the NHS often run 24/7, even though they're only used during business hours.
A test SQL Server instance running continuously costs roughly £400 per month. If you shut it down outside business hours (5 PM to 8 AM weekdays, all day weekends), the cost drops to £120 per month. Annual saving: £3,360 per instance.
Azure has a free auto-shutdown feature built into most compute resources. You set a time (say, 6 PM) and the resource powers down automatically. You can add a small notification email so your team knows it's happening.
This works for dev VMs, test databases, and sandbox environments. Never apply it to production systems.
Most NHS trusts find 15 to 25 non-production resources they can auto-shutdown, saving between £4,500 and £8,500 per year with zero service impact.
5. Use Azure Hybrid Benefit if you already own licenses
If your NHS organisation has a Software Assurance agreement with Microsoft (which most large NHS trusts do), you can apply those licences to Azure virtual machines and databases. This typically saves 40 to 55% on compute costs for Windows Server and SQL Server workloads.
For example, running SQL Server Standard on Azure costs roughly £0.65 per hour on-demand. With Azure Hybrid Benefit (using licences you already own), it drops to £0.19 per hour.
Check with your Microsoft account manager or licensing team to confirm what licences you have rights to use.
Getting help with Azure cost governance
If your NHS organisation is ramping up cloud infrastructure and cost management isn't yet a priority, now is the time to build it in. The difference between managed and unmanaged cloud spend is often £50,000 to £100,000+ per year for a medium-sized trust.
If your IT team is new to Azure cost management and wants structured support, the Microsoft 365 Administrator and Azure Administrator programmes at SmoothOps 365 include a dedicated module on cost governance. You'll learn how to implement these strategies in a live environment, and get hands-on with the Azure Cost Management and Advisor tools. Join the waitlist for the Azure Administrator programme and we'll notify you when the next cohort opens.
Frequently asked questions
How much can an NHS trust typically save with Azure cost management?
Most NHS organisations see savings of 25 to 40% within the first three months of implementing proper cost governance, depending on how much technical debt exists in their cloud estate. A trust with £50,000 monthly spend typically reduces that to £30,000 to £37,500 through right-sizing, reserved instances, and shutting down unused resources.
Do Azure cost management tools cost extra?
No. Azure Advisor (recommendations), Azure Cost Management (cost tracking and breakdown), and auto-shutdown are all included free with any Azure subscription. You only pay for the compute resources themselves, not for the tools to manage them.
Can we apply reserved instances to existing virtual machines?
Yes. You can purchase reserved instances for any VM type currently running in your subscription. The discount applies automatically once you buy the reservation, even if the VM was created and running on-demand before the RI was purchased.
What happens to a reserved instance commitment if we shut down the VM?
The reserved instance commitment continues for the full term you purchased, even if the VM is powered off. The discount applies to the next matching resource you create or run in your subscription (you can move RIs between resources of the same size and region). This is why it's important to only reserve stable, long-term workloads.
Should we reserve database costs as well as compute?
Yes, if the database runs continuously with predictable size (which patient records and appointment systems usually do). Reserved instances for Azure SQL Database typically save 35 to 50%, similar to compute. Again, aim to reserve 60 to 70% of your database spend and leave 30 to 40% on-demand for development and temporary workloads.
SmoothOps 365 runs live instructor-led training every Saturday and Sunday. 3 months. 50 contact hours. Keep your job while you train.