News, insights, and practical perspectives on Azure, cloud architecture, and strategic IT leadership.

By Christian Medewitz The LinkedIn Search Is the Problem You know the routine. A good conversation wraps up, someone says "let's connect," and out comes the phone. Not to save a contact properly — to open LinkedIn and type a name into the search bar, hoping you spelled it right and picked the correct person out of a dozen matches. That's not networking. That's a workaround for the fact that exchanging contact details still doesn't just work. It's a small thing, but it's also

I've scoped a lot of IT projects. There's one pattern I see almost every time, regardless of industry or company size: the foundation underneath the project is weaker than anyone wants to admit. Networking that was never properly segmented. Identity that grew organically instead of by design. Change management that exists on paper but not in practice. And, more often than companies like to admit, a service provider that's quietly ended up owning the process and the tooling —

Intent sizing, RoCE vs iWARP, port speeds, switchless vs Top-of-Rack, and SDN microsegmentation — the networking decisions that make or break an Azure Local cluster under failover, from real edge deployments.