By default, all inbound email to the Microsoft 365 tenant, regardless of the user’s location, enters Exchange Online in the primary tenant region first, then gets routed internally to the actual recipient.
For organizations dealing with regional data regulations, latency concerns, or strict data-handling policies, that first entry point can raise questions.
Here’s what changes with in-region routing:👇🏻
Admins can now control where inbound mail enters Exchange Online. Instead of everything landing in the primary region first, email enters directly in the same geography as the recipient’s mailbox.
In simple terms:
- User mailbox in Europe → mail enters Exchange in Europe
- User mailbox in Asia → mail enters Exchange in Asia
- No unnecessary cross-region hop
Multi-Geo tenants can now:
☑️Associate accepted domains with specific geo regions
☑️Align those domains with users in the same region
☑️Ensure anonymous and hybrid on-premises mail enters that region directly
This is included in the Microsoft 365 Multi-Geo add-on at no extra cost.
It also raises an interesting question: if Microsoft is moving toward region-aware routing, could this eventually expand beyond Multi-Geo? For now, it’s tightly coupled with Multi-Geo architecture, but worth watching.
For global tenants, that’s a meaningful level of control.