Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
At a glance
| Requirement | Details |
|---|---|
| Loop components license | OneDrive or SharePoint license |
| Loop workspaces license | Loop with workspaces service plan (see eligible licenses) |
| Network | Allow connections per Office 365 URLs and IP address ranges |
| Real-time collaboration | Allow WebSocket traffic to *.svc.ms and *.office.com |
| Full features | Exchange Online mailbox required for @mentions and workspace sharing |
Overview
Loop components create .loop files (earlier releases created .fluid files), stored in OneDrive, SharePoint, or SharePoint Embedded. Storage counts against your organization's SharePoint quota. For details, see storage. To control creation, see admin policies.
Network requirements
URLs and IP address ranges
Verify that required network connections are allowed. Loop relies on core Microsoft 365 and SharePoint infrastructure. Configure your firewall or proxy settings according to Office 365 URLs and IP address ranges.
WebSocket connections
Allow WebSocket traffic to *.svc.ms and *.office.com endpoints. WebSocket connections enable real-time collaboration features including live editing, presence indicators, and shared cursors.
License requirements
Loop components
Users need a OneDrive or SharePoint license.
Loop workspaces
Users need a license that includes the Loop with workspaces service plan. This covers creating new workspaces and managing workspace members. See Loop access via Microsoft 365 subscriptions for eligible licenses.
Exchange Online requirement
For full functionality including @mentions and workspace sharing, users need an Exchange Online mailbox. Users with Exchange On-Premises mailboxes have limited capabilities.
Relationship to Copilot Pages and Copilot Notebooks
Loop My workspace, Copilot Pages, and Copilot Notebooks use the same user-owned SharePoint Embedded container. These are separate user experiences and separate admin settings, but they share one physical personal container per user.
The single user-owned container is created when a user first needs one of these experiences and at least one of the relevant creation policies allows it. If Create Loop workspaces in Loop is disabled but Create and view Copilot Pages and Copilot Notebooks is enabled, creating a Copilot Page or Notebook can still create the container. If Create and view Copilot Pages and Copilot Notebooks is disabled but Create Loop workspaces in Loop is enabled, opening Loop My workspace can still create that same container.
To prevent the single user-owned container from being created, disable both policies for the same user.