Back to latest version
You're viewing a historical snapshot from Nov 11, 2024. This is not the latest version.

Metadata at Nov 11, 2024

Last Updated

Nov 11, 2024

Published Nov 8, 2024

Service

Microsoft 365 apps

Tag

Major change
Updated message
New feature
User impact
Admin impact

Platforms

Web

MC929025 - Microsoft Loop – Multi-Geo Support for Shared Loop workspaces

Message Center

What changed since this version

removed textadded text

Updated November 11, 2024:December 1, 2025: We have updated the timeline below to show as intended.below. Thank you for your feedback.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 March 2025November) and expect to complete by mid-January 2026 (previously late April 2025.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.

Snapshot from Nov 11, 2024

Updated November 11, 2024: We have updated the timeline below to show as intended. Thank you for your feedback.

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 late March 2025 and expect to complete by late April 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.