Microsoft Lists install problem: fix installation and startup

If Microsoft Lists fails to install or doesn’t appear, the cause is usually either a local client/browser issue or a tenant/admin policy blocking the app. Try quick, low-risk fixes first (confirm account, use lists.microsoft.com, clear cache, update Teams/Windows) and escalate to admin checks only if device fixes fail. The sections below show how to capture the symptom, run step-by-step fixes from least to most invasive, confirm whether the problem is tenant-wide, collect logs for escalation, and verify the app is working.

What exact symptom or error are you seeing right now

Start by capturing the exact symptom because different messages point to different causes. Copy the full error text and take a screenshot of the install dialog or Teams app store entry before you change anything.

Example: "App not available for your account"
Example: "Installation failed"
Example: "You don't have permission to install this app"
Example: Blank install button or Lists not appearing in Teams app bar

When it appears:

1. Note whether the error appears in a browser, the Teams desktop client, or the Windows Microsoft Lists app.
2. If it’s a browser error, check the page URL (lists.microsoft.com or teams.microsoft.com) and whether you’re signed in to the correct account.
3. If it’s in Teams, note whether the client is desktop or web, and whether other users in your team see the app.

What these common messages usually mean:

• "App not available for your account": tenant or license restriction, or an admin policy blocking the app.
• "Installation failed": local client or network issue (cache, corrupted client), or transient service problem.
• Permission or tenant blocking messages: Teams app permission policy, Conditional Access, or other tenant policy.
• Blank install / app missing: client cache or the app not published to your tenant or policy.

If the symptom is a silent failure (no error), treat it like a local cache or client state problem first and collect browser/Teams logs if you must escalate.

Is Microsoft Lists supposed to be available for you and your tenant

Applicability and privileges:

• Product/versions: Lists in Microsoft 365 (web lists.microsoft.com), the Teams app (desktop and web), and the Windows Lists app.
• Privileges: You need a global/admin or delegated admin to change tenant settings. Device checks below do not require admin rights.
• Restart/backup: No backup required for the checks below. Some steps sign you out or restart apps.

Quick checks to do first (no admin required):

• Confirm your license includes Lists (most Microsoft 365 business and enterprise plans include it).
• Confirm you’re signed in with the correct account (UPN shown in the app). Use Edge or Chrome for lists.microsoft.com.

How to check tenant settings (ask an admin if you are not admin):

1. Admins: open the Microsoft 365 admin center or Teams admin center.

Microsoft 365 admin center > Settings > Org settings > Services
Teams admin center > Teams apps > Manage apps
Teams admin center > Teams apps > Permission policies

2. In Teams admin center, check "Manage apps" to confirm Microsoft Lists (or the app name that contains "Lists by Microsoft") is allowed.
3. In "Permission policies," confirm there is no global block on Microsoft-published apps that would include Lists.

If an admin confirms the app is blocked by policy, ask them to allow the specific app or assign an app setup policy that includes Lists to your user or group.

Connect-MicrosoftTeams
Get-CsTeamsAppPermissionPolicy
Get-CsTeamsAppSetupPolicy
Get-CsAdminPowerAppEnvironment

Tenant policies and licensing are the most common reason an app is "not available" even when installation should otherwise work.

Quick fixes that usually resolve install problems (try in this order)

Try these low-risk steps first. Do them in order from least to most invasive.

1. Confirm browser and sign-in

• Where to act: Browser or Teams client.
• Privilege: End user.

1. Ensure you’re signed into the correct Microsoft account in the browser or Teams client.
2. Use a supported browser: Edge or Chrome are recommended for lists.microsoft.com.

Expected result: You can sign in and access lists.microsoft.com. If not, the account or browser is blocking access.

2. Open Lists on the web to bypass client issues

• Where to act: Browser.
• Privilege: End user.

1. Go to lists.microsoft.com and sign in with the same account.
2. Try to open or create a list.

Expected result: If this works, the issue is client-specific (Teams or Windows app). If it fails, proceed with browser checks.

3. Clear browser cache and try an incognito/private window

• Where to act: Browser.
• Privilege: End user.

1. Open a private/incognito window and sign in to lists.microsoft.com.
2. If that works, clear browser cache and cookies for Microsoft 365 sites.

Browser > Settings > Privacy & security > Clear browsing data

Expected result: The site loads and you can sign in. If not, the browser or network may be blocking scripts or cookies.

4. Clear Teams desktop client cache

• Where to act: Teams desktop client, local file system.
• Privilege: End user.

This will sign you out of the Teams desktop client and close the client.

1. Quit Teams completely.
2. Delete cache files.

%appdata%\Microsoft\Teams\Cache
%appdata%\Microsoft\Teams\blob_storage
%appdata%\Microsoft\Teams\databases

3. Restart Teams and sign in.

Expected result: Teams reloads app catalog and the Lists app should appear. If it does not, caching was not the only issue.

5. Update Office, Teams, and Windows

• Where to act: Teams client, Office apps, Windows Update.
• Privilege: End user; admin may be required in managed environments.

1. Update Teams: open Teams > Help > Check for updates.
2. Update Office: open any Office app > Account > Update Options > Update Now.
3. Update Windows: Settings > Update & Security > Windows Update.

Expected result: New client versions often resolve install or runtime errors. If updates don’t fix it, continue.

6. Reinstall Teams desktop client

• Where to act: Local machine.
• Privilege: End user; admin rights may be required to uninstall in some environments.

Reinstall will remove local client configuration and sign you out.

1. Sign out and uninstall Teams via Settings > Apps.
2. Reinstall the latest Teams from Microsoft and sign in.

Expected result: A fresh client removes corrupt installs. If reinstall fails, collect install logs before escalating.

