Microsoft Lists requirements and what you need to run it

Microsoft Lists is the modern list app built on SharePoint Online; users create, store and manage structured list data in SharePoint sites and access it from lists.microsoft.com, SharePoint pages, Teams and mobile apps. To enable Microsoft Lists for your users you must have SharePoint Online provisioned in the tenant and users must hold Microsoft 365 licenses that include SharePoint Online; additional Power Platform or premium connector scenarios require separate Power Automate or Power Apps licensing. This guide lists which subscriptions include Lists, supported clients and minimum expectations, tenant and SharePoint prerequisites admins must configure, common limitations, and a practical rollout checklist.

What exactly is Microsoft Lists and where it runs

Microsoft Lists is a user-facing UI for SharePoint lists that stores data in SharePoint Online. The app presents the same underlying SharePoint list data in three main experiences: the Lists web app, the modern SharePoint list UI, and a Lists tab inside Microsoft Teams. There is also a mobile Lists app for iOS and Android focused on viewing and light edits.

For example, say you create an inventory list in the Lists web app: the data is stored in a SharePoint list in a site the app creates or links to. You can add that list as a tab inside a Teams channel so team members see and edit the same items. The core list data is shared across web, SharePoint and Teams; available features (column formatting, flows, custom forms) depend on the client and licensing.

Boundaries — where Lists does not apply

• Classic SharePoint lists and classic web parts do not automatically gain modern Lists features. Classic customizations often require migration or rebuild to work in the modern UI.
• Lists relies on SharePoint Online storage; on-premises SharePoint Server does not provide the full Lists experience described here.

Common misconceptions

• "Lists is a separate database." It is not: Lists is a UI and feature layer on top of SharePoint lists. Data lives in SharePoint sites and follows SharePoint permissions and storage behavior.
• "Users need a separate Lists license." They do not; they need a Microsoft 365 license that includes SharePoint Online. Advanced Power Platform actions may need extra licensing.

Which Microsoft subscriptions and licenses include Microsoft Lists

Microsoft Lists is available wherever SharePoint Online is available. In typical commercial tenants Microsoft Lists functionality is included with these plans: Business Basic, Business Standard, Business Premium, Office 365 E1/E3/E5 and Microsoft 365 E3/E5.

Where Lists is not available or has limits

• Desktop-only Office subscriptions that lack SharePoint Online do not include Lists.
• Some education and government SKUs vary; check your tenant’s licensing documentation for those plans.

Licensing nuances to verify

• SharePoint Online dependency: a user must have SharePoint Online access to create, store or edit lists; lacking SharePoint Online in a user’s license prevents Lists usage.
• Power Platform features: using Power Automate flows or Power Apps with a list is possible, but flows that use premium connectors or Dataverse, or apps that require premium Power Apps capabilities, need the appropriate Power Platform or premium connector licenses.

For example, automating approvals that use a premium connector can require Power Automate premium licensing even though the list itself is available under the user’s Microsoft 365 plan.

Platform and browser requirements to use Lists reliably

Use modern, up-to-date clients to avoid partial or degraded behavior.

Supported clients and minimum expectations:

• Web: Recent versions of Microsoft Edge (Chromium) and Google Chrome are fully supported. Safari on macOS is supported for standard usage. Keep browsers updated to receive new Lists features and fixes.
• Teams: Lists works in the Teams desktop apps (Windows and macOS) and the Teams web app; keep the Teams client reasonably current to avoid UI and integration issues.
• Mobile: Lists mobile apps for iOS and Android support viewing and light editing; use currently supported OS versions from Apple and Google.

Not supported or limited

• Internet Explorer is not supported. The SharePoint classic UI lacks modern Lists features such as column formatting, rules, grid and board views; expect missing features and degraded behavior in classic pages.

Tenant, SharePoint and admin settings you must check before rollout

You must have SharePoint Online provisioned and the Lists service available at the tenant level. Confirm site provisioning policies, storage, and governance settings before allowing wide list creation.

Key items to verify and how to check them:

• SharePoint Online: ensure the tenant is provisioned and you can open the SharePoint admin center.

Microsoft 365 admin center > Admin centers > SharePoint > Settings

• Lists service switch: check SharePoint admin settings for any tenant-level switches that affect Lists availability and verify users can reach lists.microsoft.com.
• Site creation and provisioning: decide whether users can create sites or whether site creation is restricted; lists live in SharePoint sites so your site creation policy controls where lists appear.
• Tenant and per-site storage: confirm tenant storage and any per-site quota; very large lists consume storage and may need planning.
• Conditional Access, DLP and Compliance: review Conditional Access, Data Loss Prevention and other compliance policies to ensure they don’t unintentionally block list access, Power Automate flows, or external sharing you plan to allow.
• External sharing: confirm tenant and site-level external sharing settings if you plan to share lists with guests; guests need site-level access and the tenant must permit external sharing.

