Microsoft Loop service status: check if Loop is down and what to do

If Microsoft Loop won’t open, first check Microsoft’s official health dashboards to see if there’s a service incident; if those show a Loop/Fluid incident, wait for Microsoft to restore service. If the dashboards show no incident, treat it as an account, tenant, or network problem and run the quick local tests below (different browser, different network, different account). The steps below help you confirm scope, apply safe fixes and fallbacks, report the problem with the right details, and verify resolution.

Is Loop actually down for everyone or just you?

Loop won’t load or displays an error such as “Something went wrong” or a blank canvas; collaborative updates don’t appear; Loop components fail to sync.

When this appears

• When you open loop.office.com, a Loop component in Teams, or Loop inside Outlook and the page stays blank, shows an error, or edits don’t propagate to other users.

Where to check Microsoft’s official status

• Microsoft 365 Service health page in the Microsoft 365 admin center shows incidents and advisories for services tied to your tenant. Look for entries mentioning “Loop,” “Fluid components,” or “Office for the web.”
• Azure status page lists platform outages that can affect services; check the region your tenant uses if you suspect a regional problem.
• Microsoft status Twitter/X or Microsoft 365 Status account sometimes posts updates during wide incidents.
• Third-party outage trackers (Downdetector, Pingdom-based dashboards) show user reports but are not authoritative.

How to interpret Loop-specific entries

• If the Microsoft 365 admin center lists an incident that explicitly names Loop or Fluid/Loop components, it’s likely a service-side problem affecting many tenants. The admin center shows incident status (Investigating, Service degradation, Restoring, Resolved).
• If the status mentions Office web services or SharePoint but not Loop, confirm whether the failing feature depends on those services in your tenant.
• If there’s no matching incident in the admin center but many users are affected, gather evidence (timestamps, screenshots, affected users) and report it (see reporting section).

Could this be an account, tenant, or network problem instead of a Loop outage?

Before you start

• Product/versions: Applies to Microsoft Loop in browsers and the Loop experience inside Teams and Outlook on the web. No special client versions are required beyond up-to-date browsers and Microsoft 365 subscriptions that include Loop features.
• Privileges: For tenant-level checks you need Microsoft 365 admin access; for user-level tests normal user rights suffice.
• Restart/backup: No restart or backups are required for the quick checks below.

Safe checks to do first

• Test a different account: sign in with a personal Microsoft account or another tenant account. If a personal account works while your work account fails, the issue is likely tenant-specific.
• Test a different network: switch to a cellular hotspot or a home network. If Loop works on a different network, the corporate firewall/proxy or Conditional Access policy is implicated.

Common non-global causes

• Authentication errors: expired tokens, Conditional Access policies, or MFA prompts blocked by the browser can prevent Loop from loading.
• Tenant rollout or licensing: Loop features are rolled out; your tenant might not have the feature enabled or required licenses assigned.
• Network filtering: corporate firewall, proxy, DNS, or web filtering blocking Loop endpoints.

Quick narrowing test (one-minute)

1. Open your phone, enable a cellular hotspot, connect your laptop, and try Loop in a private/incognito browser window.
2. Sign in with your work account and try again.

If it works on the hotspot, the problem is network-level. If it fails on the hotspot but a personal account works, it’s tenant- or account-related.

Immediate fixes and workarounds to keep working if Loop isn’t loading

Where to act: browser or client. Privilege: standard user for all steps.

1. Reload and hard-refresh the page.

Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)

Expected result: page reloads and content appears. If still blank, continue.

2. Sign out and sign back in to clear stale authentication tokens.

Browser: profile menu > Sign out
Office web: top-right account > Sign out

Expected result: reauthentication prompts and a successful Loop load. If you get authentication errors, your account or identity provider may be blocking access.

3. Try another browser or use an incognito/private window.

Open a different browser or choose New Incognito Window / New Private Window

Expected result: if an extension or corrupted cache caused the issue, Loop should load. If it works here, disable extensions in the main browser and clear its cache.

4. Clear Loop or browser storage for the site (safe and reversible).

Browser settings > Privacy and security > Site settings > Storage > Clear data for loop.office.com or teams.microsoft.com

Expected result: site data removed; reload should fetch fresh resources. If the problem persists, the issue is less likely to be client cache.

5. Use Loop inside Teams or Outlook on the web as a fallback.

• Teams and Outlook sometimes use alternate endpoints that continue syncing when the standalone Loop web app fails. Open the same Loop component from Teams chat or from Outlook compose if available.

6. Use a temporary alternative for collaborative editing: OneNote, a shared Word document in OneDrive or SharePoint, or Microsoft Whiteboard while Loop is unavailable.

