Microsoft Loop outage: check what's down and get work moving

If Loop pages are blank, show an error, or edits won’t save, the problem is either a Microsoft service outage or a local/tenant issue; start by checking Microsoft 365 Service health and a quick client-side isolation (different browser or network). If the service is down, use OneDrive/SharePoint, Teams chat/channel documents, or OneNote as immediate fallbacks to keep working and preserve version history. If checks show no Microsoft incident, collect logs and escalate to IT or Microsoft Support with tenant ID, timestamps, affected users, error text and browser/Teams client logs.

Is this really a Microsoft Loop outage or something local to me?

Blank Loop page, spinning loader, "Couldn’t load component", or edits not saving in a Loop component embedded in Teams/Outlook.

When it appears

This appears when you open loop.microsoft.com or a Loop component inside Teams or Outlook and the content fails to load, the page shows an error, or changes don’t persist.

What to check first (fast, one-minute checks)

1. Check Microsoft 365 Service health in the Microsoft 365 admin center (requires admin access). Look for active incidents affecting Loop or collaborative services.

Microsoft 365 admin center > Health > Service health

2. Check an independent outage tracker such as Downdetector for recent reports showing many users affected.
3. Do a client-side isolation: open Loop in a different browser, an incognito/private window, or the Teams web app at https://teams.microsoft.com.
4. Try a different network or device: switch from corporate Wi‑Fi to a phone hotspot, or open the Loop content on another machine.
5. Confirm tenant scope: ask a colleague in a different tenant or a personal account to open the same content. If their experience differs, the issue may be tenant-specific.

Admin diagnostics to run next

• In the Microsoft 365 admin center, open Service health details to read incident scope and any estimated time to fix.
• In Azure AD, check Sign-ins for authentication failures that match the time and users affected.
• Search Message Center for recent updates that mention Loop or Fluid components.

If these checks show no Microsoft incident but failures persist, the problem is likely local: browser cache, network blocking, conditional access, or tenant configuration.

Before you start (applicability, privileges, quick safe checks)

Product and versions this applies to

• loop.microsoft.com and Loop components embedded in Teams desktop/web and Outlook desktop/web.

Privileges and access needed

• Admin checks (Service health, Message Center, Azure AD sign-ins) require Microsoft 365 Global Admin or equivalent.
• Tenant ID and sign-in logs require admin access to Azure AD.

Restart and backup notes

• No restart or backup is required for the quick checks below. Creating fallback files writes new content to OneDrive/SharePoint; that is safe and reversible.

Quick safe checks to run first

1. Open Loop in an incognito/private browser window.
2. Try accessing the component from another network (phone hotspot) or device.
3. If you have admin access, quickly confirm Service health in the Microsoft 365 admin center.

These checks take under five minutes and usually separate a local issue from a service-side outage.

If Loop is down, what parts are affected and will my files be lost?

Which components commonly fail

• The Loop UI (front end) that loads pages and components.
• Real-time syncing for shared components where edits may not appear to others until the service returns.
• Embedded Loop components inside Teams or Outlook that can fail to render even if stored data is intact.

Where Loop stores content and data safety

Loop components and pages persist in Microsoft 365 storage associated with your tenant: typically OneDrive for Business or SharePoint, depending on how the content was created or shared.

That means an outage that affects the Loop UI usually prevents access or syncing but does not delete stored content.

How to check content integrity after service returns

1. Re-open the component or page and confirm recent edits appear.
2. Check version history in the OneDrive or SharePoint location where the Loop content is stored to confirm saved versions.

Permanent deletion would be a separate incident and should be reported to Microsoft Support.

Quick workarounds to keep collaborating when Loop isn't available

Switch to an alternative that preserves edits and tracking

• Create a shared Word document in OneDrive or a SharePoint document library and paste the Loop content there for collaborative editing.
• In Teams, post the content to a channel or chat and attach a shared OneDrive document for collaborators to edit.
• Paste content into OneNote, create a shared page, and continue editing there.
• Work on a local or offline copy and merge changes back after the service is available.

One-sentence instructions

• Create a new Word doc in OneDrive and paste Loop content; share with Edit permissions.
• In Teams, start a channel post and attach a shared OneDrive document for collaborators to edit.

Preserving edits and version history

• Files stored in OneDrive or SharePoint keep version history automatically.
• If collaborators make separate offline copies, plan a single merge step later and record authors and timestamps in the merged file to preserve context.

