Updated December 1, 2025: We have updated the timeline below. Thank you for your patience.
Data storage for shared Loop workspaces will be located in the expected geo for multi-geo tenants.
This message is associated with Microsoft 365 Roadmap ID 421616
[When this will happen:]
General Availability (Worldwide): We will begin rolling out mid-December 2025 (previously late November) and expect to complete by mid-January 2026 (previously late December 2025).
[How this will affect your organization:]
If your organization uses multi-geo configuration, data storage for shared Loop workspaces in SharePoint Embedded will be located in the expected geo for multi-geo tenants:
- M365 group-owned workspaces are created in the group’s geo (delivery of M365 group-owned workspaces is associated with Microsoft 365 Roadmap ID 422728)
- non-M365 group-owned workspaces are created in the creator’s preferred data location.
[What you need to do to prepare:]
There is nothing you need to do to prepare. These changes will roll to your multi-geo configured tenants automatically.
Source: Microsoft
<<< [MC929025] Archive
Tooltip: View earlier revisions of this post
Latest Posts
- (Updated) Microsoft Loop – Multi-Geo Support for Shared Loop workspaces [MC929025]
- Build agents to automate production UI workflows with Amazon Nova Act (GA)

- Amazon Nova Forge: Build your own Frontier Models using Nova

- Amazon EC2 P6e-GB300 UltraServers accelerated by NVIDIA GB300 NVL72 are now generally available



