Microsoft Lists cannot install — diagnose and fix quickly

If Microsoft Lists won’t install or never appears, the cause is usually one of four things: you tried the wrong app surface (web, Teams, Windows Store), your account or license doesn’t include SharePoint/Lists, a corrupted local cache or client, or a tenant/device policy blocks access. Start with quick, reversible user actions (sign out/in, private browser, cache clear), then check licenses and tenant service settings, and finally inspect Conditional Access/Intune or Store problems if needed. The steps below diagnose the exact symptom and resolve the issue from safest to riskier fixes.

What exactly is the error or symptom I see right now?

Identify the symptom so you target the correct layer: web (Microsoft 365 portal), Teams add-in, Office/Windows app, or back-end SharePoint provisioning.

If you have a specific error message copy it exactly or screenshot it with a timestamp.

(The exact message varies; capture it or use one of these examples)
"Lists doesn't appear in the app launcher"
"This item isn't available for your account"
"Lists add-in is missing in Teams"
"Creating this list failed"

When it appears

• Web: you open the Microsoft 365 app launcher and Lists is absent, or lists.office.com fails to load.
• Windows Store: the Microsoft Lists app shows an install error, fails to start, or the Store reports "This app isn't available for your device." Capture the Store error text and code.
• Teams: the Lists tab or Add button is missing or fails. Test both Teams desktop and Teams web to compare behavior.
• Provisioning (SharePoint/Lists web): creating a list stalls with a provisioning error or spinner. Copy any server-side error string or correlation ID.

What to capture

• Screenshot(s) of the app launcher, Store error page, Teams UI, or SharePoint provisioning error with timestamps.
• The user account (UPN) and tenant name.
• If possible, a browser HAR or the Teams logs (Help > Download logs).

If you don’t have an exact error string, note whether the symptom is "missing" (permission/portal UI) versus "install failed with code" (client or Store issue). That distinction determines whether to act as an end user or as an admin.

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

Product and versions this applies to

• Microsoft Lists (web at lists.office.com), the Lists add-in in Microsoft Teams (web and desktop), and the optional Microsoft Lists Windows Store app.

Privileges needed

• End user: no admin rights required for basic client checks (sign out/in, browser tests, wsreset, open lists.office.com).
• Admin tasks: Global Admin, Billing Admin, or a role that can view/assign licenses and service settings. Azure AD Global Administrator or Conditional Access policy owner to inspect Conditional Access. Intune Administrator to review device compliance.

Restart and backup

• No backup required for these troubleshooting steps. You may be asked to restart the device after updates or repairs.

Safe checks to run first (one or two quick tests)

1. Open lists.office.com in an incognito/private browser window.
2. Sign out of Microsoft 365 on the device and sign back in.

If either test works, the problem is client-side (cache, extension, or local app). If both fail, continue with the admin and policy checks below.

Is your account, license, or tenant blocking Lists?

Before changing clients or devices, confirm whether the user or tenant is blocking Lists. Common causes: missing license, SharePoint service disabled, guest accounts, or targeted release settings.

Checks for admins and users

1. Check the user's license assignment and service plan.

Microsoft 365 admin center > Users > Active users > select user > Licenses and apps

Expected result: the user has a Microsoft 365 license that includes SharePoint/Lists (for example, Business Standard, Business Premium, E3, E5) and the SharePoint service is checked.

What it means if that did not happen: assign the correct SKU or check the service box, then wait 10–30 minutes for propagation and retry.

2. Confirm SharePoint/Lists is enabled at tenant level.

Microsoft 365 admin center > Settings > Org settings > Services > SharePoint

Expected result: SharePoint service is enabled. If disabled, enable it and allow a short propagation window.

3. Check release preferences and user type.

Microsoft 365 admin center > Settings > Org settings > Release preferences

• Targeted release settings rarely block basic Lists availability, but custom rollout settings can delay specific features.
• If the user is a guest/external, external sharing settings or guest restrictions can stop Lists from appearing. Verify the user type under Active users.