Checks to confirm Loop is working again and how to validate your content

What to refresh and re-check

1. Refresh the Loop page or re-open the Loop component in Teams/Outlook and confirm the UI and components render.
2. Check Microsoft 365 admin center Service health to confirm the incident is marked resolved.
3. Test the component in both loop.microsoft.com and the host app (Teams/Outlook) to ensure both surfaces work.

How to confirm edits synced correctly

• Open the OneDrive/SharePoint storage location for the Loop content and review version history for recent saves.
• If you used a fallback document, compare that file with the live content and merge differences if needed.

Simple checklist to sign off to users

• Service health shows no active Loop incidents.
• Loop pages/components load for you and at least two other users.
• Expected edits are present in the live component or in OneDrive/SharePoint version history.
• Embedded components load in Teams/Outlook.

If all items pass, tell users they can resume work and avoid concurrent edits on temporary offline copies until everything is fully synced.

When to escalate to your IT admin or Microsoft Support and what to include

When to escalate

• Escalate to IT admin when the issue affects multiple users in your tenant, persists after client-side checks, or authentication failures appear in Azure AD sign-ins.
• Open a Microsoft support ticket when the Microsoft 365 admin center shows no incident but the service still fails for your tenant, or when data integrity looks suspect.

Information to collect before you escalate

• Tenant ID (from Azure AD or Microsoft 365 admin center).
• Exact timestamps (UTC) when the failure occurred and when you retried.
• Affected users and sample user UPNs.
• Exact symptom text or error messages and the host app (Loop web, Teams desktop, Teams web, Outlook).
• Browser and version, or Teams desktop client version.
• Network details (corporate network, VPN, or home network) and whether the issue persisted across networks.
• Screenshots of errors and browser developer console logs.

What logs and commands are useful

• Azure AD Sign-in logs showing failed token or authentication attempts at the incident time.
• Browser developer console output (copy/paste the error lines).
• Network trace or packet capture, provided to IT or Microsoft Support when requested.

How to open a support ticket (fastest path)

1. In Microsoft 365 admin center, go to Support > New service request and include the details above.

Microsoft 365 admin center > Support > New service request

2. Attach screenshots and console logs and provide a clear timeline and the number of affected users.

What escalating does for you

• Microsoft support can access backend telemetry for your tenant and correlate the failure with service-side incidents or configuration problems, which usually speeds resolution.

What usually causes Microsoft Loop outages and how to reduce disruption next time

Common root causes

• Service-side updates or deployments that introduce a regression.
• Authentication or token service failures in Azure AD that prevent users from renewing access tokens.
• Dependent Microsoft 365 services (OneDrive/SharePoint or Graph API) experiencing issues that block Loop persistence or syncing.
• Network or conditional access policies blocking required endpoints.

Practical preparedness steps for IT leads

• Keep a short runbook listing immediate checks (Service health, Azure AD sign-ins, Message Center) and quick fallbacks (SharePoint/OneDrive docs, OneNote, Teams channel).
• Prepare a communication template for users that explains the symptom, temporary workarounds, and an ETA check-in schedule.
• Ensure admins know where version history lives for Loop-backed content and how to retrieve it.
• Maintain a fallback storage location and sharing pattern (a OneDrive folder or a SharePoint page) that teams can switch to quickly.
• Document required endpoints for Loop so network or proxy appliances can whitelist them if needed.

You cannot prevent all outages. The goal is to shorten impact by validating quickly, switching to safe fallbacks, and communicating clearly.

Conclusion

If Loop fails, first confirm scope using Microsoft 365 Service health and simple client-side checks. Use OneDrive/SharePoint, Teams, or OneNote as fallbacks to keep working and preserve version history. If the problem persists with no public incident, escalate with tenant ID, timestamps, affected users, error messages and console logs.

Frequently Asked Questions

Will my Loop content be deleted during an outage?

No—content is persisted in Microsoft 365 storage (OneDrive/SharePoint). An outage usually prevents access or syncing temporarily; deletion would be a separate incident and should be reported to Microsoft Support.

How long should I wait before escalating to Microsoft Support?

If multiple users are affected and the Service health dashboard shows no active incident, escalate after 15–30 minutes of checks and log collection; escalate sooner if data integrity looks compromised.

Can I keep working offline and merge changes later?

Yes—work offline in local copies or OneNote and paste or merge changes back when Loop is available. Avoid simultaneous edits in multiple offline files unless you plan a manual reconciliation step.