Category
planForChange
Severity
normal
Major change
True
Last modified
2025-12-02 17:32:28
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
—
Action by (AI)
—
Services
Microsoft 365 apps
Tags
Updated message, New feature, User impact, Admin impact
Master tags
—
Roadmap IDs
421616
One-line summary
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.
Similar updates
More like thisMC929022 (Updated) Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces
(Updated) Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces Admins can require new Loop workspaces to be managed by existing Microsoft 365 Groups, with rollout starting early March 2026 and completing by late March 2026. Updated December 3, 2025: We have updated the timeline. Thank you for your patience. Admins will be.
MC1113112 (Updated) Microsoft Exchange Online | Releasing Multi-Geo In-Region Routing
(Updated) Microsoft Exchange Online | Releasing Multi-Geo In-Region Routing Multi-Geo In-Region Routing lets admins control inbound email routing by geo-region for accepted domains; feature rolls out from October to December 2025 and requires Multi-Geo licenses. Updated October 30, 2025: We have updated the timeline. This message is associated.
MC1173930 Microsoft SharePoint and OneDrive: General availability of tenant rename with no scale limitations
Microsoft SharePoint and OneDrive: General availability of tenant rename with no scale limitations SharePoint Online Tenant Rename is now generally available for all customers, removing site count limits; rollout completes by mid-October 2025. Organizations undergoing rebranding, mergers, acquisitions, divestitures, or tenant consolidations often.
MC929014 (Updated) Microsoft Loop – Departed User Content Workflows for User-Owned Loop workspaces
(Updated) Microsoft Loop – Departed User Content Workflows for User-Owned Loop workspaces Admins can manage retention and deletion workflows for user-owned Loop workspaces like Copilot Pages when users leave; rollout starts early January 2026. This message is associated with Microsoft 365 Roadmap ID 421612 [When this will happen:] General.
MC929020 (Updated) Microsoft Loop – Admin Usage Reports
(Updated) Microsoft Loop – Admin Usage Reports The rollout of Loop usage monitoring in Microsoft 365 admin dashboards is delayed; a new release date will be announced in a future Message Center post. Updated August 20, 2025: After further review, this has been delayed. A new Message Center post will be p... We apologize for any inconvenience..
MC1198079 Migrate User Data Across Tenants: Mailboxes, OneDrives, and Teams Chats
Migrate User Data Across Tenants: Mailboxes, OneDrives, and Teams Chats A unified interface for cross-tenant migrations of Exchange, OneDrive, and Teams data will enter public preview in early December 2025, streamlining admin workflows. [Introduction] To simplify cross-tenant migrations, we're introducing a unified interface that enables.
Details
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
Body (from Message Center)
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.
Raw JSON (for debugging)
Expand/collapse the full payload below.
Show/hide raw
{
"snapshot_item": {
"action_required_by": null,
"ai_action_required_by": null,
"ai_actions": [],
"ai_master_tags": [],
"ai_model": "gpt-4.1",
"ai_summary": "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.",
"ai_topics": [
"Microsoft 365 Apps",
"Loop",
"SharePoint"
],
"category": "planForChange",
"details_map": {
"Platforms": "Web",
"RoadmapIds": "421616",
"Summary": "Microsoft Loop\u0027s 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\u0027s geo; non-group-owned in the creator\u0027s preferred location. No preparation is needed from organizations."
},
"id": "MC929025",
"importance": 5,
"is_major_change": true,
"last_modified": "2025-12-02T17:32:28Z",
"ms_products": [
"Microsoft 365 Apps"
],
"platforms": "Web",
"roadmap_ids": [
"421616"
],
"services": [
"Microsoft 365 apps"
],
"severity": "normal",
"tags": [
"Updated message",
"New feature",
"User impact",
"Admin impact"
],
"title": "(Updated) Microsoft Loop \u2013 Multi-Geo Support for Shared Loop workspaces"
}
}