Microsoft Lists compatibility: where it works & integrations

Microsoft Lists is the modern UI for SharePoint-backed lists that you use in SharePoint Online, the Lists web app, Teams tabs, and the Lists mobile apps. It works wherever the modern SharePoint list UI is supported, but browser versions, the host (SharePoint Online vs on-premises), licensing, conditional access and some column or customization types can limit features or block access.

What people mean when they ask about Microsoft Lists compatibility

Definition: Microsoft Lists is the modern presentation and app surface for SharePoint lists. The underlying data and permissions are SharePoint lists; "Lists" is both a standalone app in Microsoft 365 and a way to view and edit SharePoint list data.

For example: say a team asks for a List tab in Teams and mobile access. To deliver that you must create a SharePoint Online list (or use the Lists app), add it as a Teams tab or open it in the Lists mobile app, and confirm the users have appropriate Microsoft 365 licenses and are not blocked by tenant policies such as Conditional Access or external-sharing restrictions.

Boundaries: Microsoft Lists requires modern SharePoint capabilities. Classic SharePoint pages, older on-premise SharePoint Server versions, and unsupported browsers will not provide the full Lists experience. Some integrations and column types will degrade or be unavailable depending on host and configuration.

Misconceptions: "Lists" is not a separate storage engine — it uses SharePoint lists. Also, the existence of a Lists mobile app does not guarantee full feature parity with the browser; test the exact host and device you plan to support.

Will Microsoft Lists work in my browser and on my devices

Short answer: use modern browsers or the Lists mobile apps; do not use Internet Explorer 11 or out-of-date browsers.

Supported browsers and desktop

Microsoft documents that the modern Lists experience requires standards-compliant browsers. Use current versions of Microsoft Edge (Chromium-based), Google Chrome, Mozilla Firefox, or Safari. Internet Explorer 11 is not supported for the modern Lists UI and will be redirected to classic pages or fail.

There is no native desktop client for Lists on Windows or macOS beyond the browser-hosted experience and the embedded view inside the Teams desktop client.

Mobile apps

Microsoft provides Lists mobile apps for iOS and Android. The mobile apps do not always match the web UI: some column customizations, Power Apps custom forms and complex inline editing may be unavailable or behave differently. Lists added as a Teams tab are accessible from Teams mobile, but the Teams mobile view can be more limited than the native Lists mobile app.

Concrete examples

• If a user opens Lists in Chrome on a managed Windows laptop with current updates, the modern UI, inline column formatting and view formatting should work.
• If a user opens Lists in IE11 on an older workstation, they will not get the modern Lists experience and some actions will fail.
• If a user opens a list inside the Teams desktop client, they get an embedded SharePoint-backed experience; some customizations that rely on full browser capabilities or external pop-ups may not work in the Teams webview.

If you need precise minimum OS or browser release numbers for compliance records, check your tenant's admin portal and Microsoft's official platform support pages because browser support is updated regularly and references changed versions.

How Lists behaves inside SharePoint, Teams, Power Apps and Power Automate — what integrates and what’s limited

Lead point: Lists are SharePoint lists and inherit storage, permissions and many behaviors from SharePoint. The Lists app offers a focused UX, but each host imposes limits.

SharePoint Online

The modern Lists UI is the default for SharePoint Online lists. Column formatting, view formatting, rules and modern list settings are available. Classic SharePoint pages and classic lists won’t show the modern Lists UX and can break newer formatting or Power Apps forms.

Teams

You can add a list as a Teams channel or chat tab. The tab uses the SharePoint-backed list and displays the modern UI inside Teams. Teams tabs can limit complex customizations: Power Apps forms that require full-page rendering or SPFx web parts that need specific page contexts may not behave identically inside Teams.

Power Apps

You can customize list forms with Power Apps and use lists as data sources for canvas apps. Basic forms and simple customizations are supported, but some advanced column types (complex managed metadata configurations or certain custom site columns) may not be editable without extra configuration. Switching a list to use a Power Apps form can change the in-list editing experience.

Power Automate and connectors

Lists work as triggers and actions in Power Automate (when an item is created/modified, get items, update item). Some column types and complex lookups can cause differences: multi-value managed metadata, large person/group fields or complex lookup chains can complicate flow conditions and pagination. Connectors that access on-premises SharePoint require the On-Premises Data Gateway; without that gateway, flows cannot operate against on-prem lists.

Limitations to call out

• Column types: certain legacy or highly-customized column types may not be fully supported by all hosts (Power Apps, mobile). Lookup columns with many entries, complex calculated fields or old-style multi-line HTML fields can behave unpredictably.
• SPFx and customizations: SharePoint Framework solutions that rely on specific page contexts may require additional permissions or adjustments to work inside Teams or the Lists app.

Example: if you customize a list form with Power Apps and then add the same list as a Teams tab, users in Teams may see the Power Apps form but client-side behaviors such as browser pop-ups or unsupported script might not run in the Teams webview.

Licensing, tenant and sharing rules that prevent access even when the platform is supported

Lead point: supported client software is necessary but not sufficient — licensing and tenant policies often control access.

Licensing basics

• Microsoft Lists functionality is available with Microsoft 365 plans that include SharePoint Online. If a user lacks a license that includes SharePoint Online, they cannot create or edit lists.
• Guest users with permissions can access lists, but tenant sharing settings and guest access policies can block that.