Quick verification checklist (run these checks now)

1. Are SharePoint Online and the SharePoint admin center accessible?
2. Is the Lists service enabled at tenant level and can users reach lists.microsoft.com?
3. Who can create sites and lists in your tenant (user roles and provisioning flow)?
4. Do Conditional Access and DLP policies permit intended list usage and Power Platform flows?
5. Is tenant storage sufficient for the expected list volume?

If you restrict site creation, prepare a site provisioning path or designate a group to host centrally managed lists.

Common limitations, gotchas and incompatibilities

Guest and external access

• Guests can edit list items only if the underlying SharePoint site allows external sharing and you grant edit permissions. Tenant external sharing settings and Conditional Access can still block or limit guest access. Test guest scenarios in your tenant before broad use.

Classic customizations and migration

• Classic SharePoint customizations, scripted web parts and classic forms typically won’t work in the modern Lists experience. If you rely on classic customizations, plan to migrate or rebuild them using supported modern approaches.

Large lists and lookup limits

• Very large lists and complex lookup columns can hit SharePoint list view thresholds and performance limits. Use indexed columns, filtered views, or alternative storage for large-scale scenarios.

Power Platform integration caveats

• Basic Power Automate flows and Power Apps forms work with Lists, but flows using premium connectors or Dataverse require extra licensing.
• A custom Power Apps form replaces the modern list form UI; reverting to the default form requires removing the custom form.

Other practical notes

• Column formatting using complex JSON can appear differently in Teams tabs versus the web app.
• Features sometimes roll out gradually; a tenant may not see a new feature immediately.
• Mobile apps provide fewer editing capabilities than the web app; design mobile-friendly views and actions when mobile access is required.

Quick readiness checklist and next steps for deployment

Use this checklist to verify readiness and run a controlled pilot before broad rollout.

1. Confirm licenses.

• Verify users who need Lists have Microsoft 365 plans that include SharePoint Online.

2. Verify tenant and SharePoint provisioning.

• Ensure SharePoint Online is provisioned and the SharePoint admin center is accessible.

3. Check service and sharing settings.

• Confirm Lists service is enabled and tenant/site external sharing settings match collaboration needs.

4. Review security and compliance policies.

• Validate Conditional Access, DLP and any sensitive info policies against intended list workflows.

5. Confirm browser and client policies.

• Ensure devices run supported browsers or Teams versions; update corporate browser policies if necessary.

6. Test a pilot list.

• Create a representative list, add sample column formatting and a simple Power Automate flow, test in web, Teams and mobile.

7. Train and document.

• Prepare a short how-to for users covering creating lists, adding a list to a Teams tab, and basic governance rules.

Don’t enable broad site creation or external sharing without a governance plan; unmanaged lists can create security and compliance overhead.

If a requirement is missing

1. Acquire or upgrade the needed licenses.
2. Enable SharePoint Online provisioning or adjust Conditional Access/DLP settings in a controlled pilot.
3. If classic customizations block features, plan a migration to modern lists or rebuild key elements with supported modern options.

Conclusion

Start by confirming SharePoint Online is provisioned and that the users who need Lists hold Microsoft 365 licenses that include SharePoint Online. Run the readiness checklist, create a pilot list, and test it from the web, Teams and mobile with representative users. Address any license gaps, blocked flows or storage limits before rolling Lists out broadly.

Frequently Asked Questions

Can external guests edit Lists items?

Yes, if the underlying SharePoint site allows external sharing and you grant the guest edit permissions. Tenant external sharing and Conditional Access policies can still block or limit access, so test the exact scenario in your tenant.

Do users need a separate Lists license?

No. Lists uses SharePoint Online licensing provided through Microsoft 365 plans. Users need a plan that includes SharePoint Online; advanced Power Platform actions may require separate Power Automate or Power Apps licensing.

Will classic SharePoint lists automatically become Lists (modern)?

No. Classic lists do not automatically convert in all cases. Many classic customizations—scripted web parts, custom forms—require migration or rework to function in the modern Lists UI.

How do I check if the Lists service is enabled for my tenant?

Open the SharePoint admin center and review tenant settings related to Lists and SharePoint services, then verify users can reach lists.microsoft.com. A simple test is to create a list and open it from the SharePoint UI and a Teams tab to confirm access.