SharePoint On-Premises Architecture: What It Really Looks Like in the Wild

There’s a certain moment in every infrastructure architect’s career when someone leans across a conference table and asks, “Why are we still running SharePoint on-premises?” It’s rarely a technical question. It’s a strategic one. In the era of cloud-first mandates and evergreen SaaS platforms, choosing—or continuing—to run Microsoft SharePoint on-premises can feel like swimming upstream. Yet in regulated industries, high-security environments, and certain global enterprises, it’s not just relevant—it’s non-negotiable. Having designed and maintained multiple on-prem farms over the years, I’ve come to see SharePoint On-Premises architecture not as outdated, but as deliberate. It demands intention. And when done well, it’s surprisingly elegant. The Farm Is Not Just a Diagram On paper, SharePoint architecture looks clean: web front ends, application servers, SQL backend. Logical tiers. Clear boundaries. In practice, it’s rarely that tidy. A typical production farm might include: Multiple W