Loop component links will now open on Loop.microsoft.com

Loop component links that currently open in an editor on Office.com will now open on Loop.microsoft.com. Users will have access to the same functionality as is available on Office.com. Users who have access to Loop workspace will also be able to leverage these capabilities on Loop.microsoft.com.

[When this will happen:]

Targeted Release: We will begin rolling out early September 2023 and expected to complete by mid-September 2023.

Standard Release: We will begin rolling out late September 2023 and expect to complete by early October 2023.

[How this will affect your organization:]

With this change all links to .loop files will open on loop.microsoft.com. The resulting experience on loop.microsoft.com will depend on what the IT admin has enabled for that user. 

If the user has access to create Loop workspaces and the content created in Loop workspaces, which are backed by Syntex repository services, the user will have access to the full Microsoft Loop app experience. To learn more about how to enable and disable Loop workspace creation please refer to: Manage Loop workspace experiences in Syntex repository services.

If the user does not have access to Loop workspaces but does have access to create Loop components across M365, these users will only have access to view and edit .loop files created in M365 applications. To learn more about how to enable and disable Loop components experiences across M365 please refer to: Manage Loop components in OneDrive and SharePoint.

[What you need to do to prepare:]

With this change, there are no new changes to the admin settings for Loop experiences. Any existing Cloud Policy will apply. If you wish to update or review your organization’s setting, please do refer to the following articles: 

Manage Loop workspace experiences in Syntex repository services.

Manage Loop components in OneDrive and SharePoint

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *