Microsoft Lists supported versions and where they work

Microsoft Lists is the modern list experience included with SharePoint Online and surfaced in the standalone Lists web app, Teams, and the Microsoft Lists mobile apps. If your Microsoft 365 subscription includes SharePoint Online, your users get Microsoft Lists; on-premises SharePoint (classic sites and older server releases) does not provide full Lists parity and will miss many features. This article shows which plans and SharePoint versions include Lists, which features require extra licenses, the supported clients and browsers, where Lists is not available or limited, and how to verify support for your tenant.

What exactly counts as “Microsoft Lists supported versions”

Microsoft Lists is the modern list service and user experience Microsoft ships as part of SharePoint Online and surfaces in several places: the Lists web app inside Microsoft 365, the Lists tab inside Teams, and the native Microsoft Lists mobile apps.

When administrators ask about “supported versions” they mean three things: which Microsoft subscription SKUs entitle users to the Lists experience; whether the SharePoint delivery channel is Online or on-premises; and which client software (browsers, Teams desktop/mobile, mobile OS) can access the experience.

For example: a user with Microsoft 365 Business Standard (which includes SharePoint Online) will see the Lists app in the Microsoft 365 app launcher and can create modern lists in SharePoint sites. By contrast, a user on an on-premises SharePoint Server deployment will not automatically receive the Lists web app or the latest list features unless those features were explicitly back-ported or a hybrid configuration is in place.

Why support varies: Microsoft develops Lists as part of SharePoint Online and ships new capabilities there first. Some features depend on cloud backend services or telemetry that aren’t present on-premises, so parity varies by delivery channel and by tenant rollout settings and admin controls.

Which Microsoft 365 plans and SharePoint versions include Microsoft Lists

Direct answer: Microsoft Lists is included with Microsoft 365 plans that include SharePoint Online. If your subscription provides SharePoint Online, users can use the Lists experience subject to tenant policies and any required additional licenses for connected services.

• Microsoft 365 business and enterprise plans that include SharePoint Online: these provide the Lists web app and modern lists in SharePoint sites. Feature behavior can still vary by tenant release ring and admin controls.
• Office perpetual (desktop-only) licenses: desktop Office apps alone do not include SharePoint Online and therefore do not provide the Lists web app or the modern Lists features by themselves.
• SharePoint Server (on-premises): classic on-premises releases (for example SharePoint Server 2019 and earlier) do not have full Microsoft Lists parity. Expect the classic list UX and only those modern list features that Microsoft explicitly back-ported via feature packs or cumulative updates. Subscription Edition of SharePoint Server may offer cloud-connected features depending on the release and hybrid configuration, but many cloud-only capabilities (for example some Power Automate connectors, Graph integrations, the Lists home UX) are only available in SharePoint Online.

For example: if you run SharePoint Server 2019, you should not expect the full Lists app or the Lists home UX in Microsoft 365; you will get the classic list experience and any modern elements Microsoft documented as back-ported.

If you need exact server builds or cumulative updates that add specific functionality, consult Microsoft’s SharePoint Server release and update documentation for the precise KBs and feature lists.

Where Lists works: browsers, desktop, Teams and mobile requirements

Lists is a web-first experience. That means supported browsers, the Teams client and supported mobile OS versions determine what users can do.

Browsers and desktop OS

• Supported browsers: current versions of Chromium-based Microsoft Edge, Google Chrome, Mozilla Firefox, and Safari are the typical supported browsers for Microsoft 365 web experiences. Feature behavior can vary between browsers; test critical scenarios (drag-and-drop, file previews, modern column renderings) on your supported browser set.
• Desktop OS: Lists runs in browsers and in the Teams desktop client. Supported desktop OS versions are those that can run an up-to-date browser or the supported Teams client (for example supported Windows 10/11 and supported macOS releases). If desktops run unsupported OS versions that cannot host a modern browser or Teams, users may lose functionality.

Teams integration

• Lists in Teams appears as a tab and uses the same underlying SharePoint list service. To use Lists inside Teams you need a Teams client version that supports custom tabs and adding SharePoint pages or lists as tabs. The Teams desktop client generally provides the fullest experience; the Teams web client follows browser support limitations.

Mobile apps

• Microsoft Lists mobile apps are available on iOS and Android and require a supported mobile OS version. Exact minimum OS versions change over time. If you manage devices with MDM, confirm allowed OS versions and that sign-in to Microsoft 365 is permitted.

Browser and client capabilities are updated regularly. If your organization enforces strict client version policies, test representative lists and rules in your allowed client versions before a broad rollout.

Where Microsoft Lists is not available or limited

Lists is not fully available or is limited in some environments and configurations.

• Classic SharePoint sites: classic sites remain on the classic list UX and will not automatically receive the modern Lists UX or its features. Upgrading the site or migrating content to a modern site is required to get modern Lists features.
• On-premises SharePoint Server: SharePoint Server 2019 and older do not provide full Lists parity. Some functionality has been back-ported in feature packs or updates, but many cloud-only capabilities (Flows/Power Automate integrations that depend on cloud connectors, Microsoft Graph features, the Lists home in Microsoft 365) require SharePoint Online.
• Feature-dependent limits: features that rely on Power Platform premium connectors, compliance integrations, or cloud telemetry may not work without the additional licenses or cloud services those features require.
• Tenant configuration limits: tenant admin policies, conditional access, blocked browsers, and targeted release settings can limit or delay which users see which features.

For example: if your tenant blocks access to the Microsoft Store or App Store and you rely on the Lists mobile app, users will need an alternative such as browser access or you’ll need to allow enterprise app deployment.

Common misconceptions and important feature limitations

Clarifications administrators commonly need.

• "Microsoft Lists is the same as classic SharePoint lists." No. Modern Lists features (new column types, conditional formatting, rules, the Lists home UX) are built for modern SharePoint sites; classic sites remain on the classic list UX until upgraded.
• "On-premises SharePoint equals Lists." Not automatically. On-premises servers generally lack parity with SharePoint Online; many features depend on cloud services and won’t be present unless Microsoft has explicitly back-ported them.
• "Any Microsoft 365 plan with SharePoint Online includes every Lists feature." Base Lists features are available with SharePoint Online, but advanced integrations (some Power Automate connectors, premium Power Apps features, advanced analytics or compliance integrations) can require additional Power Platform or premium licenses. Confirm connector and feature licensing in Power Platform documentation.

Examples that help planning:

• Conditional rules that trigger approvals using premium connectors may require extra Power Automate licensing beyond core Microsoft 365 entitlements.
• Tenant targeted release setting: users in targeted release can receive new Lists features earlier than users in standard release.
• Classic team sites: modern list templates and the Lists home won’t appear until you upgrade the site or migrate content to a modern site.

How to check your tenant and where to find authoritative, up-to-date support info

Use this checklist to verify what your tenant supports and to find authoritative updates.

1. Check which licenses are assigned to users.

Get-MsolUser -UserPrincipalName user@yourtenant.com | Select-Object DisplayName,Licenses

2. Verify SharePoint Online is enabled and view service health.

• Sign in to the Microsoft 365 admin center and open Service health. Look for SharePoint and related services (Teams, Power Automate) to confirm operational status.

3. Review the Message center for tenant notifications about Lists feature rollouts or changes.

• In the Microsoft 365 admin center go to Message center and filter for SharePoint or Lists-related messages. These messages show upcoming changes and whether a rollout is tenant-scoped or worldwide.

4. Confirm client and browser support across your environment.

• Inventory the browsers and OS versions in use and verify they can run the latest supported browser builds or the supported Teams client. If you need exact minimum versions, consult Microsoft Docs for current browser support for Microsoft 365.

5. Check SharePoint Server docs if you run on-premises.

• If you operate SharePoint Server, review the product’s release notes and update history to learn which modern features, if any, Microsoft back-ported to a cumulative update or feature pack.

Don’t assume feature parity based on product names. Always check the Message center and Microsoft Docs; feature availability can differ by tenant configuration and release rings.

Where authoritative information lives: Microsoft Docs for Lists and SharePoint, the Microsoft 365 Roadmap for upcoming items, the Message center for tenant-specific notices, and the Service health dashboard in the admin center for live issues. Use these sources rather than third-party summaries for exact license and feature requirements.

Conclusion

If your organization has Microsoft 365 with SharePoint Online, expect to provide Microsoft Lists to most users; if you rely on on-premises SharePoint or desktop-only Office licenses, expect gaps and plan for migration or hybrid configurations to get full Lists functionality. Start by auditing assigned licenses and client/browser versions, check Message center entries for your tenant, and test representative scenarios (classic vs modern sites, Teams tabs, mobile app flows) before a wide rollout.

Frequently Asked Questions

Does every Microsoft 365 license include Microsoft Lists?

Licenses that include SharePoint Online provide the Lists experience. Desktop-only Office perpetual licenses do not include SharePoint Online and therefore do not provide Microsoft Lists by themselves.

Will Lists work in classic SharePoint sites?

Classic sites remain on the classic list UX and will not automatically receive the modern Lists UX or its features. To use modern Lists features you must upgrade the site or migrate content to a modern SharePoint site.

Can I use Lists with Power Automate and Power Apps without extra licensing?

Basic Power Automate and Power Apps functionality included with Microsoft 365 can work with Lists. However, some connectors, premium flows, or advanced Power Platform features require additional licensing. Confirm connector and feature licensing in Microsoft’s Power Platform documentation.