Firewall & routing
The boundary between your office and the internet: rules, firmware updates, and a record of who is allowed to change them.
Networking / The office's own category
The network is not just “whatever the firewall does.”
A firewall appliance blinking quietly in a closet is not a network plan. The office network — firewall, Wi-Fi, wired ports, and remote access — deserves the same named, maintained category every laptop already gets.
Lire cette page en françaisWhy this needs its own name
Devices get a plan. The network in between often doesn't.
Device lifecycle gives every laptop a repeatable plan: provision, maintain, support, retire. The network hardware sitting between those laptops and the internet often gets none of that. A firewall, an access point or two, and a switch get installed once at setup, then disappear from anyone's attention until something stops working.
Four pieces, one standard
Networking is more than the box that blinks.
Wi-Fi
Coverage, a genuinely separate guest network, and passwords that are not still the ones set at installation.
Wired network
Switches and cabling that mostly go unnoticed until a port stops working or a new desk needs one.
Remote access (VPN)
A defined, revocable way for specific people to reach office resources from outside — not a permanent hole punched in the firewall.
Who owns what
Maintenance and business decisions are not the same line item.
| Area | What can be maintained | What stays a business decision |
|---|---|---|
| Firewall & rules | Firmware updates, rule hygiene, a change log | Which sites or services are allowed, and why |
| Wi-Fi | Access point health, guest network hygiene, password rotation | Coverage build-out for a new space |
| Wired network | Port and switch health, cabling documentation | New construction or office moves |
| Remote access | Access provisioning and prompt revocation | Who is approved for remote access, and to what |
Before you trust the blinking light
A network that has quietly worked for years is not a documented one.
Most offices can answer very few of these questions on request — which is exactly why they are worth asking before something forces the answer.
- Who has the administrator password for the firewall, and when was it last changed
- Whether firmware updates happen on a schedule or only after something breaks
- Whether the guest Wi-Fi network can actually reach the business network it is supposed to be separate from
- Who is still listed for remote access after they changed roles or left
What this does not replace
Ordinary office connectivity, not carrier engineering.
This is not a claim of data-centre network engineering, carrier-grade infrastructure, or specialized industrial networks — those need their own dedicated project scope. It also does not replace the internet service provider itself; see how that relationship is coordinated separately . Ordinary office connectivity — the equipment your team actually owns and depends on — is what gets a maintained standard here.
Next step
Turn your IT context into a clear scope.
A scope conversation covers your team, Microsoft 365, devices, vendors, and responsibilities to transfer. You leave with the scope questions that need answers—without sharing secrets.
Discuss your IT scope