> ## 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 not launching — diagnose and fix so it opens - URL: https://todayfixtech.com/microsoft-lists-not-launching/ - Published: 2026-10-30T07:11:34.000Z - Updated: 2026-10-30T07:11:34.000Z - Author: Md Sojib Mia - Tags: Troubleshooting [If Microsoft Lists opens](https://todayfixtech.com/fix-microsoft-365-login-issues/) to a blank page, a perpetual spinner, or an error, the cause is usually client-side (browser/Teams cache, extensions), account/service issues (license, permissions, or M365 outage), or a network/tenant security block. Start with quick, low-risk checks: sign out/in, try an incognito/private window or another browser/device, and confirm Microsoft 365 service health and licensing. If those don’t help, follow the stepwise fixes below from safest (cache, extensions) to advanced (repair Office, clear Teams cache, tenant policies, proxies/firewall). ## What exactly happens when I open Microsoft Lists ```text Blank page after the Lists UI loads Perpetual spinner with no content Explicit error message or code (for example: correlation ID, HTTP 500, 403, 401) Lists works everywhere except inside Teams or the Lists mobile app Lists opens but specific lists fail to render ``` Symptom When it appears - Immediately after clicking Lists (page stays white or shows UI chrome but no list content). - After authentication redirects (spinner loops after sign-in). - Only inside Teams while web browser access works, or only in a particular browser while other browsers work. Why the distinction matters - Blank page or spinner usually means client-side rendering or blocked requests (browser JavaScript, extensions, cache, or blocked network calls). Fixes focus on clearing cache, disabling extensions, or trying a different browser/client. - Explicit error codes like `401` or `403` point to authentication, licensing, or permissions; check the account, assigned licenses, and SharePoint/list permissions. - `HTTP 500` or a correlation ID normally indicate a server-side or tenant problem; check Microsoft 365 service health and capture the correlation ID for support. - Problems only inside Microsoft Teams suggest the Teams webview or its cache, Conditional Access policies, or the Teams client rather than the Lists service itself. ## Could this be caused by service, account or permission issues Before you start - Product/versions: Microsoft Lists in browser, Microsoft Teams desktop app, and the Lists mobile app. - Privileges needed: user account for local checks. Tenant admin (Microsoft 365 admin) for service health, licensing, Conditional Access, and SharePoint tenant settings. Network admin for proxy/firewall checks. - Restart/backup: no restart or backup required for the quick checks below. - Safe checks to do first: verify service health and confirm you can open SharePoint. Check Microsoft 365 Service Health (admin) 1. Sign in to the Microsoft 365 admin center as an admin. ```text Admin center > Health > Service health ``` Settings path 1. Look for incidents affecting SharePoint or Microsoft Lists. If an outage is listed, the fix is Microsoft’s; follow the incident notes. Verify user license and product access (admin) 1. In the admin center, open Active users. ```text Admin center > Users > Active users ``` Settings path 1. Select the user and check Product licenses to confirm a license that includes SharePoint/Lists is assigned. What to check as a user - Sign in at `portal.office.com` and open SharePoint; if SharePoint home fails, the issue is likely service, licensing, or tenant configuration. - If you can open other Microsoft 365 apps but not Lists, suspect site or list permissions. Verify site/list permissions 1. Open the SharePoint site that hosts the list (Site contents > the list). If you can open the site but not the list, check whether the list has unique permissions. 2. If you have site owner access: Site settings > Site permissions. ```text Site settings > Site permissions ``` Settings path If you lack site owner access, ask the site owner to confirm your permission level. If access is blocked with `403`, capture the error page and any correlation ID for escalation. ## Quick safe fixes to try first (minutes) Where to act: browser, Teams client, or mobile app. Privilege: your user account. 1. Sign out and sign back in. ```text Browser: click profile > Sign out Teams: click profile > Sign out Mobile: app settings > Sign out ``` Settings path Expected result: Lists loads after a fresh sign-in. If not, continue. 1. Open Lists in a private/incognito window. ```text Browser: New InPrivate/Incognito window ``` Settings path Expected result: If Lists opens, the issue is browser cache or an extension. 1. Try a different browser or the Lists mobile app. Expected result: If another browser works, keep using it and troubleshoot the original browser’s cache and extensions. 1. Disable browser extensions and test. - Disable all extensions, then enable them one-by-one to find the culprit. Expected result: Lists opens when a problematic extension is disabled. If none are problematic, re-enable extensions. 1. Test with another account or device. Expected result: If another account works on the same device, the problem is account or permission related. If another device works with the same account, the problem is client or device-specific. ## If it still won’t open: browser and client troubleshooting Where to act: browser or Teams on the device. Privilege: your user account. Clear browser cache and site data 1. Open the browser settings and clear cached images, files and site data for `office.com`, `sharepoint.com` and `microsoft.com`. ```text Browser settings > Privacy and security > Clear browsing data > Cached images and files; Cookies and other site data ``` Settings path Expected result: Lists loads after clearing. If it doesn’t, proceed. Reset site permissions for Lists/SharePoint 1. Open site settings for the SharePoint site and remove any denied entries or blocked cookies for the domain. ```text Site settings > Site permissions ``` Settings path Expected result: Removing blocked site permissions allows scripts and cookies required for Lists to run. Enable modern browser features - Ensure JavaScript is enabled, third-party cookies are allowed for Microsoft domains, and TLS 1.2+ is enabled in browser/OS settings. Clear Teams cache (desktop) Close Teams before clearing cache. 1. Quit Teams completely. 2. Delete the Teams cache folders. ```powershell Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\Application Cache\Cache" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\Blob_storage" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\Cache" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\databases" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\IndexedDB" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\Local Storage" Remove-Item -Recurse -Force "$env:APPDATA\Microsoft\Teams\tmp" ``` PowerShell (run as Administrator) Expected result: Teams opens a fresh session and embedded Lists pages render. If not, sign in again or reinstall Teams. Repair Office (Windows) Repair may require administrative privileges and can take several minutes. 1. Open Settings > Apps > Installed apps, find Microsoft 365, choose Modify, then Quick Repair. If Quick Repair doesn’t fix it, try Online Repair. ```text Settings > Apps > Installed apps > Microsoft 365 > Modify > Quick Repair ``` Settings path Expected result: Office web integrations are restored; if Lists still fails, consider reinstalling the mobile app or the Teams client. Reinstall Lists mobile app 1. Uninstall, then reinstall the Lists app from the official app store and sign in again. Expected result: Mobile app renders lists normally if device-specific corruption caused the issue. ## Network, security and tenant-level causes to check next Where to act: network team, tenant admin. Privilege: [network admin or Microsoft](https://todayfixtech.com/microsoft-365-tips-tricks/) 365 admin for testing. Proxy, firewall and VPN - Temporarily connect a device to a different network (home mobile hotspot) or disable VPN to test whether a corporate proxy or firewall is blocking requests. - Ensure the following general domains are reachable from the client: *`.sharepoint.com`,* `.office.com`, `*.microsoftonline.com`, and other Microsoft 365 endpoints your tenant uses. Conditional Access and security policies - Conditional Access policies can block web views, require compliant devices, or block legacy authentication. Ask your admin to check Conditional Access sign-in logs and any policies that apply to the user. IE/Edge legacy mode and SharePoint compatibility - If your organization uses IE mode in Edge or blocks modern authentication flows, embedded Lists may fail. Test in a fully modern browser session (non-IE mode) and, if that works, work with tenant admins to update compatibility settings. SharePoint tenant settings and Custom Script - Tenant-level restrictions like blocked custom scripts or site-level feature toggles can prevent certain list renderings. Admins should review SharePoint Admin Center settings for scripting and site features. How to test/temporarily bypass safely 1. Use a hotspot or home network to rule out VPN/proxy. 2. Have an admin temporarily exclude the user from a Conditional Access policy to test. Expected result: If Lists loads after a bypass, the responsible network or policy must be adjusted. If it still fails, collect logs for support. ## How to confirm Lists is fixed and what to collect if you escalate Quick verification steps 1. Open a known-working list and confirm items render and you can edit a list item. 2. Create a small test list (Title column only) and open it. 3. Open the same list from SharePoint site > Site contents > the list, and from the Lists app/Teams link if applicable. Expected result: Lists load with content visible, and basic actions (open item, create item) succeed. What to collect before escalating - Browser console output and network trace: ```text Open DevTools (F12) > Console tab (copy errors) Open DevTools > Network tab (reproduce and save HAR) ``` Settings path - Screenshot of the blank page or exact error text, including any correlation ID. - Teams logs (desktop): ```text %appdata%\Microsoft\Teams\logs.txt ``` Settings path - Time of the failure and the tenant name. What to send [to IT or Microsoft](https://todayfixtech.com/microsoft-365-for-beginners/) support - A short description of the problem, the steps you already tried, the exact time (with timezone), screenshots, browser console errors, the HAR file, Teams logs, and any correlation IDs. Expected result when escalated: IT or Microsoft support uses the correlation ID and logs to find server-side failures, inspect Conditional Access or tenant settings, and advise a fix or confirm a service incident. ## Conclusion If the quick fixes don’t work, collect the browser console output, a HAR file, any correlation IDs, Teams logs and the time of the failure, then contact your IT team or Microsoft support. Use a working browser, the Lists mobile app, or a different network as a temporary workaround while the issue is investigated. ## Frequently Asked Questions ### Why does Lists work in one browser but not another? Different browsers keep different cached data, have different extensions, and apply different cookie and privacy settings. If Lists opens in one browser but not another, clear cache and disable extensions in the failing browser, or use the working browser while you troubleshoot. ### What does a correlation ID mean on an error page? A correlation ID is a unique identifier for the failed request that your tenant admin or Microsoft support can use to locate server-side logs. Save that ID and the time of the error before contacting support. ### Can Conditional Access block Microsoft Lists but not other Office apps? Yes. Conditional Access rules can target specific applications, client types (browser, mobile, desktop), or platform conditions. A policy that blocks web-view contexts or requires device compliance can affect Lists embedded in Teams or a browser while leaving other apps accessible.