"Local IT support" means something different now than it did ten years ago. The server is gone. The tenant is in a Microsoft data centre and can be administered from anywhere with a laptop. So the honest question is not whether your provider is round the corner, it is which parts of the job genuinely need someone in the building, and whether they can do those parts too.
This is a look at what local support actually buys you, what it does not, how it is priced in the UK, and the questions worth asking before anything gets signed.
Most Microsoft 365 work is remote by nature. Tenant configuration, licensing, mailbox migration, conditional access, Intune policy, mail flow troubleshooting, permissions, all of it happens in a browser and a PowerShell window. Distance is irrelevant for any of that.
These are the jobs where physical presence genuinely changes the outcome:
| Task | Why on site |
|---|---|
| Network hardware, firewalls, switches, access points | Cables, console ports and reboots. Nobody has ever fixed a dead switch over Teams |
| Printers and scan to email | Half the fault is always at the device. Scan to email breaks reliably every time SMTP AUTH gets locked down |
| New starter handover | Twenty minutes sat with someone beats an hour of tickets over the next fortnight |
| Failed or physically damaged devices | Swap the hardware, recover the data |
| Cyber Essentials Plus assessment | Involves hands-on verification of endpoints |
| Quarterly reviews with the business owner | Strategy conversations go differently in a room than on a call |
That list is not nothing. It is also not a full time job for most businesses under fifty people. A sensible arrangement is remote as the default with on-site available, priced honestly, rather than a provider pretending everything needs a van.
Reactive helpdesk is the visible part and the least valuable. Anyone can reset a password. The things that separate a decent provider from an expensive one:
Three models cover almost everything you will be quoted.
| Model | How it works | Suits |
|---|---|---|
| Per user per month | Fixed fee per licensed user covering a defined scope of support | Businesses that want a predictable budget line and consistent usage |
| Capped hours block | A set number of support hours per month at a fixed fee, with overage charged at a stated rate | Smaller teams with variable demand who want a known floor |
| Ad hoc hourly | Pay for what you use, usually with a minimum charge per incident | Very small or very stable setups with an internal person who handles the basics |
Two things to check in any quote:
This is the part of an agreement most worth reading slowly.
A response target is how quickly someone acknowledges your ticket and starts work. That is something a provider controls and can reasonably commit to, within stated business hours.
A resolution time is how quickly the problem is fixed. On a platform your provider does not own, that is not always in their gift. If Exchange Online is degraded in the UK South region, no local support company is resolving that. They can keep you informed, apply a workaround, and escalate to Microsoft. They cannot promise a fix time.
So if a proposal guarantees resolution within a fixed window, read it carefully. Either there are exclusions doing a lot of work further down the document, or the commitment is not meant seriously. A stated response target within defined business hours, with an escalation path and an out of hours arrangement priced separately, is the honest version.
The single most important item on that list is the last one. Your Microsoft 365 tenant is your business. Email, files, identities, all of it.
What you want to see:
If a provider resists any of that, the conversation is over. Losing access to your own tenant during a supplier dispute is a scenario worth avoiding by design rather than by trust.
Some of the useful local context is not about the drive time:
On that last point, the scheme got stricter in April 2026. Version 3.3 of the requirements and the new Danzell question set introduced automatic failures for missing MFA on cloud services that offer it, and for high-risk security updates applied slower than 14 days. If certification is on your roadmap, ask any prospective provider what they know about that change. The answer tells you a lot.
For a business of 10 to 30 people running on Microsoft 365, a sensible arrangement looks like this:
None of that requires the provider to be in the next street. It does require them to be close enough to turn up when turning up is the only thing that works, and organised enough that they rarely need to.
If you want to sanity-check your own setup first, start with securing Microsoft 365 for a small business and auditing your tenant security. Both are free to work through and will tell you what shape you are in before you speak to anyone.
We are two engineers covering Wigan, Warrington, St Helens, Skelmersdale, Ormskirk and the wider North West.
See Microsoft 365 SupportMore in this series: all Klariq guides.