Example: if a corporate proxy causes a blank Loop canvas in Chrome, switch to your phone hotspot, open Edge in private mode, sign in, and continue via Teams if the Loop client still fails. That keeps work moving while you collect data to report the issue.

How to gather the right info and report the outage to Microsoft or your IT team

What to collect before reporting

• Exact timestamps (with timezone) when you first saw the problem and when you reproduced it.
• Screenshots of the error or blank pages, including the browser address bar and any console errors.
• Exact error text or HTTP status codes if shown.

Example: "Failed to load resource: the server responded with a status of 503 (Service Unavailable)"

• Tenant ID and affected user list (user principal names or emails). Admins can find Tenant ID in the Microsoft 365 admin center under Settings > Org settings or Azure AD properties.
• What you already tried: browsers, networks, accounts, and whether Loop inside Teams/Outlook works.
• Correlation with Microsoft health pages: note whether an incident was reported and include its incident ID if available.

How to report (channels)

• Microsoft 365 admin center support: admins should open a service request from Support > New service request. Attach screenshots, timestamps, tenant ID and steps to reproduce.
• In-product feedback: users can use the feedback/report a problem option inside the Loop experience and include reproduction steps and screenshots.
• Escalation: if this affects business-critical workflows, admins can request faster handling when creating the support ticket.

Example support message

Tenant ID: 12345678-aaaa-bbbb-cccc-0123456789ab
First seen: 2026-11-03 09:12 UTC
Affected users: alice@contoso.com, bob@contoso.com
Symptom: Loop canvas fails to load (blank page). Browser console shows 503 on https://loop.microsoft.com/api/...
Tried: hard refresh, sign out/in, incognito, different network (cellular hotspot), Loop in Teams works for some users.
Please investigate; no related incident shown in Service health as of report time.

If you’re a user, give your IT admin the same data; don’t open a Microsoft ticket unless you’re an admin or instructed to do so.

How to confirm the problem is resolved and what to monitor next

How to verify resolution

1. Reproduce the failed action you recorded earlier (open the same Loop component, create or edit content, check sync). Expected result: the Loop component loads and edits sync across users.
2. Confirm with other affected users on different networks/accounts that their issues are resolved.
3. Check the Microsoft 365 Service health entry for the incident and validate its status shows Restored or Resolved.

What to monitor short-term

• Set Service health alerts in the Microsoft 365 admin center so admins receive automated notifications when Microsoft records incidents affecting your services.
• Follow Microsoft status accounts for real-time updates during major incidents.
• If the problem was tenant-specific (policy, Conditional Access), monitor Conditional Access sign-in logs and Azure AD health for repeated authentication failures.

Expected signals of a persistent problem

• Some users recover while others don’t: often indicates tenant policy or Conditional Access differences.
• Service health says resolved but users still see errors: allow several minutes for cache and propagation; if the issue persists, reopen the support ticket with fresh logs.

Common questions people miss when checking Loop status

Q: Why does the admin center show no issue while users are affected? A: Microsoft’s automated detection can miss tenant-specific or network-layer problems. A dependent service (authentication, SharePoint, Exchange) might fail and produce Loop symptoms without the Loop service itself being flagged.

Q: Microsoft says they fixed it but I still have problems—what then? A: Allow a few minutes for propagation and caches to clear. Clear browser cache, try a new browser session, and confirm with other users. If the issue persists beyond a short wait, collect logs and reopen the ticket.

Q: When will tenant-level issues be restored compared to global outages? A: Global outages are resolved when Microsoft restores the central service. Tenant-level issues (policies, licensing) require administrative action in your tenant and won’t be fixed by Microsoft unless the root cause is on their side.

Conclusion

If checks show a Microsoft incident, wait for Microsoft to resolve and follow the admin center updates. If the admin center shows no incident, run the quick tests (different account, network, browser), use the workarounds above, collect timestamps/screenshots/tenant ID, and open a support request from the Microsoft 365 admin center or hand the data to your IT admin.

Frequently Asked Questions

What domains or endpoints should I allow to let Loop work through a corporate firewall?

Allow loop.office.com, teams.microsoft.com, and the Microsoft 365 endpoints used by Office for the web and SharePoint. Work with your network team to permit Microsoft 365 service endpoints and check Microsoft documentation for the current endpoint lists.

Can I keep working offline if Loop is down?

Loop requires online services for real-time collaboration. For short outages, use a shared Word or OneNote file stored in OneDrive or SharePoint as a temporary collaborative document; those have better offline sync and will let users continue editing until Loop is restored.