MC929025 High Major change

(Updated) Microsoft Loop – Multi-Geo Support for Shared Loop workspaces

  • Admin

Summary AI-generated

Data storage for shared Loop workspaces in multi-geo tenants will be located in the expected geo, rolling out mid-Dec 2025 to mid-Jan 2026; no admin action needed.

Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.

Original post from Microsoft

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.

Additional details from Microsoft

RoadmapIds
421616
Summary
Microsoft Loop's multi-geo support for shared workspaces will roll out mid-December 2025 to mid-January 2026. Data storage aligns with tenant geos: M365 group-owned workspaces store data in the group's geo; non-group-owned in the creator's preferred location. No preparation is needed from organizations.
Platforms
Web