Multi-Geo is one of the compliance features that were already introduced two years ago at Ignite and allows emails and also files to be stored in the respective region, but everything is managed in just one tenant. This option is accordingly aimed at the multi-national companies.
Multi Geo for Microsoft Teams
Now it has gone to GA status after a long period of preview. This means that Microsoft Teams can now be run in different regions and managed from just one tenant.
You need the following one for your Multi-Geo enviroment:
- 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
Teams data ownership principles
Teams Multi-Geo treats data ownership differently for end users and teams, depending on who is the designated “owner” of the data.
End-user chat data: In a 1:1 or 1:N chat, the creator of the chat is the “owner” of the data, and that end user’s PDL determines where the chat data is stored
Meeting chat data: The meeting organizer is the “owner” of the data, and the organizer’s PDL determines where the meeting chat data is stored.
Team and channel data: The team is the “owner” of the data and is supported by a Microsoft 365 group, which means that the PDL of the Microsoft 365 group determines where the data is stored
An important point about data ownership is that when an end user’s or Microsoft 365 group’s PDL is changed, the associated data that is “owned” is migrated to the newly defined PDL. If an end user has Multi-Geo disabled or their license removed, their chat data will eventually be migrated back to the tenant default. If the tenant has Multi-Geo disabled, all of the team’s core customer data will eventually be migrated back to the tenant’s Geo default location.