Tenant and security policies that block usage

• Conditional Access and device compliance can prevent access from unmanaged or non-compliant devices even if the Lists app or browser is supported. If your tenant blocks legacy authentication or requires MFA and the client cannot honor that, access will fail.
• External sharing settings control whether lists can be shared with guests. If external sharing is disabled at the tenant or site level, guests cannot access lists even if invited.

On-premises and hybrid notes

SharePoint Server (on-premises) does not always have parity with SharePoint Online. Lists' modern features rely on SharePoint Online capabilities; if you keep data on an on-prem SharePoint farm without feature parity, some Lists features will not be available.

Checklist an admin can run to confirm a user's access

• Confirm the user has a Microsoft 365 license that includes SharePoint Online.
• Confirm site-level permissions allow that user to access the specific list.
• Check tenant external-sharing and guest access settings if the user is a guest.
• Check Conditional Access and compliance policies for device requirements or network restrictions.

Microsoft 365 admin center > Settings > Org settings > Services > SharePoint
SharePoint admin center > Policies > Sharing
Azure AD > Security > Conditional Access

Common gaps, gotchas and unsupported scenarios to watch for

Lead point: expect silent degradation in several areas — classic pages, on-prem servers, certain column types, large lists and legacy browsers.

Frequent pain points

• Classic SharePoint pages: lists on classic pages won't show the modern Lists UI and can break view formatting or new column types.
• On-prem SharePoint Server: SharePoint Server generally lags behind SharePoint Online. Features introduced in SharePoint Online that Lists relies on may not exist on-prem or may require a specific server version and updates.
• Legacy browsers: IE11 and very old browser versions will not support the modern UI. Users may be redirected or see an incomplete UI.
• Column type limits: large lookup columns, complex managed metadata, multi-value people fields and custom field types can behave inconsistently in Power Apps, Power Automate and mobile. Lookup columns with many items can cause performance problems or hit list view thresholds.
• Large lists and thresholds: very large lists can hit SharePoint list view thresholds and slower queries; some actions may time out or flows may need pagination and filter tuning.

Examples of silent degradation

• A view with JSON column formatting renders in the browser but not in the Teams tab version of the list.
• A Power Automate flow triggers on item creation, but a multi-value managed metadata column appears empty in the flow output because the connector flattened or transformed the data.

If you depend on specific behaviors from custom column types or heavy customizations, test them end-to-end in the exact host (Teams, mobile app, SharePoint site) because differences can be subtle.

How to test and verify compatibility in your environment quickly

Lead point: test the core scenarios that matter in the exact host and configuration your users will use. Use this checklist to find common problems quickly.

1. Create a sample list in SharePoint Online with representative columns and test items.

Title
Status (Choice)
AssignedTo (Person)
Category (Managed metadata)
RelatedItem (Lookup)
Notes (Multiple lines)

2. Open the list in a modern browser on a managed device and verify view rendering, column formatting and inline editing.
3. Add the same list as a Teams channel tab and test editing items from the Teams desktop and Teams web clients.
4. Install and open the Lists mobile app (iOS/Android) and try viewing and editing items; check which columns are editable and whether the custom form displays.
5. Create a simple Power Automate flow: trigger on item created, then send a test notification with key fields; verify the flow receives all expected values.
6. Customize the list form with Power Apps (a basic save/submit form) and test the form in browser, Teams and mobile to check parity.
7. If you have on-prem SharePoint or hybrid: try the same list scenario against the on-prem site (or a hybrid-aligned site) to see which features are unavailable.

Logs and settings to inspect if something fails

• ULS logs (SharePoint admin) when you suspect server-side errors (on-prem or hybrid).
• Azure AD sign-in logs and Conditional Access reports for authentication/authorization failures.
• Power Automate run history for failed flow runs and parsed outputs.
• Browser console for client-side errors when formatting or custom scripts fail.

Common quick fixes

• If a user can't access Lists in Teams: confirm the Teams client is updated and the user has site-level permissions to the underlying SharePoint list.
• If a Power Automate flow misses fields: re-check the connector outputs in run history and use the SharePoint Get item action to retrieve raw field values.
• If mobile editing is limited: try the native Lists mobile app instead of Teams mobile view, and verify device Conditional Access policies allow the app.

Reproduce the issue exactly as the user does (same client, same network, same tenant) — differences in host or Conditional Access context are often the root cause.

Conclusion

To roll out Microsoft Lists, store lists in SharePoint Online, require current browsers or the Lists mobile apps, and confirm users have the necessary Microsoft 365 licenses. Verify tenant policies — Conditional Access, external sharing and guest access — before wide deployment. Test every host your users will use (browser, Teams, mobile, Power Apps, Power Automate) with representative data and any complex column types you depend on. When something fails, check Conditional Access, sharing settings, run histories and logs before treating it as a product bug.

Frequently Asked Questions

Can I use Microsoft Lists with on-premises SharePoint Server?

You can create and use lists on SharePoint Server, but modern Lists features and some integrations rely on SharePoint Online capabilities. Expect functional gaps and test specific features; some scenarios require hybrid setups or the On-Premises Data Gateway for flows.

Will custom Power Apps forms always work inside Teams and the Lists mobile app?

No. Power Apps forms often work in Teams and on mobile, but they can lose behaviors that depend on a full browser environment or unsupported scripts. Test each customized form in the exact host to verify behavior.