Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 18:49 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Loop – Multi-Geo Support for Shared Loop workspaces

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
421616

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 2 Dec 2025 late November 2025, late December 2025 → mid-December 2025, mid-January 2026
  • Seen 4 Apr 2025 late March 2025, late April 2025 → late November 2025, late December 2025
  • Seen 11 Nov 2024 late March 2025, late April 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

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.

What changed

Between archive captures, newest first
  1. Updated April 4,December 1, 2025: We have updated the rollout timeline below. Thank you for your patience. Data storage for shared Loop … When this will happen: General Availability (Worldwide): We will begin rolling out late November mid-December 2025 (previously late March)November) and expect to complete by late December 2025 mid-January 2026 (previously late April).December 2025). How this will affect your organization: If your organization uses multi-geo configuration, …

  2. Updated November 11, 2024:April 4, 2025: We have updated the rollout 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 … this will happen: General Availability (Worldwide): We will begin rolling out late MarchNovember 2025 (previously late March) and expect to complete by late April 2025.December 2025 (previously late April). How this will affect your organization: If your organization uses multi-geo configuration, …

    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    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 … this will happen: General Availability (Worldwide): We will begin rolling out late Mar 2024March 2025 and expect to complete by late Apr 2024.April 2025. How this will affect your organization: If your organization uses multi-geo configuration, …

  3. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 18:49 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current