Service

Networking from the closet to the cloud

DNS · Routing · Hybrid · Azure

My day job is enterprise Azure networking at Microsoft — VNETs, datapath, Private Link, Private Resolver, the gnarly hybrid scenarios. I bring that same depth to small and mid-size Central Valley clients, scaled down to fit. Whether it's a flaky office LAN, a site-to-site VPN, or a real cloud network design, I've probably broken (and fixed) something like it before.

Get a network review See business IT

What I set up

LAN/WLAN design and clean-up — UniFi, Aruba, Meraki, the lot
DNS that actually resolves (and resolves quickly)
Site-to-site VPN and Tailscale-style overlays
Azure VNET, Private Link, Private Resolver, peering, BGP
Datapath troubleshooting when "the internet is slow"
Diagrams that match the live network, kept current

How it works

Map

I draw what you actually have, not what the previous person said you had. That alone fixes things sometimes.
Tune

Fix routing, DNS, segmentation, and the noisy edges. Everything tested before it's the new normal.
Document

Diagrams and runbooks land in your repo. If I get hit by a truck, you don't have to start over.

Tools I lean on

Five-person office or three sites — same process: map it, fix DNS and routing, write it down.

Pricing

Network Consulting

$75 / hour or quoted project

LAN/WLAN design, DNS, VPN, Azure VNET work, and datapath troubleshooting. Larger engagements can be scoped and quoted flat. Travel or after-hours work quoted separately.

See the full pricing page for all rates.

Common questions

How much does this cost?

Network work runs $75 an hour. Larger projects — full LAN redesigns, Azure VNET builds, multi-site VPN setups — can be scoped and quoted as a flat fee. See the pricing page for details.

Do you sell hardware?

No. I'll recommend what fits and help you procure it directly. No markups, no kickbacks.

Can you fix something Microsoft-side?

Often yes, since I work in that world daily. If something genuinely needs an escalation, I know how to get one.

My ISP says it's not their problem. Is it?

Maybe, maybe not. Bring me into it — I've made carriers admit to a lot.

Can you do this remotely?

Mostly yes. Anything cloud is remote. Onsite is reserved for cabling, hardware swaps, and first-time site visits.

Network getting in your way?

Bring me your diagram (or your "we don't have one"). I'll find the bottleneck.

Start the conversation