Chapter purpose
The supplied Exchange books teach enduring concepts such as directory dependency, transport, stores, client access and security. Modern Exchange consolidates and changes those components, so this chapter maps the lineage without treating legacy roles as current.
Learning objectives
- Explain current Mailbox and Edge Transport roles.
- Describe Exchange dependence on Active Directory.
- Compare on-premises, Exchange Online and hybrid.
- Recognize front-end/back-end terminology as historical.
Why this matters in a real company
Email remains business critical, but organizations can choose cloud, on-premises or hybrid. The decision affects security, availability, licensing, skills and recovery.
1.1 What changed since Exchange 2003
Exchange 2000 and 2003 separated concepts into front-end/back-end servers, protocol services and information stores. Modern Exchange Server uses a Mailbox server building block that contains transport, mailbox database and client access services, with an optional Edge Transport role.
The old books remain useful for learning how messaging depends on DNS, SMTP, directory services, storage and operational security, but their setup screens and server-role topology are historical.
1.2 Exchange Server Subscription Edition is the current on-premises line
Microsoft current documentation covers Exchange Server Subscription Edition. The Mailbox role provides transport, mailbox database and client access functions, while Edge Transport can provide perimeter transport.
Exchange 2016 and 2019 reached end of support in October 2025, so any new on-premises plan should be checked against the current Exchange SE supportability matrix.
1.3 Exchange Online changes the responsibility boundary
With Exchange Online, Microsoft operates the mailbox service and much of the mail-security front door. The organization still owns domains, identities, DNS records, access policy, retention choices, application mail integrations and security configuration.
Cloud email removes server maintenance, not architecture.
1.4 Hybrid is a bridge between organizations
A hybrid deployment connects on-premises Exchange and Exchange Online so mail routing, recipient coexistence and mailbox migration can work across both. Microsoft configures trusted hybrid transport using TLS.
Hybrid should exist because the business or migration design needs it, not because it is fashionable.
Mailbox role as the modern building block
Modern Exchange Server architecture is intentionally less role-fragmented than Exchange 2003. Mailbox servers contain mailbox databases, transport services and client access services. Client connections are accepted at the front-end services and proxied to the backend service that owns the mailbox operation.
Edge Transport remains a separate optional role for perimeter transport. It is not a mailbox server and is commonly placed in a perimeter network where the organization needs that topology.
On-premises vs cloud is an operating-model decision
Exchange Online removes responsibility for operating the mailbox servers themselves, but the business still controls domains, sender authentication, identities, access policy, retention configuration and application mail integrations. On-premises Exchange gives the organization more infrastructure control but also requires continuous patching, certificate management, storage, high availability and security operations.
Hybrid combines both models and therefore carries both sets of dependencies during coexistence. The simplest long-term architecture is usually the one with the fewest permanent moving parts that still meets business requirements.
A company still runs Exchange 2019
The business has 250 mailboxes, several SMTP devices and a legacy application. Exchange 2019 support has ended.
Decision: Choose Exchange SE, Exchange Online or a hybrid migration based on real dependencies and support requirements rather than simply leaving the old environment in place.
Evidence: Document current applications, SMTP sources, recipient model, supported target and migration/recovery plan.
Hands-on lab
Draw on-premises Exchange SE, Exchange Online and hybrid versions of the same fictional company. Mark who owns DNS, mailboxes, transport, certificates and recovery.
Troubleshooting exercise
- Users cannot send externally: trace transport/connectors and DNS instead of restarting every service.
- Address information is wrong: check recipient directory data.
- Hybrid mail queues: verify connectors, TLS identity and endpoints.
Field checklist
- Current Exchange support state verified.
- Architecture documented.
- AD/DNS dependencies known.
- Cloud vs on-prem responsibility clear.
- SMTP/app dependencies inventoried.
- Target end state documented.
Current technical references
The supplied PDF books are used as a historical curriculum map. Current implementation guidance is checked against current Microsoft documentation.