> ## Content Index > Fetch the complete content index at: https://todayfixtech.com/llms.txt > Use this file to discover other available public pages before exploring further. # Microsoft Lists keeps disconnecting — how to fix it now - URL: https://todayfixtech.com/microsoft-lists-disconnecting/ - Published: 2026-10-30T06:46:51.000Z - Updated: 2026-10-30T06:46:50.000Z - Author: Md Sojib Mia - Tags: Troubleshooting, Microsoft [If Microsoft Lists keeps](https://todayfixtech.com/microsoft-365-tips-tricks/) disconnecting, the problem is usually a local client or network issue, or a tenant policy (Conditional Access or token/session rules); service outages are less common. Quick fixes that usually restore access are signing out and back in, clearing site data or using an incognito window, updating the browser or Teams app, and testing from a different network or device. If those steps fail, collect diagnostics (HAR, console logs, Teams logs, sign-in logs) and escalate to your admin or Microsoft support with that package. ## Is it just me or is Microsoft Lists down for everyone ```text Lists page or list items load then drop to a blank page, show "connection lost", return frequent 401/403 errors, or the Lists app in Teams shows "Something went wrong". ``` Symptom When this happens: immediately check whether other users or services are affected. 1. Open the Microsoft 365 admin center and check Service health (admins only). ```text Microsoft 365 admin center → Health → Service health ``` Settings path Expected result: the admin center lists active incidents and advisories. If it shows a Lists/SharePoint/[Microsoft 365 incident for](https://todayfixtech.com/fix-microsoft-365-login-issues/) your region, the issue is service-side; wait for Microsoft updates. 1. Check Azure status or Microsoft 365 status pages for platform incidents. 2. Check a public outage tracker (DownDetector) or the official Microsoft Twitter account for broader reports. What the outcomes mean: - Admin center shows an incident: service-side problem; monitor Microsoft updates. - No incident but many users report the same behavior: escalate to your admin to open a Microsoft support case with Microsoft. - Only you or a small group affected and admin center is clean: proceed with local and tenant-level diagnostics. ## Could this be my device, network, or browser Before you start - Applies to: Microsoft Lists in browser, Lists app in Teams (desktop/web), and Lists mobile app on iOS/Android. - Privileges: normal user for the checks; admin only for tenant-level changes. - Restart or backup: a simple browser restart or device reboot is safe. No backups required. - Safe first checks: try an incognito/private window and test from a different network or device. Fast local checks (do them in this order): 1. Incognito/private window test - Open a private window and load Lists or the SharePoint list URL. Expected result: lists load normally. What it means: a browser extension or cached state is likely causing disconnects. 1. Different browser - Try the same list in Edge, Chrome, Firefox, or Safari. Expected result: lists work in another browser. What it means: current browser profile or settings are at fault. 1. Disable extensions - Temporarily disable all extensions and reload the list. Expected result: stable connection. What it means: an extension interferes with auth or requests. 1. Clear site data for Microsoft domains - Clear cookies and site data for `microsoft.com`, `office.com`, `sharepoint.com`, and your tenant domain. ```text Browser settings → Privacy & security → Cookies and other site data → See all cookies and site data → search for microsoft, office, sharepoint, .onmicrosoft.com → Remove ``` Settings path Expected result: resolves stale auth tokens or corrupted site data. 1. Test on mobile or another network - Open the Lists mobile app or load the list on a phone using cellular data. Expected result: if mobile + cellular works but office Wi‑Fi fails, the office network or proxy is likely the cause. 1. Check DNS and VPN - If using a VPN, disconnect and retry. If DNS is custom, try switching to a public DNS if allowed. Expected result: success off VPN indicates VPN rules or routing are breaking requests. 1. Observe error codes in the browser console - Open DevTools (F12) → Console and Network tabs while reproducing the error. Look for HTTP 401, 403, 429, 500, or CORS errors. Expected result: the error code indicates whether it’s permission (401/403), throttling (429), or server (5xx). ## Common quick fixes to try now Where to act: user device (browser, Teams app), network client settings. 1. Sign out and sign back in - Sign out from Office 365/Teams/OneDrive in the app or browser and sign back in. Expected result: auth tokens refresh and Lists reconnect. What it means if it fails: tokens or Conditional Access session policies may prevent refresh. 1. Clear browser site data for Microsoft domains - Clear cookies and site data only for these domains rather than a full profile reset. ```text Browser settings → Privacy & security → Cookies and other site data → See all cookies and site data → search for microsoft, office, sharepoint, .onmicrosoft.com → Remove ``` Settings path Expected result: stale cookies removed; reauth required; connectivity restored. 1. Update browser and Teams app - Update to the latest stable browser version and the Teams desktop/mobile app. Expected result: fixes tied to older clients. 1. Disable problematic extensions - Temporarily disable ad blockers, privacy plugins, or developer tools that alter headers. Expected result: if disabling fixes it, re-enable extensions one-by-one to find the culprit. 1. Reboot device - Restart the machine or phone. Expected result: clears local network state and stuck sockets. 1. Try app vs web - If web fails, try the Teams Lists app or SharePoint app; if the app fails and web works, client settings or cache is at fault. Expected result: identifies client-specific issues. 1. Toggle VPN or proxy - Disconnect from VPN or proxy and test again. Expected result: if disconnects stop, investigate VPN split tunneling, firewall rules, or proxy header modifications. Emptying the whole browser profile or reinstalling Teams is more invasive; try the above first. ## If quick fixes don’t help, check tenant and account controls Where to act: Azure AD / Microsoft 365 admin center — requires admin privileges. 1. Conditional Access policies - Check for policies that block or require compliant devices, MFA, or named locations. Look for policies applying to SharePoint, Exchange Online, Microsoft 365 apps or All Cloud Apps. ```text Azure Active Directory → Security → Conditional Access → Policies ``` Settings path Expected result: identify policies that might prompt reauthentication or block sessions. If a policy recently changed, rollback or create an exception for a test user. 1. Session control and token lifetime - Inspect sign-in frequency or session controls under Conditional Access and Identity Protection; short refresh token lifetimes or forced reauth can appear as reconnects. ```text Azure Active Directory → Security → Conditional Access → Session controls ``` Settings path Expected result: longer session frequency reduces reauth prompts; if no change is allowed, note that behavior for support. 1. License and service status - Ensure affected accounts have valid Microsoft 365 licenses that include SharePoint/Lists. ```text Microsoft 365 admin center → Users → Active users → Select user → Licenses and apps ``` Settings path Expected result: license missing can cause access errors. 1. SharePoint and Lists permissions - Verify the list or site permissions: broken inheritance, expired guest access, or missing group membership causes 403 errors. ```text SharePoint admin center → Sites → Active sites → → Permissions ``` Settings path Expected result: fix permissions or re-add the user to the right group. 1. Recent tenant changes - Ask admins to review Audit logs and Azure AD sign-in logs around the timestamps of disconnects to spot policy blocks, MFA prompts, or risk detections. ```text Azure Active Directory → Monitoring → Sign-ins ``` Settings path Expected result: sign-in log entries show error codes and Conditional Access evaluation details that pinpoint the tenant-level cause. ## Gather logs and diagnostics before you escalate What to collect and how (one action per step): 1. Capture the browser console and network errors - Open DevTools (F12) → Console and Network and reproduce the disconnect. 1. Save a HAR file (HTTP Archive) - In DevTools Network tab, right-click and select "Save all as HAR". ```text DevTools → Network → Right click → Save all as HAR ``` Settings path Expected result: a HAR file containing request/response pairs and timestamps. 1. Collect Teams desktop logs - For Teams desktop: use `Ctrl+Alt+Shift+1` (Windows) to create logs in your Downloads folder. ```text Teams → Ctrl+Alt+Shift+1 (Windows) or Command+Option+Shift+1 (Mac) ``` Settings path Expected result: log package including client traces. 1. Office telemetry (admins) - If Office telemetry is enabled, collect diagnostic logs per admin guidance. 1. Note exact timestamps, tenant ID, user UPN, device type, client versions, and network (Wi‑Fi/cellular/VPN) - Have the UTC timestamps for when disconnects occurred and whether others saw the same issue. 1. Screenshots and short video of the failure - Show the error message, console errors, or the behavior in Teams/Lists. What each item helps with: HAR + console show HTTP/JS errors; Teams logs show client-level auth or socket errors; sign-in logs show Conditional Access decisions. Remove or redact personal data (SSNs, passwords) from logs before sending to support. ## How to verify the problem is fixed and prevent it coming back Verification tests (do them in order): 1. Reproduce for 24–48 hours - Use Lists across your browser, Teams, and mobile; verify no reconnects during typical workflows. Expected result: stable access and no repeated 401/403/5xx errors. 1. Cross-client consistency - Confirm the list loads in an incognito window, a different browser, and the Lists mobile app. Expected result: consistent behavior indicates a true fix rather than a local workaround. 1. Monitor sign-in logs (admin) - Watch for repeated Conditional Access evaluations or token refresh errors for the user. Expected result: no new policy blocks or high failure rates logged. Prevention best practices: - Keep browsers and Teams clients updated. - Avoid aggressive cookie-clearing schedules that log users out frequently. - Review Conditional Access rules for overly strict session lifetimes; prefer sensible sign-in frequency unless security policy requires short windows. - Ensure VPNs and proxies preserve authentication headers and allow Microsoft endpoints; use split tunneling for Microsoft 365 where safe and supported. - Document and rollback tenant policy changes in a controlled change window so you can trace new disconnects to configuration changes. Some security requirements (for example, device compliance) will intentionally require frequent reauthentication; confirm policy intent with your security team. ## When to contact your admin or Microsoft support and what to say Threshold for escalation: - Contact internal admin/helpdesk when multiple users, a department, or all users experience disconnects, or when you’ve collected logs and cannot identify a local cause. - Contact Microsoft support when tenant-level logs show Microsoft service errors, the Microsoft 365 admin center shows an incident but no public update, or support asks for a Microsoft investigation. Who to contact and how to package the issue: 1. Internal helpdesk: provide these items in your ticket - Exact timestamps (UTC) of failures. - Your UPN and tenant ID. - A HAR file, browser console screenshot, and a brief description of steps that reproduce the issue. - Whether the issue occurs on cellular, a different network, or another device. 1. Microsoft support: include everything above plus admin-level logs - Azure AD sign-in logs for affected users around the timestamps. - Any Conditional Access policy names applied and their evaluation results. - Teams desktop log package and HAR file. Suggested message template (short): ```text Users in tenant started seeing intermittent disconnects to Microsoft Lists from