Microsoft 365 Multi-Geo

Multi-Geo Capabilities lets a single Microsoft 365 tenant store user data in multiple geographic regions, per user. It's how multinationals run one tenant for the whole organisation while still keeping French employees' personal data in France, Japanese employees' data in Japan, and so on.

What Multi-Geo covers

Multi-Geo applies to these workloads, with data residency scoped per user:

• Exchange Online mailboxes.
• OneDrive for Business.
• SharePoint sites (Microsoft 365 Group-connected sites follow the owner's geography, with the option to move sites between geographies).
• Microsoft Teams files (because they live in SharePoint sites that obey Multi-Geo).
• Microsoft Teams Phone metadata (more limited).

It does not typically extend to:

• Entra ID — identity data has a separate residency model, generally tied to tenant region.
• Yammer / Viva Engage — tenant-region only.
• Power BI — tenant-region only.
• Defender and Purview — tenant-region only.

The list of Multi-Geo-aware workloads has been expanding, so check current Microsoft documentation for the latest.

How it works

A tenant declares its default geography (e.g., EU) and adds satellite geographies (e.g., APC, AUS, GBR, JPN). Each user is assigned a preferred data location (PDL) that determines where their Exchange mailbox and OneDrive live. The PDL is an attribute (PreferredDataLocation) set on the user object, typically synced from on-prem AD via Entra Connect.

When a user is created or has their PDL changed, Microsoft automatically migrates their mailbox and OneDrive to the right region. The user signs in as normal — they don't see anything different except the URL of their OneDrive includes the region code.

SharePoint sites and Microsoft 365 Groups

Group-connected sites (which includes Teams team sites) follow the owner's PDL at creation. Sites can be moved between geographies later via PowerShell or the SharePoint admin center.

Standalone communication sites and team sites can be created in any geography by an admin.

Search and discovery

Microsoft Search is cross-geo aware: searching from any region returns results from the user's accessible content regardless of where it's stored. The user experience is unified even though the data is distributed.

Cross-geo collaboration

Users in one geography can share with users in another geography just as they share with anyone else in the tenant. There's no barrier — Multi-Geo affects storage location, not collaboration.

When to use Multi-Geo

The two main drivers:

• Regulatory residency — French employee personal data must stay in France under specific labour or data-protection rules. Multi-Geo provides legal residency without splitting the tenant.
• Latency — large geographic dispersion benefits from data being closer to the user. Effect is small in most cases (Microsoft 365 is generally fast everywhere), but can matter for video and large files.

When you don't need it

• All employees in one country / region → tenant-default residency is enough.
• Data sovereignty needs that go beyond storage (telemetry, support, processing) → look at Advanced Data Residency or sovereign clouds.

Licensing

Multi-Geo is sold as a per-user add-on, typically on top of Microsoft 365 E3 / E5. Each user in a non-default geography needs the add-on.

For genuinely multinational tenants, Multi-Geo is a meaningful operational simplifier. For single-region tenants, it's irrelevant.