What it means if checks fail

• Missing license or disabled SharePoint: assign or enable, wait for propagation, then try again.
• Guest account: adjust external sharing or provide a licensed internal account for full Lists access.

Quick fixes you should try first (no admin rights needed)

These end-user steps fix most client-side and browser issues. Do them in order and stop when Lists appears.

1. Sign out of Microsoft 365 everywhere the user tried (browser, Teams, Windows app) and sign back in.
2. Use a private/incognito browser window to rule out profile cache and extensions.
3. Clear the browser cache for Microsoft 365 domains or try a different browser.
4. Repair Office (Windows) if Lists is present in Office apps but won’t open.

Repair closes Office apps. Save work before you proceed.

1. Open Settings > Apps > Installed apps > Microsoft 365 Apps > Modify > Quick Repair.

Expected result: Office Quick Repair completes and Lists opens if Office-side corruption caused the problem. If Quick Repair fails, run Online Repair and retry.

5. Update Windows and Office.

• Windows Update:

Start-Process ms-settings:windowsupdate

Expected result: system updates install; reboot if prompted. If updates fail, note the Windows Update error codes.

• Office update from any Office app: File > Account > Update Options > Update Now.

Expected result: Office updates complete and missing components are restored.

6. Clear Microsoft Store cache for Store-app install issues.

wsreset.exe

Expected result: Store cache clears and you can reattempt the Lists app install. If the Store reports device incompatibility, check Windows edition and architecture.

7. If Lists is missing in Teams desktop but works in Teams web, reset the Teams cache or reinstall Teams.

• Collect Teams logs before reinstalling: Teams desktop > Help > Download logs.

If these steps don’t fix the issue, capture error messages and proceed to the admin-level checklist.

Admin-level fixes when users still can't install or open Lists

If user-side steps didn't work, inspect tenant services, policies, and device management layers.

1. Verify SharePoint and Lists service enabled at tenant level.

Microsoft 365 admin center > Settings > Org settings > Services > SharePoint

Expected result: SharePoint service is enabled. If not, enable it and inform users that changes can take minutes to propagate.

2. Confirm license and service plans for the user (re-check after assignment).

Microsoft 365 admin center > Users > Active users > select user > Licenses and apps

Expected result: the user’s license includes SharePoint and Lists and the service is checked.

3. Check Conditional Access and Intune policies that could block access or installations.

Azure AD portal > Security > Conditional Access

• Look for policies blocking unmanaged devices or requiring compliant devices for SharePoint or Office apps. If a policy blocks the affected user or group, temporarily exclude the user or adjust the policy.

Microsoft Endpoint Manager admin center > Devices > All devices

• Verify the device shows compliant. If not, inspect noncompliance reasons (OS version, missing baseline) and remediate.

4. Check Service Health and Message Center for tenant incidents or recent changes.

Microsoft 365 admin center > Health > Service health

Expected result: no active incidents affecting SharePoint/Lists. If an incident exists, follow Microsoft guidance and notify impacted users.

5. Re-provisioning and SharePoint profile issues.

# Connect to SharePoint Online (example; further steps depend on error)
Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

Expected result: administrative connection succeeds. Further re-provisioning steps depend on the provisioning error; collect correlation IDs before contacting Microsoft support.

What it means if admin checks fail

• Conditional Access blocks access: either change the policy or provide an exception for the user/group.
• Intune noncompliance: remediate device compliance or use an allowed device.
• License/service missing: assign or enable and retry after propagation.

If you change a policy, test with one user before applying tenant-wide.

How to verify the install succeeded and what to do if users still can’t access Lists

Confirm success from user and admin perspectives and collect artifacts if problems persist.

User-level checks

1. Open the Microsoft 365 app launcher and select Lists. The Lists web should open and show recent lists.
2. Go to lists.office.com; the page should load and allow creating a new list.
3. For the Windows app, launch the app and confirm the signed-in account shows the correct tenant and user.

