Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Microsoft Teams now included in Microsoft 365 Multi-Geo!

Published Jul 13 2021 08:00 AM 23.5K Views

With Microsoft 365 Multi-Geo, organizations have greater control over the location of specific data centers their data is stored in. Admins can provision and store data at rest in the geo locations of their choice to help meet data residency requirements, especially helpful for multi-national organizations. Microsoft 365 Multi-Geo includes support for Exchange Online, SharePoint Online and OneDrive…and now Teams!

In a Multi-Geo environment, an organization’s Microsoft 365 tenant consists of a central location and one or more satellite locations. The tenant’s central location is based on where the Microsoft 365 subscription was originally provisioned and satellite locations are the additional geo locations specified by admins. To store an end user’s data in a specific geo location separate from the tenant’s central location, an admin will set the end user’s Preferred Data Location (PDL) Azure Active Directory attribute.

Figure 1: Microsoft 365 Multi-GeoFigure 1: Microsoft 365 Multi-Geo


Microsoft Teams Multi-Geo Support now Generally Available!

Teams Multi-Geo enables customers to store Teams core customer data at rest for end users and teams in the geo locations of their choice, controlled through the same PDL leveraged by existing Microsoft 365 Multi-Geo services. This will allow admins to control where Teams customer data will sit down to the team and end user level.

Teams data ownership principles

Teams Multi-Geo handles data ownership different for end users and teams based on who the designated “owner” of the data is.

  • End user chat data: in a 1:1 or 1:N chat, the creator of the chat is the data “owner” and the PDL of that end user will determine where the chat data sits
  • Meeting chat data: the organizer of the meeting is the data “owner” and the PDL of the organizer will determine where the meeting chat data sits
  • Team and channel data: the team is the data “owner” and is backed by a Microsoft 365 group, meaning the Microsoft 365 group’s PDL will determine where the data sits

An important piece in data ownership is that if an end user or Microsoft 365 group’s PDL is changed, the associated data “owned” will be migrated to the newly set PDL. If an end user has Multi-Geo disabled or their license removed, their chat data will eventually migrate back to the tenant default. If the tenant has Multi-Geo disabled, all Teams core customer data will eventually migrate back to the tenant default geo location.

Frequently Asked Questions:

How will this impact my organization if we are already using Microsoft 365 Multi-Geo?

For customers who have setup and enabled Microsoft 365 Multi-Geo capabilities by setting a PDL for an end user or Microsoft 365 Group, Microsoft 365 Multi-Geo will begin migrating Teams core customer data and respecting PDLs as we work through the queue. This queue will process continuously over the next few quarters and is fully automated. No action is required by IT administrators. Any new PDL changes will be processed after the tenant has completed the initial sync, and new PDL changes beyond that will be queued and processed in the order they are received. Microsoft 365 Multi-Geo is not enabled by default - if you have not setup and enabled any Multi-Geo capabilities there will be no impact for your organization.

How do we prepare to take advantage of Microsoft 365 Multi-Geo?

The first step of Microsoft 365 Multi-Geo is to ensure that each user who will have a PDL set separate from the central tenant location has a proper Multi-Geo license assigned. If an end user has a PDL set but is not assigned a proper license, their data will not move and remain in the tenant default geo location. If a user has their Microsoft 365 Multi-Geo license removed, their data will migrate back to the tenant default geo location.

What are the licensing requirements for Microsoft 365 Multi-Geo?

Microsoft 365 Multi-Geo licensing is available as an add-on to the below Microsoft 365 subscription plans for Enterprise Agreement customers. For more information, please contact your Microsoft account team.

  • Microsoft 365 F1, F3, E3, or E5
  • Office 365 F3, E1, E3, or E5
  • Exchange Online Plan 1 or Plan 2
  • OneDrive for Business Plan 1 or Plan 2
  • SharePoint Online Plan 1 or Plan 2

Does Microsoft 365 Multi-Geo impact our security and compliance capabilities?

All existing information protection and compliance capabilities will continue working as is with Microsoft 365 Multi-Geo.

Can Microsoft 365 Multi-Geo help improve network performance?

No, Microsoft 365 Multi-Geo is designed to support data residency requirements and is not designed for performance optimization. For more information about performance optimization for Microsoft 365, please reference Network planning and performance tuning for Microsoft 365.

Where can I go to learn more?

For detailed information on Microsoft 365 Multi-Geo and Teams Multi-Geo, please see:

Occasional Contributor


Hi @John Gruszczyk,
thank you for sharing this. It's great that Teams is now included in the Multi-Geo Config.

I have a few questions about the data owner: You wrote:

  • Team and channel data: the team is the data “owner” and is backed by a Microsoft 365 group, meaning the Microsoft 365 group’s PDL will determine where the data sits

How is the M365 Group PDL determined. Is it defined by the location of the Team Owners?
If yes: If there are multiple Team Owners (which should be the case everytime), which one is used to determine the PDL?

Thank you


@jakobschaefer Hi Jakob, thanks for the kind words and question. A Microsoft 365 Group PDL can be set or is determined by the Microsoft 365 Group creator - Create a Microsoft 365 Group with a specific preferred data location - Microsoft 365 Enterprise | Mi...

Why is Multi-Geo only for Enterprise Agreement customers?
As a CSP Indirect Provider we have a number of customers who need this.
New Guidelines set CSP as the program for customers up to 2400 seats, many of these will need Multi-Geo.

Frequent Visitor

Are there also plans to offer multi-geo support for Dataverse for Teams (or offer some other way to control the data location)?
Would be nice if Dataverse environments for Teams could also be provisioned in a region based on the group PDL as opposed to always using the tenant home location.
For many (at least in my company), is a requirement as a matter of fact.


What about the associated SharePoint data? If the PDL of the M365 group changes, will the site be migrated to the new GEO? 

Occasional Visitor

Hi John,


If the MS Teams meeting organizer is with PDL = CAN, whether the video/audio data will be stored after the meeting end as well as the chat history?



Occasional Contributor

Multi-Geo need to be available for customers using CSP instead of being limited to EA customers. 
Any statement on this topic?


Version history
Last update:
‎Sep 07 2021 03:46 PM
Updated by: