Microsoft

Microsoft Lists supported devices and where features differ

Md Sojib Mia

— 7 min read
Share

Microsoft Lists is a Microsoft 365 service for creating, sharing, and tracking structured lists (items, columns, views) across the web, Teams, SharePoint, and mobile apps. It runs wherever Microsoft 365 runs: the Lists web app in a browser, the Lists app inside Microsoft Teams, the native Lists mobile apps for iOS and Android, and as lists embedded in SharePoint sites. If a device can run a modern, up-to-date browser or the Teams/mobile apps and sign into your Microsoft 365 tenant, Lists will generally work; read on for exact OS/browser guidance, feature differences, installation steps, verification methods, browser settings, and common enterprise blockers.

Can I run Microsoft Lists on this device right now?

Microsoft Lists runs in four core places: the Lists web app (browser), the Lists app inside Microsoft Teams, the native Lists mobile apps for iOS and Android, and as lists or list web parts inside SharePoint sites.

  • Does the device run a currently supported desktop or mobile OS and receive updates? If yes, proceed.
  • Does the device have a modern browser (Edge, Chrome, Safari, Firefox) updated to a recent release? If yes, the web app should load.
  • Can the user sign into their Microsoft 365 account and access other Microsoft 365 services (Outlook, SharePoint)? If yes, authentication will likely work.
  • If the device uses Microsoft Teams as the primary client, can it run the Teams desktop or Teams mobile app (not just old embedded webviews or IE mode)? If yes, the Lists experience in Teams will be available.

For example, if a corporate laptop runs a recent Chrome and the user can open outlook.office.com and SharePoint, that machine is a good candidate for Lists in the browser. If the device only has an older browser locked down by IT, update the browser or use the Teams app on a supported device.

If a device is blocked from signing into Microsoft 365 by Conditional Access or lacks essential web platform features (cookies, IndexedDB), the Lists web app will fail even on a modern OS.

Which operating systems and browsers are supported

Microsoft Lists follows Microsoft 365 web app support: modern desktop and mobile OSes plus modern browsers.

  • Desktop OSes:
  • Windows 10/11 and recent macOS releases are supported for the web experience when the browser is up to date. Older, out-of-support OS builds may run the browser but can hit compatibility or security limits.
  • Mobile OSes:
  • iOS and Android are supported via the Lists mobile apps; the exact minimum OS version appears in the App Store and Play Store listings. If a device cannot install apps from those stores, use the web experience where possible.
  • Browsers (practical guidance):
  • Edge (Chromium-based): supported when up to date.
  • Google Chrome: supported when up to date.
  • Safari: supported on recent macOS and iOS; older Safari versions may lack needed web APIs.
  • Firefox: generally supported when current, but some enterprise features may work differently.
  • Internet Explorer 11:
  • Lists is not designed for IE11. The web app may be blocked or degrade significantly; if your environment forces IE11 or IE mode, provide an alternate modern browser or use the Teams desktop app.

Many Microsoft 365 web features follow a "current" and "one prior" major browser-version rule. For compliance or auditing, check your tenant's Microsoft 365 admin documentation or test with your target browser build.

How the experience differs between web, Teams, and mobile apps

The Lists data model (items, columns, views) is consistent across hosts, but capabilities and UI differ. The web app offers the most complete feature set; Teams and mobile apps are more focused.

Web app (lists.microsoft.com or SharePoint-hosted lists)

  • Full feature set: create custom columns, advanced column types (choice, person, lookup), conditional formatting authoring, multiple view types, JSON view and form customizations, saved filters, and Power Automate flow creation via the UI.
  • Attachments, drag-and-drop file support, and bulk editing are supported.

Teams host

  • Integrated context: Lists appear inside a team channel as a tab or through the Lists app in Teams.
  • Limitations: some advanced actions (full JSON formatting authoring, certain Power Automate creation flows, and some SharePoint list settings) require opening the list in the browser. Drag-and-drop file attachments may behave inconsistently depending on the Teams build.

Mobile apps (iOS and Android)

  • Focused feature set: viewing items, quick edits, creating items, scanning QR codes, and simple views. Conditional formatting is applied for display but complex JSON view or form editing is not available in-app.
  • Power Automate flows can trigger from mobile actions, but authoring flows is easiest on the web.

SharePoint pages

  • Lists embedded in SharePoint behave like the web app but inherit SharePoint site permissions and page-level web part behavior. Some list admin actions live in SharePoint list settings rather than the Lists app.

Concrete example: if you need to author a JSON view that highlights rows based on multiple column conditions, author it in the Lists web app. You can view the result in Teams or on mobile, but you can’t edit that JSON there.

Where features matter:

  • Authoring complex views and forms: use the web.
  • Creating flows and advanced automations: use the web.
  • Quick data entry and on-the-go edits: use mobile apps.

Common enterprise blockers and what to check on a managed device

Managed devices often have policies or network controls that break Lists. Check these common blockers and look for the signals listed.

  • Blocked cookies or restrictive cookie settings:
  • Problem: authentication or UI components fail.
  • Check: allow cookies temporarily or test with a browser profile that has default cookie settings.
  • Conditional Access policies (Intune/device compliance):
  • Problem: non-compliant or unmanaged devices are blocked from signing in.
  • Check: sign-in error messages often reference device compliance or Conditional Access; test with a compliant device and review Azure AD sign-in logs.
  • Disabled browser storage (IndexedDB, localStorage):
  • Problem: Lists uses browser storage for caching and state; disabling these breaks functionality.
  • Check: open the browser console and look for IndexedDB-related errors.
  • Legacy browsers or old webviews (EdgeHTML, old WebView controls):
  • Problem: missing modern web APIs; IE mode will not support Lists properly.
  • Check: confirm the rendering engine and avoid embedded legacy webviews.
  • Network proxies, content filters, or TLS interception:
  • Problem: blocking or rewriting requests to Microsoft 365 endpoints breaks authentication or API calls.
  • Check: compare network traffic from a working device to the managed device.
  • Teams app policies or app permission blocks:
  • Problem: Lists can be blocked inside Teams by admin policy.
  • Check: if the Lists tab is missing in Teams, review Teams admin center app permission policies.

Simple tests to identify the blocker:

  1. Open the browser's developer console and look for authentication errors or API call failures.
  2. Sign in to another Microsoft 365 web app (Outlook or SharePoint). If sign-in fails similarly, the issue is tenant or access-related.
  3. Try the Teams desktop app (if available). If Teams shows the list but the browser does not, the problem is browser-related.

Don't change Conditional Access or compliance settings without coordinating with identity and security teams.

How to install or open Microsoft Lists on each device

Follow these steps depending on the device and host.

Desktop browser (fast path)

  1. Open a supported browser and sign into the user's Microsoft 365 account.
  2. Navigate to the Lists web app via the Microsoft 365 app launcher or type lists.microsoft.com in the address bar.
Open browser
Sign in to Microsoft 365
Enter lists.microsoft.com
Expected steps

Teams desktop or web

  1. In Teams desktop, click "Apps" in the left rail and search for "Lists"; add it as a tab to a channel or to the left rail.
  2. In Teams web, use the same Apps search. If the app is missing, ask admins to allow it in the Teams admin center.

Mobile (iOS/Android)

  1. Open the App Store (iOS) or Play Store (Android).
  2. Search for "Microsoft Lists" and install the app.
  3. Sign in with the user's Microsoft 365 account.

SharePoint

  • Open the SharePoint site where the list lives and access the list from Site contents or from a page web part. To create a new list from a template, use the "New" menu on the site.

Verifying the running version

  • Browser: check the browser's About page to confirm it's up to date. Also check the user agent string via developer tools.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36
Example user agent (compare only)
  • Teams: open Teams > Help > About to see the client version.
  • Mobile app: check the app's settings or the App Store/Play Store listing for the installed version number.

If you cannot find the Lists app in Teams or the app store, verify that your tenant or Intune app protection policies allow the app.

Quick verification steps and next actions for admins

Use this short checklist to confirm device support and troubleshoot failures.

  1. Basic browser/OS check
  • Confirm the device OS and browser are up to date.
  1. Sign-in test
  • Open a browser and sign into another Microsoft 365 service (Outlook web or SharePoint). If sign-in fails, fix identity or network issues first.
  1. Open the Lists web app
  • Navigate to lists.microsoft.com. If it loads, try creating an item and editing a column.
  1. Developer console checks
  • Open Developer Tools and watch for network or JavaScript errors when loading Lists. Look specifically for authentication, CORS, or IndexedDB errors.
  1. Teams and mobile checks
  • If using Teams, confirm the Lists app is available under Apps and that the Teams client version is current. On mobile, open the Lists app and sign in.

If a check fails, next actions for admins

  • Update the browser or OS on the device. If the device is locked down, provide a managed browser that supports modern web APIs.
  • Review Conditional Access and Intune policies that may block non-compliant devices or browsers.
  • Allow cookies and IndexedDB for Microsoft 365 domains or add them to a trusted sites list in enterprise browsers.
  • If the Lists app is missing in Teams, adjust Teams app permission policies in the Teams admin center.
  • Collect logs: user agent, browser console output, and a screenshot of the sign-in or error message; escalate to Microsoft 365 support if tenant-side fixes don’t help.
[System.Net.WebRequest]::Create('https://lists.microsoft.com').GetResponse().Headers['User-Agent']
Collect user agent (PowerShell on Windows)

Conclusion

If a device runs a supported OS with an up-to-date browser or can run the Teams/mobile apps and sign into Microsoft 365, Lists will generally work. Start with the quick checklist: confirm sign-in, open `lists.microsoft.com`, and try a simple create/edit. If something fails, focus on browser features (cookies, IndexedDB), Conditional Access or Teams app permissions—those checks will show whether the problem is the device, the network, or tenant policies and point to the next steps.

Frequently Asked Questions

Can I use Microsoft Lists if my users are forced to use Internet Explorer or IE mode?

No. Lists expects modern browser APIs not present in Internet Explorer or IE mode. If your environment requires IE for legacy apps, provide a modern browser or use the Teams desktop app on supported clients instead.

Will lists work offline on mobile devices?

The mobile apps offer limited offline capabilities and local caching for recent content, but full offline authoring and sync scenarios are limited. For heavy offline needs, evaluate a solution that explicitly supports offline sync or test the mobile app for your scenario.

How do I confirm whether Conditional Access is blocking Lists?

Have a test user sign in and capture the error message when access is denied; the exact message varies but often references device compliance or policy. Check sign-in logs in Azure AD for the event and the policy name, then adjust or create an exception for compliant devices.

Read more