Microsoft Loop connection problem: get pages syncing again

If Microsoft Loop won’t load, keeps spinning, or won’t sync changes, the most common causes are a Microsoft 365 service issue, a sign-in problem, cached browser or app data, or something on your device or network blocking it. The fastest safe fixes are to check service status, refresh Loop, sign out and back in, and then test without extensions or VPN. If Loop works on one device but not another, the problem is usually local to the failing device, browser, app, or network rather than Loop itself.

What the connection problem looks like in Loop

Loop connection problems usually show up in a few familiar ways.

The page never finishes loading, a workspace opens to a blank screen, changes stay stuck on “syncing,” or you see a message saying something went wrong and to try again.

Sometimes only comments, components, or recent edits fail to appear, while older content still opens. You may also notice that Loop works for a while, then stops saving changes, or that someone else can see your edits but you can’t see theirs.

If the problem starts right after a browser update, a password change, a VPN connection, or a company sign-in prompt, that usually points to a local setup issue instead of a problem with the Loop service itself.

Before you start

This article applies to Microsoft Loop in work or school accounts, including the Loop web app, desktop app, and mobile app.

You usually do not need administrator rights for the first checks. Some later checks, such as service health, tenant permissions, or network policy changes, may need help from your Microsoft 365 admin.

You do not need to restart anything yet, and you should not clear every account or reset the app before trying the low-risk checks below.

Safe checks to do first:

• Try Loop in a private or incognito window.
• Check whether the problem happens on more than one device or browser.
• Confirm you can still sign in to Microsoft 365 with the same work or school account.

When this is a Loop problem and when it’s your setup

Before you change a lot of things, sort the problem into one of three buckets: Microsoft Loop itself, your account, or your device and network. If Loop is failing for many people in your organization at the same time, or across different devices and browsers, the problem is more likely with Microsoft 365 service health or your tenant settings. If only you are affected, the browser, app, cache, sign-in state, or network is the likelier cause.

A quick way to separate the causes:

• If Loop fails in every browser and on every device, think service or account first.
• If Loop works in a private or incognito window, think cache or extensions.
• If Loop works off the company network but not on it, think VPN, proxy, or firewall rules.
• If one workspace fails but others open normally, think permissions or a workspace-specific issue.

If you can’t tell where the break is, start with the service check and the sign-out/sign-in test. Those are the two quickest ways to rule out a problem outside your device.

The fastest fixes to try first

Start with the least disruptive checks. They solve a lot of Loop connection problems and are easy to reverse.

1. Check Microsoft 365 service health.

Open the Microsoft 365 service health page your organization uses, or ask your admin to check it. If there’s an outage or advisory affecting Loop, SharePoint, or sign-in, wait for Microsoft to fix it.

No active incident affecting Loop, or a note that the issue is already being worked on.

If there is an incident, the problem is not on your side. If service health looks fine, move on.

2. Refresh Loop and open it again.

Close the Loop tab or app fully, then reopen the same page or workspace. A hard refresh in the browser can also help.

The page reloads and the workspace opens normally.

If the same screen keeps loading forever, the cached session may be stuck.

3. Sign out of Microsoft 365 and sign back in.

Use the account menu in Loop or the Microsoft 365 web session, sign out completely, then sign back in with the same work or school account.

Loop or Microsoft 365 account menu > Sign out

You return to Loop with a fresh login and the workspace loads.

If sign-in loops, errors, or asks for credentials repeatedly, the issue may be tied to your account token, multi-factor sign-in, or conditional access rules.

4. Test in a private or incognito window.

Open Loop there and try the same page.

Browser menu > New InPrivate window / New Incognito window

Loop opens without using the usual cached site data or extensions.

If it works there, your normal browser profile is probably the problem.

5. Disable extensions and try again.

Turn off ad blockers, privacy tools, script blockers, password managers with site controls, and security extensions one by one, then reload Loop.

Browser menu > Extensions > Manage extensions

Loop loads after the interfering extension is disabled.

If disabling one extension fixes it, keep that extension off for Loop or add Microsoft 365 sites to its allow list.

6. Test without VPN or proxy.

Disconnect from VPN, and if your device uses a proxy, test without it if your organization allows that.

System settings > Network > VPN / Proxy

Loop loads and syncs normally on the direct connection.