If the quick fixes don’t work — account, policy and deeper troubleshooting

When device fixes don’t help, the issue is often tenant-level controls, Conditional Access, or service health.

1. Check service health

• Where to act: Microsoft 365 admin center.
• Privilege: Admin.

1. Open Microsoft 365 admin center > Health > Service health and look for Lists or Teams-related incidents.

Expected result: If there is a service incident, wait for Microsoft to resolve it. If no incident, continue.

2. Check Azure AD sign-in logs (admin required)

• Where to act: Azure AD portal.
• Privilege: Admin.

1. Go to Azure AD > Sign-ins and filter by the user and time to see failed sign-in errors or Conditional Access blocks.

Expected result: Logs show any Conditional Access or sign-in errors. If blocked, note the policy name and error code.

3. Check Teams app permission and setup policies (admin required)

• Where to act: Teams admin center or PowerShell.
• Privilege: Admin.

1. In Teams admin center, confirm the Lists app is not blocked under "Manage apps." Confirm the user’s app setup policy assigns or allows Lists.

Connect-MicrosoftTeams
Get-CsTeamsAppPermissionPolicy | Format-Table Identity,Description
Get-CsTeamsAppSetupPolicy -Identity "Global" | fl

Expected result: The policies show whether Lists is allowed. If a deny rule exists, an admin must change that policy or assign a different policy.

4. Conditional Access and compliance policies

• Where to act: Azure AD Conditional Access, Intune app protection.
• Privilege: Admin.
• Admins should check Conditional Access policies and Intune app protection policies that might prevent the app from loading or installing.

Expected result: If a Conditional Access policy blocks the client or browser, modify the policy or create an exception for the Lists app for the affected users.

5. Tenant app publishing

• Where to act: Teams admin center.
• Privilege: Admin.
• If the tenant uses app catalog restrictions, Lists might not be published to your tenant. Admins should check Teams admin center > Teams apps > Manage apps and search for the Lists app.

What to ask your admin to change

• Allow the Lists app in Teams admin center Manage apps.
• Assign an app setup policy that includes Lists to the affected user or group.
• Adjust Conditional Access policies that block the client or browser.

What to collect if logs look suspicious: app ID, timestamp, error code from Azure AD or Teams, and the policy name that triggered the block.

How to verify Microsoft Lists is installed and working after fixes

Confirm success with these concrete checks and collect evidence for closure.

1. Open Lists on the web

• Where to act: Browser.
• Privilege: End user.

1. Go to lists.microsoft.com and sign in.
2. Create a simple list and add one item.

List creates successfully and the new item appears.

Expected result: List saves without errors and the item appears. If not, capture the error text and console logs.

2. Verify in Teams

• Where to act: Teams client.
• Privilege: End user.

1. Add a Lists tab to a team channel: Teams > channel > + > Lists.
2. Create a list or open an existing one and add an item.

Expected result: The tab loads, the list is editable, and new items are saved.

3. Verify the Windows Lists app (if used)

• Where to act: Windows app.
• Privilege: End user.

1. Launch the app and sign in.
2. Open a list and create an item.

Expected result: App launches and synchronizes lists.

4. Check logs and console if issues persist

• Where to act: Browser dev tools or Teams client logs.
• Privilege: End user.
• In a browser, open DevTools (F12) Console and note any network or script errors while loading lists.microsoft.com.
• In Teams, collect client logs: Help > Download logs.

What success looks like to include in a ticket: screenshots of the created list and list item, time-stamped evidence of successful sign-in, and the absence of errors in the console or sign-in logs.

Quick prevention checklist and what to include if you need to escalate to support

Prevention checklist

• Keep Teams, Office, and Windows updated.
• Use a supported browser for lists.microsoft.com (Edge or Chrome recommended).
• If you’re an admin, allow the Lists app in Teams admin center and include it in the appropriate app setup policies.
• Avoid aggressive cookie or script blockers on sites used for Microsoft 365.

When you escalate to IT or Microsoft support, include this minimal troubleshooting packet:

• Exact error text and a screenshot.
• Where the error occurred (browser name/version, Teams desktop or web, Windows app) and the account UPN.
• Tenant ID and user UPN (an admin can find the tenant ID in Azure AD > Properties).
• Time and date (with timezone) when the issue happened.
• Steps you already tried (opened lists.microsoft.com, cleared cache, reinstalled Teams, etc.).
• Browser console log or Teams client logs if available.

Azure AD > Overview > Tenant ID

Providing exact timestamps, screenshots, and the tenant ID shortens resolution time because admins or Microsoft support can correlate your attempts with service logs.

Conclusion

If device fixes resolve the problem, capture a screenshot of a working list and close the ticket. If the problem is tenant-level, hand the troubleshooting packet above to your admin or Microsoft support so they can check permission policies, Conditional Access, and service health.

Frequently Asked Questions

Why does Lists work in the browser but not in Teams?

If Lists works in the browser but not in Teams, the Teams client is the likely cause: cached app metadata, an outdated client, or a Teams app permission/setup policy that prevents the app from appearing. Clear Teams cache, update or reinstall the client, and ask an admin to confirm Teams app permission and setup policies.

What error info should I capture for my admin?

Capture the full error text, a screenshot, the account UPN, tenant ID, timestamp, whether the error was in browser or Teams, and the steps you already tried (cache cleared, reinstall). If possible, include browser console output or downloaded Teams logs.

Can licensing prevent installation of Microsoft Lists?

Yes. If your license does not include Microsoft 365 services that provide Lists, or if your tenant restricts the app to certain licenses or groups, you may see "app not available" or permission errors. Ask your admin to verify licensing and app availability.