Microsoft Loop not updating: why changes aren’t syncing

Microsoft Loop usually isn’t broken when updates don’t appear right away. Most of the time, you’re seeing normal sync delay, the wrong account or tenant, or a stale tab, app, or browser session. Start with refresh, reopen, and an account check; if the change still doesn’t show up in another surface, move on to cache, app updates, and service status.

What “not updating” usually means in Loop

Most people notice this in one of a few ways: a change they just made does not appear in another browser tab, the same page looks stale on another device, or a Loop component embedded in Teams or Outlook still shows old text after someone edited it.

Sometimes one person sees the latest version and another person sees an older one. That does not always mean the edit failed. Loop content can take a short time to catch up across surfaces, especially if you just switched apps or the other window has been open for a while.

A good first clue is scope. If one component is stale but other Loop content updates normally, the issue is probably limited to that page, that embed, or that collaborator’s session. If nothing updates anywhere, the cause is more likely account-related, connection-related, or tied to a Microsoft 365 service issue.

Before you start

This applies to Microsoft Loop in the web app, Microsoft 365 surfaces such as Teams and Outlook, and the desktop app where Loop content is available.

You do not need Administrator or sudo rights for the first checks in this guide. You may need admin help later if the problem turns out to be tenant-wide, permission-related, or tied to Microsoft 365 service health.

You do not need to restart your device to begin, and you should not clear all browser data or reinstall anything as a first step. The safest checks are to refresh the page, reopen the app, and confirm you are signed into the right Microsoft account and tenant.

Symptom

Changes in Microsoft Loop do not appear in another tab, on another device, or in Teams or Outlook.

This usually shows up right after someone edits a Loop page or component, then opens the same content somewhere else and sees the old version. It can also appear when one collaborator sees the update and another collaborator does not.

When this is a Loop problem and when it’s just sync delay

A short wait is normal when you’ve just edited a page or component. If the change shows up after a minute or two, you were probably just seeing sync delay.

It starts to look like a real problem when the content stays stale after you refresh the page, reopen the app, or check from another device. It also points to a real issue if the edit is visible in one place but not in another place signed in to the same account.

The wrong account is a common cause. Say you’re signed into a personal Microsoft account in the browser, but the Loop page belongs to your work tenant. In that case, you may be looking at the wrong version entirely, or you may not have access to the same content.

Another clue is whether the same page behaves differently across surfaces. If the page updates in the web version but not in the desktop app, the problem is probably local to the app or its cache, not the Loop service itself.

The fastest fixes to try first

Start with the least risky checks first. You do not need admin rights for these steps.

1. Refresh the page or reopen the component.

The latest edits appear after a refresh, or the page reloads from the current version.

If the content updates, the issue was just a temporary display or sync delay. If it does not, move on.

2. Close and reopen Loop, Teams, or Outlook, depending on where you were editing.

The app reconnects and pulls the current version of the page or component.

If the same stale content returns, the session may be stuck.

3. Confirm you are signed into the right Microsoft account and tenant.

- Work account versus personal account
- The correct organization or tenant
- The same account on both devices

If you were in the wrong account, switch to the account that owns or has access to the Loop content.

4. Check your internet connection.

- Can you open other Microsoft 365 pages?
- Does the page update on a different network?
- Are you on a captive portal, VPN, or unstable Wi-Fi?

If other sites work but Loop does not, the issue is still not necessarily Loop itself, but the connection is still worth ruling out.

5. Try the web version if you are using the desktop app, or try the app if you are in the browser.

The same page should show the same latest content across surfaces.

If one surface updates and the other does not, the problem is local to the surface that is stale.

If it still won’t update, check the cache, app version, and Microsoft 365 status

If the basic checks do not fix it, the next safest step is to clear the browser cache for the site or update the app. You do not need to wipe everything; start with the browser or app you are actually using.

For a browser, clear cached files and cookies for the Loop or Microsoft 365 site, then sign in again. The exact menu differs by browser, but the goal is the same: remove stale session data that can keep showing an old copy of the page.

Browser settings > Privacy / Site data / Clear browsing data > Cached images and files

If you use the desktop app, install the latest update and reopen it. An outdated app can lag behind changes or hold on to an old session.

App settings > About or Help > Check for updates

Also check Microsoft 365 service status if the problem affects multiple people or multiple devices. If a Loop component updates in one tab but not another, and the same behavior shows up for coworkers, that points away from your device and toward a service issue or tenant-side problem. If status pages or your admin reports an incident, waiting may be the only practical fix until Microsoft resolves it.

If only one page, one component, or one collaborator is not updating, the problem is usually narrower than a full Loop outage. In that case, compare the stale view with the current one in another tab, another browser, or the web version. If the same page is fine everywhere except one embed, the issue is probably local to that embed or session. If one collaborator alone cannot see the update, the problem is more likely on their side than yours.

How to verify the fix worked

A fix has worked when the same page or component shows the same current content in more than one place. The cleanest test is to edit a short piece of text in one location, then open the same Loop page or component in another tab, another device, or another Microsoft 365 surface.

The edit appears in the second view without manual re-entry.

If it shows up everywhere, syncing is working again. If one page still lags behind while the rest update correctly, the problem is likely limited to that page, that embed, or that collaborator’s session.

If only one collaborator does not see the latest version, ask them to sign out and back in, confirm they are using the same account, and open the content in the web version. That helps separate a local session issue from a shared content issue.

When to hand it off to your admin or support

Escalate when the problem looks bigger than a single bad refresh. That includes permission errors, tenant restrictions, repeated sign-in failures, or cases where only people in one organization cannot see updates.

You should also hand it off if:

• The same Loop page fails for several users across different devices
• The issue only happens inside a managed work tenant
• You suspect a permissions change removed access to the page or component
• Microsoft 365 status shows an incident and the problem matches it
• The page works for some collaborators but not for others with the same intended access

An admin can check tenant settings, license assignment, access policies, and service health that you cannot see from your side. If the issue is tied to a company policy or outage, there usually is not a local fix you can apply yourself.

Conclusion

If Loop still will not update after the basic checks, focus on scope: one page, one app, one account, or one tenant. That tells you whether to keep working locally or hand it to your admin. If you want the fastest next move, test the same content in the web version while signed into the correct work account.

Frequently Asked Questions

Why does Microsoft Loop update in one tab but not another?

That usually means one tab has stale session data or cache. Refresh both tabs first, then sign out and back in, or clear site data for the browser if the stale view keeps coming back.

How long should I wait before assuming Loop is stuck?

A short delay is normal right after an edit. If the change still does not appear after a refresh or reopen, treat it as a sync problem rather than normal delay.

Can the wrong Microsoft account make Loop look broken?

Yes. If you are signed into a different work or personal account, you may be looking at a different tenant or a page you cannot fully access. Always confirm the account before you troubleshoot anything else.

What if only one collaborator cannot see the update?

That usually points to a local sign-in, permission, or cache issue on that person’s side. Have them refresh, check the account, and try the web version before escalating.