Azure for SMBs: what we run, and what you probably don't need

Azure is sold like an all-you-can-eat menu, and that's the trap. Faced with hundreds of services, the instinct is either to over-build (because everything sounds important) or to lift everything across as-is and watch the bill climb. Neither is necessary. The Azure footprint that actually serves a small business is small, deliberate, and boring in the best way. Here's what we run for SMBs, and the sprawl we leave on the menu.

What a sensible SMB Azure footprint looks like

For most small businesses, a good Azure estate is a short list. A few right-sized virtual machines for the workloads that genuinely need to run as servers - a line-of-business app, a database - rather than oversized instances chosen "to be safe." Immutable backup across those servers, your endpoints, and your Microsoft 365 data, with restore tests actually run and documented rather than assumed. A disaster-recovery plan you've rehearsed, so a failure is a known procedure instead of a panic. And identity anchored to your existing Microsoft 365 tenant, so you're managing one set of accounts and access rules, not two. That's the spine. Run it as one estate with one team who sees the whole picture and most SMBs are well covered.

What you probably don't need

Most of Azure's catalogue is built for problems SMBs don't have. You almost certainly don't need a container-orchestration platform, a data-warehouse-and-analytics stack, multi-region active-active redundancy, or a dedicated DevOps pipeline to run a handful of business workloads. These aren't bad services - they're answers to enterprise-scale questions, and adopting them at SMB scale buys you cost and complexity without buying you resilience. The discipline is matching the architecture to the size of the business, not to the size of the menu.

Keeping the bill honest

Azure bill shock is nearly always one of three things: instances sized far larger than the workload needs, resources left running that nobody turns off, and paying full on-demand rates for steady workloads that should be on reservations. Right-size against actual usage, shut down what isn't used, and apply reservation pricing (and Microsoft partner credits where they're available) to the predictable workloads. None of that is clever, it's just attention - and attention is exactly what an unmanaged Azure estate doesn't get. The bill climbs because no one owns it.

Where to start

If your Azure bill is creeping or you're planning a move, the first job is a right-sizing and backup review - what's running, what it costs, and whether you could actually recover from a failure. That's the front of our Cloud & Infrastructure service, which runs Azure hosting, backup, and disaster recovery as one managed estate, with your Managed IT keeping the day-to-day healthy. Because backup and recovery are also compliance controls, it's worth seeing how the Essential Eight and CIS Controls treat data recovery while you're reviewing it.

Azure rewards restraint. Run the few services your business genuinely needs, run them well, watch the three things that drive the bill, and the cloud stops being a mystery line item and becomes infrastructure you can reason about.