If Loop works only when VPN is off, the network path is likely blocking or slowing the service. If you are on a managed work device, your IT team may need to allow the right Microsoft 365 endpoints.

7. Clear site data for Loop or Microsoft 365.

Do this only if the steps above didn’t help. Remove cached cookies and site data for Loop, then sign in again.

Browser settings > Privacy and security > Site data / Cookies > Search for Loop or Microsoft 365 > Remove

The next sign-in uses fresh site data and the page loads correctly.

If clearing site data fixes it, the old browser session was probably damaged. If the problem returns quickly, the browser profile or an extension is still involved.

8. Update the Loop app or your browser.

If you use the desktop or mobile app, install the latest update. If you use the web app, make sure the browser itself is current.

App store / Microsoft Store / browser menu > Help > About

The app or browser shows the newest available version and Loop behaves normally after reopening.

If an older app version is the issue, updates usually fix it. If not, the problem may be account-specific or workspace-specific.

If only one device, browser, or workspace fails

If Loop works on one device but not another, focus on the failing device first. The most common causes are browser cache, extensions, an out-of-date app, VPN, proxy, or device policy. Compare the working device with the failing one: same account, same browser version, same network, and same workspace.

If Loop works in one browser but not another on the same device, the browser profile is usually the problem. If it works on Wi-Fi but not on a company connection, the network path is more likely at fault. If it works on desktop but not mobile, update the app on the mobile device first.

If only certain workspaces fail, the issue is often permissions, sharing changes, tenant restrictions, or a workspace-specific problem. A shared workspace may open for you one day and fail the next if your access changed, the page was moved, or the owner changed sharing settings. A workspace that works on one account but not another often points to permission or tenant-policy differences, not a broken app.

How to tell if it’s working again

The fix is real only if Loop loads the same content consistently, not just once. Reopen the exact page, component, or workspace that was failing and check that it opens without hanging. Then make a small edit, wait for it to save, and reload the page to confirm the change is still there.

If you have access to another device or browser, open the same workspace there too. When the same content loads on both, the connection is probably fixed. If you’re using Loop with coworkers or classmates, ask one person to confirm they can see your latest change after a short delay.

The page opens, edits save, and the same content appears after refresh on at least one other device or browser.

If it works for a few minutes and then starts failing again, that usually means the root cause wasn’t removed. In that case, pay attention to patterns: does it fail only on Wi-Fi, only with VPN, only in one browser, or only after you join a certain workspace?

If it keeps happening, what to check next

If Loop keeps dropping connection after the quick fixes, look at the less obvious causes.

Check these next:

• Your browser is up to date and not blocked by a managed update policy.
• You are signed into the right work or school account, especially if you have more than one Microsoft account.
• Your company network is not filtering Microsoft 365 traffic too aggressively.
• The problem workspace still exists and you still have access to it.
• Your device date and time are correct, since bad system time can break sign-in and syncing.

If only certain workspaces fail, ask the owner or your Microsoft 365 admin to confirm the workspace permissions and any tenant restrictions on Loop, SharePoint, or guest access. If the problem happens across devices, browsers, and networks, contact Microsoft support through your organization’s normal support path and include the exact workspace name, the device you used, the browser or app version, and what you already tried.

If the issue keeps coming back after a fix, try to match the trigger. A recurring pattern makes the next step much easier to narrow down than starting from scratch every time.

Conclusion

If Loop is still stuck after these checks, don’t keep forcing refreshes forever. Try the same workspace in another browser or device, note exactly where it fails, and bring that pattern to your IT admin or Microsoft support.

Frequently Asked Questions

Why does Microsoft Loop work on one device but not another?

That usually means the problem is local to the failing device: browser cache, extensions, app version, VPN, proxy, or device policy. If the same workspace works elsewhere, the Loop service itself is probably fine.

Why do only certain Loop workspaces fail to load?

That often points to permissions, sharing changes, tenant restrictions, or a workspace-specific issue. If other workspaces open normally, check whether you still have access to the failing one and ask the owner or admin to review permissions.

Should I clear all browser data to fix Loop?

Usually no. Start by clearing site data for Loop or Microsoft 365 only. Clearing everything can sign you out of other sites and remove data you didn’t mean to touch.

Do I need admin rights to fix a Loop connection problem?

Most first steps do not need admin rights. You only need admin help if the issue comes from service health, tenant settings, permissions, or network policies.