Microsoft Loop not connecting: how to get it working again

If Microsoft Loop is stuck connecting, spinning, or refusing to sync, the usual cause is a Microsoft service issue, a broken sign-in/session, or a workspace-level permission or tenant setting. The fastest fixes are to check service health, sign out and back in, then try Loop in a private window or another browser/device. If it only fails in one workspace or one file, the problem is usually permissions, cached site data, or a Microsoft 365/Teams/OneDrive session issue rather than Loop itself.

What the problem looks like when Loop won’t connect

Loop problems usually show up as endless loading, a spinning indicator that never finishes, a blank page, a sign-in loop, or a message that the workspace or page can’t sync. Sometimes the page opens, but edits don’t appear for other people, or you see a stale version after waiting.

If the issue is broad, you may see it across multiple workspaces and on multiple devices. If it only happens in one workspace, one page, or only after you open Loop from Teams or Outlook, that usually points to a permission problem, cached browser data, or a Microsoft 365 session that is only broken in one place. If other Microsoft 365 apps are also acting strangely, treat it as a wider account or service issue rather than a Loop-only problem.

When this is a Loop issue and when it’s something else

This applies to Microsoft Loop in a browser and the Loop experience inside Microsoft 365 apps such as Teams and Outlook. You do not need administrator rights for the first checks, and none of the first fixes require a restart or any file backup.

Before you change anything, do two safe checks:

• Open another Microsoft 365 app, such as Outlook or Teams, and see if it signs in normally.
• Try opening Loop in a private or Incognito window before changing any settings.

If many users in your tenant have the same problem, Microsoft’s service status or an admin setting is a likely cause. If only your device fails, look at the browser, cached data, VPN, extensions, or sign-in state. If only one workspace fails, think permissions, tenant restrictions, or a broken link to the underlying SharePoint or OneDrive content.

A slow or unreliable network can also make Loop look broken. A captive portal, filtered network, proxy, VPN, or strict privacy setting can stop the app from loading its sign-in and sync components even though other websites still work.

Try the quickest fixes first

Start with the least disruptive checks. They solve a lot of Loop connection problems and are safe to try first.

1. Check Microsoft 365 service health.

If your organization has an admin center, have someone check the Microsoft 365 service health page for Loop, Teams, SharePoint, and OneDrive incidents. If Microsoft is reporting a problem, there may be nothing to fix on your side yet. If no incident is listed, move on.

2. Sign out of Microsoft Loop and sign back in.

Open Loop, sign out if you can, then close the browser tab or app completely and sign in again with the same work account.

You return to the workspace and Loop loads without the endless spinner.

If the sign-in screen loops or you land back at the same blank page, the stored session is probably stale. Continue to the next step.

3. Hard refresh the page.

In a browser, reload the page with a hard refresh. This forces the browser to fetch current page data instead of using what it already cached.

Windows or Linux: Ctrl+Shift+R
Mac: Command+Shift+R

If the page still hangs, try a private window next.

4. Open Loop in Incognito or InPrivate mode.

Use a private window so the browser starts with a clean session and no old site data.

Loop opens normally, or it fails in a different way that points to account or permission trouble.

If it works there, your normal browser profile likely has bad cache, cookies, or an extension conflict.

5. Try another browser or another device.

Use a current version of Edge, Chrome, or another supported browser, then test from a second device if you can. A browser-specific fix is much easier to narrow down than a tenant-wide one.

6. Clear site data for Loop and Microsoft sign-in pages.

If private mode works but your normal browser does not, clear the site data for Loop and Microsoft login sites, then sign in again. This is more targeted than clearing all browser data.

Browser settings > Privacy and security > Site data and cookies > See all site data and permissions

Clearing site data signs you out of Microsoft 365 in that browser and may remove saved session data.

If your browser has a site-data search box, look for Loop and Microsoft sign-in entries, then remove only those entries before you try again. If that is not available in your browser, clear the site data for the Microsoft login and Loop sites through your browser’s site permissions or cookie settings.

7. Disable VPNs, proxy tools, and extensions that can interfere.

Turn off VPN software, privacy extensions, ad blockers, and script blockers, then reload Loop. These tools can block the cookies or embedded requests Loop needs to connect.

If one of these fixes works, the page should stop spinning and your workspace should load with current content. If none of them changes anything, the cause is probably workspace-specific or controlled by your tenant settings.

Check whether Loop is connecting now

Once you think it is fixed, verify it in the same place that failed before. Open the same workspace, page, or file, not just a different one. Then make one small edit and wait to see whether it saves and appears as expected.

A good check looks like this:

• Open the same Loop workspace that was stuck.
• Refresh the page and confirm it still loads.
• Make a small edit, then watch for it to save.
• If you collaborate with someone else, ask them to confirm they can see the change.

If Loop works on one browser but not another, the fix is local to that browser profile. If it works on your phone but not your laptop, the laptop’s browser, network, or security software is still the likely blocker. If it works for one workspace but not another, that usually points to permissions, sharing settings, or a problem with the underlying SharePoint or OneDrive location for that specific item.

If it still won’t connect, what usually blocks it

When the quick fixes do not help, the problem is often one of these less obvious blockers.

• Third-party cookies are blocked. Loop and Microsoft sign-in flows can fail if the browser blocks the cookies they use for authentication.
• The browser is out of date. An older browser can break modern Microsoft 365 sign-in and embedded app behavior.
• Your account lacks access to that workspace. If the page belongs to a shared workspace, the owner may have removed your permission or changed the share link.
• OneDrive or SharePoint is having trouble. Loop content depends on Microsoft 365 storage and identity services, so a OneDrive or SharePoint issue can look like a Loop failure.
• A tenant setting blocks Loop. Your Microsoft 365 admin may have disabled Loop, restricted it to certain groups, or blocked it through compliance or privacy policy.
• Teams or Microsoft 365 has a stale session. If Loop is launched from Teams, the Teams session can be the part that is broken even when the browser itself seems fine.

If only one workspace fails, test a different workspace and compare the behavior. If all workspaces fail, the account, browser, or network is the better place to focus. If you have an admin, give them the exact workspace name, the browser you used, and whether the problem happens on another device. That narrows it down much faster than saying only that Loop will not load.

Conclusion

If Loop still will not connect after the browser and sign-in checks, treat it as a workspace, tenant, or Microsoft service issue and hand over the details to your admin or IT support. The most useful clues are whether it fails everywhere or only in one workspace, and whether it works in a private window or on another device. Keep the working browser or device open if you can, since that helps you compare what is different.

Frequently Asked Questions

Why does Microsoft Loop keep spinning and never load?

The usual causes are a stale sign-in session, blocked cookies, a browser extension, or a Microsoft 365 service problem. If it only happens in one browser profile, clear the site data for Microsoft and try again.

Why does Loop work in Incognito but not my normal browser?

That usually means something in the normal profile is interfering, such as cached data, cookies, or an extension. Clearing site data or disabling extensions is the next step.

Why can I open one Loop workspace but not another?

That often points to permissions, sharing settings, or the underlying SharePoint or OneDrive location for that workspace. It can also mean only one item has corrupted cached data.

Can my organization block Microsoft Loop from loading?

Yes. Tenant settings, compliance rules, or app restrictions can block Loop or parts of it. If nothing works across devices and browsers, an admin should check the tenant configuration.