What is SD-WAN, and when does a business actually need it?
SD-WAN is a way of connecting several business locations over ordinary internet links while keeping control of how traffic travels between them. It solves a real problem, and it is sold to a great many businesses that do not have that problem.
- SD-WAN manages how traffic is routed across multiple internet links, by software rather than by hardware configuration.
- It earns its place when you have several sites, heavy cloud use, or connections that fail at inconvenient times.
- A single-office business with one good connection generally does not need it, and we will say so.
What the letters mean
A WAN — wide area network — is simply the network that connects your locations to each other and to the internet. The "SD" stands for software-defined, which means the decisions about how traffic travels are made by software, centrally, rather than configured link by link on each piece of equipment.
That is the whole idea. What used to require a technician configuring a router at each site becomes a policy applied everywhere at once, and the network can react on its own when a link degrades.
What it replaces
Traditionally, connecting business sites reliably meant buying dedicated private circuits from a telecom provider. They were dependable and they were expensive, and every change meant a work order.
- Ordinary internet links, used deliberately. Two commodity connections at a site, with the software deciding which traffic uses which.
- Failover that happens by itself. When one link degrades, traffic moves without anyone noticing at the moment it matters.
- Policies instead of configurations. A rule like "voice traffic takes the most stable path" is written once and applied everywhere.
- Direct routes to cloud applications. Traffic bound for Microsoft 365 does not have to travel to head office first just to turn around.
When it is genuinely worth it
There are five situations where the argument makes itself. If none of them describes you, the honest answer is that this is not your priority.
| Situation | What SD-WAN changes |
|---|---|
| Several locations | One set of rules instead of one configuration per site. |
| Heavy cloud and Microsoft 365 use | Traffic takes a direct path rather than a detour through head office. |
| Voice or video that matters | The stable path is chosen deliberately, not by accident. |
| Links that fail occasionally | A second ordinary connection becomes real redundancy. |
| A site that opens or moves often | Bringing it online is a policy, not a project. |
When you do not need it
We would rather write this section than have you buy something on the strength of an acronym.
- One office, one good connection. There is nothing to route between. A second link for redundancy is simpler and cheaper.
- Everything already in the cloud, everyone remote. If there is no office network to speak of, the problem SD-WAN solves has already gone away.
- The real problem is Wi-Fi coverage. A building coverage problem is not fixed by anything happening between sites.
- The real problem is the connection itself. Software routing cannot invent capacity that the link does not have.
SD-WAN is not a security product
This is the confusion worth clearing up, because the marketing rarely does. SD-WAN decides how traffic travels. It does not decide what is allowed through, it does not inspect what crosses the boundary, and it does not notice when someone is already inside.
Those are the jobs of a firewall, of application filtering and of detection, and they remain separate questions — the capabilities our network security service manages. A vendor bundling them together is selling you a package, which can be convenient — but the capabilities are still distinct, and you should know which ones you are actually getting.
Several locations, and a network that grew one site at a time?
30 minutes to look at how your sites actually connect today, and whether SD-WAN would change anything — including if the answer is no.