You are working on a Copilot Page that contains a Loop component, but changes made by collaborators do not appear in real time. The component appears stuck, showing an outdated version or a spinning sync indicator. This failure usually occurs because the Loop component relies on a specific Microsoft Graph connection that can be blocked by network policies, browser settings, or outdated Microsoft 365 licenses. This article explains why the sync breaks and provides a step-by-step fix to restore real-time collaboration.
Key Takeaways: Fixing Loop Component Sync in Copilot Pages
- Microsoft 365 admin center > Org settings > Loop: Controls whether Loop components are enabled for your tenant. Disabling this breaks all Loop sync.
- Browser settings > Cookies and site data: Blocking third-party cookies prevents the Loop component from authenticating with the Microsoft Graph sync service.
- Windows Firewall or proxy > Allowlist for loop.microsoft.com: Network filtering can block the WebSocket connection required for real-time sync.
Why the Loop Component in Copilot Pages Loses Sync
A Loop component inside a Copilot Page is not a static embed. It maintains a persistent WebSocket connection to the Microsoft Graph sync service. This connection transmits each keystroke and edit to all active collaborators. When the connection drops, the component falls back to a local-only edit mode. The user sees their own changes but not those from others.
The root cause is almost always one of three things. First, the organization has disabled Loop components in the Microsoft 365 admin center. Second, the browser blocks third-party cookies or WebSocket connections. Third, a network firewall or proxy server intercepts the WebSocket traffic to loop.microsoft.com. Less common causes include an expired Microsoft 365 license that lacks the Loop service plan or a browser extension that modifies page scripts.
The Role of the Microsoft Graph Sync Service
Loop components use the Fluid Framework, which relies on the Microsoft Graph sync service to broadcast edits. The service requires an active authenticated session. If the authentication token expires or is revoked, the sync stops. The component does not display an error message. It simply stops updating. The user must refresh the page or re-authenticate to restore the token.
Steps to Re-enable Loop Component Sync in Copilot Pages
Follow these steps in order. Test the sync after each step by making an edit in the Loop component and asking a collaborator to confirm the change appears within 10 seconds.
- Verify Loop is enabled in the Microsoft 365 admin center
Go to Microsoft 365 admin center > Org settings > Loop. Ensure the toggle for Allow Loop components in Microsoft 365 is set to On. If it is Off, turn it On and click Save. Wait 5 minutes for the change to propagate before testing. - Allow third-party cookies in your browser
In Microsoft Edge, go to Settings > Cookies and site permissions > Manage and delete cookies and site data. Set Block third-party cookies to Off or add loop.microsoft.com to the Allow list. In Google Chrome, go to Settings > Privacy and security > Third-party cookies and select Allow third-party cookies or add loop.microsoft.com to the Sites that can always use cookies list. Reload the Copilot Page. - Clear the browser cache for Copilot Pages
Open the browser Developer Tools with F12. Click the Application tab. Under Storage, select Clear site data for the domain copilot.microsoft.com. This removes stale tokens and cached scripts. Reload the page and sign in again. - Check network firewall or proxy rules
Ask your IT administrator to verify that the domain loop.microsoft.com and all subdomains are not blocked by the corporate firewall or proxy. The sync service uses WebSocket endpoints at wss://loop.microsoft.com. If the firewall blocks WebSocket traffic, the component cannot sync. The administrator can create an allow rule for the entire loop.microsoft.com domain. - Disable browser extensions temporarily
Extensions that modify page content, such as ad blockers, script blockers, or privacy tools, can break the Loop component script. Open the browser extension manager. Disable all extensions. Reload the Copilot Page. If sync works, re-enable extensions one by one to identify the conflicting one. - Re-authenticate your Microsoft 365 account
Sign out of all Microsoft 365 services in the browser. Go to copilot.microsoft.com and sign in again. This refreshes the authentication token used by the Loop component. Test the sync immediately after sign-in.
If Copilot Pages Loop Sync Still Fails
After completing the main steps, some users still encounter sync failures. The following issues are less common but have specific fixes.
Loop Component Shows Read-Only Mode
If the Loop component appears grayed out and you cannot type, the document may have been shared with view-only permissions. Ask the owner to change the sharing link to Can edit. In the Copilot Page, click Share and set the permission level to Edit for all collaborators.
Changes Sync Only After Manual Refresh
This indicates that the WebSocket connection failed but the component can still sync via HTTP polling. The fix is to ensure that your network allows WebSocket traffic. In a corporate environment, the IT team must enable WebSocket passthrough on the proxy server. On a home network, reset the router or temporarily disable any VPN that might interfere with WebSocket connections.
Loop Component Missing from the Insert Menu
If the Loop component option does not appear when you try to insert it, the feature is disabled for your tenant or your license. Verify that your Microsoft 365 license includes the Loop service plan. Go to Microsoft 365 admin center > Users > Active users, select your account, and check the Licenses and apps tab. Ensure Loop is enabled. If it is not, contact your administrator to assign a license that includes Loop.
Copilot Pages Loop Sync vs Standard Loop Components
| Item | Copilot Pages Loop Component | Standard Loop Component in Teams or Outlook |
|---|---|---|
| Host environment | Embedded inside a Copilot Page at copilot.microsoft.com | Embedded in Teams chat, Outlook email, or Word Online |
| Sync method | WebSocket to Microsoft Graph sync service | WebSocket to Microsoft Graph sync service |
| Authentication | Uses the Copilot Pages session token | Uses the host app authentication token |
| Third-party cookie requirement | Required for sync | Required for sync |
| Firewall domain to allow | loop.microsoft.com and all subdomains | loop.microsoft.com and all subdomains |
| Common failure cause | Browser cookie blocking or proxy WebSocket filter | Tenant policy disabling Loop or expired token |
You can now fix a Loop component sync failure in Copilot Pages by checking the tenant policy, browser cookie settings, and network firewall rules. Start with the admin center toggle, then move to browser and network settings. If the problem persists, verify the sharing permissions and the WebSocket connectivity. For ongoing collaboration, keep the browser Developer Tools console open to watch for WebSocket connection errors. A successful connection shows a status of 101 Switching Protocols.