Microsoft Loop cannot sync: fix pages and components

If Microsoft Loop cannot sync, the usual cause is a signed-in account mismatch, an offline or weak connection, an out-of-date app or browser, or a permissions or storage problem in OneDrive or SharePoint. Start by confirming you’re in the right account, that the item is still stored where Loop expects it, and that the same component or page changes in another Microsoft 365 app. If it still doesn’t update, the issue is more likely tenant policy, permissions, or a service outage than something you can fix on your device.

Symptom

Changes in Loop do not appear on another device, for a teammate, or in another Microsoft 365 app

This usually shows up after you edit a Loop page or component and then open it somewhere else, such as the Loop app, Teams, Outlook, Word, or a browser. The exact message varies, and sometimes there is no error at all — the item just stays stale or shows old content.

Before you start

• This applies to Microsoft Loop content used across Microsoft 365, including browser, desktop, and mobile access.
• You do not need administrator rights for the first checks.
• No restart or backup is required for the first steps, but avoid making more edits until you know the current version has synced.
• Safe first checks: confirm the signed-in account, check whether you are online, and open the same item in another Microsoft 365 app before changing anything else.

What to try first, in order

1. Confirm you are signed into the same work or school account everywhere you use the item. If Loop works on one device but not another, account mismatch is the first thing to check. Sign out of the affected app or browser profile, then sign back in with the account that owns or was shared the Loop item. If the item appears after that, the problem was account access, not sync. If it still does not update, move to the next step.
2. Check that the device has a live connection. Use a stable connection and wait a moment for the page to refresh. If you were offline, on a weak connection, or switching networks, Loop may not have written changes back yet. If edits appear after the connection settles, sync was delayed. If nothing changes, the issue is elsewhere.
3. Refresh the app or browser page, then open the item again. Close and reopen the page, the desktop app, or the mobile app. This forces Loop to reload the latest state from Microsoft 365 without changing the content itself. If the page updates, the local view was stale. If it still shows old content, keep going.
4. Check whether the same item updates in another Microsoft 365 app. Open the component where it normally lives, such as Teams, Outlook, or Word, and compare what you see there with the Loop app or browser view. If one app shows the latest version and another does not, the problem is likely in the host app’s cache, rendering, or session state. If the item is stale everywhere, the issue is more likely storage, permissions, or a service-side problem.
5. Update the app or browser you are using. Out-of-date versions can keep an older cached copy or fail to handle Loop updates correctly. Install the latest version of the Microsoft 365 app, and if you are using a browser, update it as well. If updating fixes the issue, the older version was the problem. If not, check storage and permissions next.

How to tell where the problem is

If the item fails in every app and on every device, look first at OneDrive or SharePoint storage, permissions, or a service outage. If it works in one app but not another, the issue is more likely in that specific Microsoft 365 app’s cache or session than in Loop itself.

A simple way to separate the causes is this:

• If the component never updates anywhere, suspect storage, permissions, or tenant policy.
• If it updates in one place but not another, suspect the host app or browser.
• If it fails only for one person, suspect account mismatch, access, or licensing.

For content that was created in one tenant and opened in another, cross-tenant restrictions can also block updates even when the page opens normally.

What an admin should check in the tenant

If you have admin access, check whether Loop is allowed in the tenant and whether the right Microsoft 365 services are enabled for the affected users. Policies can block creation, sharing, or collaboration in ways that look like sync failure to the end user.

Also check whether the underlying OneDrive or SharePoint storage is available and whether the affected users have the needed licenses and permissions. If the item was created in one tenant and opened in another, cross-tenant restrictions can also break the update path.

If users report the same failure across devices and apps, and the item does not update even after sign-out and sign-in, a service-side or policy-side issue is more likely than a browser problem.

Verify it worked

Open the same Loop page or component in at least two places: the browser, the desktop app, or a mobile device. Make one small edit in one place, then refresh or reopen the item in the other place.

Expected result: the new content appears everywhere after a short delay, and teammates with access see the same version. If one device still shows old content while the others update, the sync problem is not fully fixed yet.

If you need to confirm storage is involved, check whether the item’s source location in OneDrive or SharePoint matches the place where the component was created or shared. If that location is unavailable or access is blocked, sync will keep failing until that is fixed.

Conclusion

If Loop still will not sync after these checks, stop changing the item and get the owner or admin to check permissions, tenant policy, or service status. If you want, I can turn this into a shorter checklist for Teams, Outlook, Word, or the Loop app specifically.

Frequently Asked Questions

Why does Microsoft Loop update for me but not for my teammates?

That usually means the item is saved, but your teammates are opening it with a different account, from a stale cache, or without the right permissions. It can also happen if their app version is behind or if the shared file is in a location they can’t fully access.

Can Loop sync offline and update later?

Usually it needs a live connection to write changes back to the shared file. If you were offline or on a weak connection, some edits may not upload right away and can look missing until the connection recovers.

How do I know if the problem is Loop or SharePoint/OneDrive?

If the same page fails everywhere, the storage or permissions are a better suspect than the app. If it works in one Microsoft 365 app but not another, the problem is more likely in the host app’s cache or rendering.