Admin-level checks

1. Verify a SharePoint site was provisioned when a user created a list.

SharePoint admin center > Sites > Active sites

Expected result: a site or list container exists for the created list.

2. Check audit logs for sign-ins and list creation events.

Microsoft 365 compliance center > Audit > Search

Expected result: sign-in and list creation events for the user. If events are absent, the action didn't reach the service.

3. In Intune, confirm app install or reporting status if you pushed a Windows Store app.

Microsoft Endpoint Manager admin center > Apps > Windows apps > Monitor

Expected result: install status shows successful or failed with an error you can act on.

Simple verification tests

• Create a small list (one or two columns) and add an item. If creation succeeds and items are visible to other users with access, the service is working.
• Open the same list from Teams and from the Lists web to confirm cross-surface availability.

If verification fails, capture timestamps, user UPNs, error strings, correlation IDs, and relevant logs before escalating.

Common edge cases and what to escalate to Microsoft support

Edge cases that often need deeper investigation or Microsoft intervention:

• Tenant migrations or tenant-to-tenant moves with incomplete service propagation.
• Corrupted user profiles in Azure AD or SharePoint that block provisioning.
• Persistent Store or Teams cache corruption that ordinary resets don't fix.
• Third-party firewall, SSL inspection, or proxy appliances blocking Microsoft 365 endpoints used by Lists.
• Conditional Access policies that interact poorly with legacy auth or specific client behaviors.

What to collect before you open a support ticket

• Exact error messages and screenshots with timestamps.
• Affected user UPNs and tenant name.
• Time range when the issue started and steps already attempted (Office repair, wsreset, cache clears, license checks).
• Admin traces: Service Health snapshot, Conditional Access policy names/settings relevant to the user, Intune device compliance status, SharePoint site name and correlation ID if provisioning failed.
• Logs:
• Browser HAR or console logs for web errors.
• Teams diagnostic logs (Help > Download logs).
• Microsoft 365 audit search results showing attempted actions.

When to escalate

• You have a provisioning error with a correlation ID and the issue persists after tenant-level checks and policy validation.
• Multiple users are affected and Service Health shows no incident.
• License and service settings look correct but the service still rejects access.

Escalation note: include correlation IDs and timestamps; these are the fastest way for Microsoft support to locate server-side failures.

Conclusion

Fix the least invasive things first: client cache and browser tests, then licenses and tenant service settings, then Conditional Access/Intune and Store issues. Verify success by creating a simple list and checking SharePoint site and audit logs. If the problem persists with a correlation ID or multiple users affected, collect the artifacts listed above and open a Microsoft support ticket.

Frequently Asked Questions

Why does Lists show up in Teams web but not the desktop app?

The Teams desktop client keeps its own cache and can behave differently under local app policies. Test Lists in Teams web first. If web works but desktop does not: clear the Teams cache, sign out and back in, or reinstall Teams. Also check Conditional Access and Intune app protection policies for differences between desktop and web clients.

Can a missing Microsoft 365 license cause Lists install failure?

Yes. Lists depends on the SharePoint service in Microsoft 365. If a user’s license doesn’t include SharePoint or the SharePoint service is disabled for the tenant, Lists won’t appear. Confirm the SKU and that SharePoint is enabled in the admin center.

What if a user’s device is compliant but the Intune portal still blocks the Lists app?

Review the specific compliance policy evaluated (OS version, BitLocker, firewall). If the device reports compliant but app installs are blocked, check the app protection policy and its assignment scope. If you can’t find the conflict, collect device logs and contact support with the device ID and policy names.

Which Microsoft endpoints must be reachable for Lists to work?

Lists relies on SharePoint and Microsoft 365 endpoints. If a firewall or proxy blocks those services you’ll see provisioning or access failures. If you suspect blocking, capture a network trace and the blocked endpoint details before escalating.