Microsoft Loop – Multi-Geo Support for Shared Loop workspaces
Microsoft Loop is set to introduce Multi-Geo support for shared workspaces starting from late March 2024, with data storage located in the expected geo. This means that 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. There is nothing you need to do to prepare for these changes as they will occur automatically for multi-geo tenants. This rollout is associated with Microsoft 365 Roadmap ID 421616 and is expected to complete by late April 2024.
This update, which will be available worldwide in its General Availability phase, will not affect M365 group-owned workspaces which are created in the group's geo. However, non-M365 group-owned workspaces will be created in the creator's preferred data location. To prepare for this change, it is important to understand that crafting M365 Loop workspaces demand a thorough grasp of these upcoming changes to optimize the experience of your users. Bear in mind that this message is associated with Microsoft 365 Roadmap ID 422728.
Stay informed and ahead of the curve by keeping up with the latest trends and updates on the Microsoft 365 ecosystem.
The post Microsoft Loop – Multi-Geo Support for Shared Loop workspaces appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Loop – Multi-Geo Support for Shared Loop workspaces
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Microsoft 365 app: Microsoft Loop – Multi-geo support for shared Loop workspaces
Microsoft 365 has released a new app called Microsoft Loop that now supports multi-geo for shared Loop workspaces, effectively ensuring that d...
Microsoft 365: Multi-Geo In-Region Routing
Microsoft 365's Multi-Geo In-Region Routing feature enables customers with regional data compliance requirements to control the routing of inb...
Configuration Change: Search-MailboxAuditLog cmdlet, multi-geo scenarios
If you're utilizing the Search-MailboxAuditLog cmdlet in a multi-geo Exchange environment, you might encounter an error message when attemptin...
Feature release for Multi-geo admin audit
A new feature has been released for Exchange Online Multi-geo environments that allows admins to audit admin operations across all locations u...
Microsoft Syntex is available in the non-primary region of multi-geo tenants
Microsoft has made its Syntex capabilities available in the non-primary region of multi-geo tenants with its latest release, allowing users to...
Syntex is available in non-primary region of multi-geo tenants
Good news for multi-geo tenants using Syntex capabilities, as Microsoft has released a new update that enables Syntex capabilities such as doc...
Exchange: Microsoft multi-geo admin operation auditing
In March of 2023, Exchange Online Multi-Geo will launch a new feature that enables administrators to audit operations across all locations usi...
Multi-Geo reduced seat minimum and expanded geo coverage
We are excited to announce the availability of Microsoft 365 Multi-Geo in Switzerland, and the reduction of the seat minimum requirement to 25...
Viva Engage now supports cross geo B2B Guest access!
Viva Engage just made a significant update by announcing cross-geo B2B guest access support, which will be launched soon. The update will enab...
Microsoft Teams: Geo filtering for Teams apps
Microsoft Teams is introducing a new feature that allows ISVs to target applications to specific geographies. This means that users will only ...