Architecture Areas

The decisions behind the platform.

Tenant Architecture

Boundaries, service design, coexistence, multi-tenant decisions, and the choices that define how a Microsoft 365 environment is structured.

Identity & Entra ID

Identity architecture, authentication, Conditional Access, synchronization, privileged access, and the trust model behind the tenant.

Collaboration Services

Exchange, Teams, SharePoint, OneDrive, voice, and the dependencies that connect Microsoft 365 workloads into one usable platform.

Hybrid & Cloud

Where on-premises systems, Azure, Microsoft 365, networking, identity, and operational dependencies meet during modernization.

Patterns & Trade-offs

Reference patterns, design alternatives, constraints, failure modes, and the reasons one technically valid option may still be the wrong architecture.

Target-State Design

Turning discovery, business requirements, risk, and technical constraints into an architecture teams can actually implement and operate.

Architecture Articles

From the architecture desk.


No Architecture articles have been published yet.

How I Approach Architecture

Understand the environment before designing the answer.

My architecture process starts with the business, the current environment, and the constraints. From there, I look at identity, workloads, security, governance, operational ownership, dependencies, and risk before defining the target state. The technology matters — but it only becomes the right architecture when those decisions make sense together.