Microsoft Lists vs SharePoint lists: what is the difference, and how do you govern them?

The direct answer

Microsoft Lists is the app; SharePoint lists are the lists inside sites; Microsoft states that both run on the same lists platform. The governance question is not which one to use but where each list is saved. A list in a SharePoint site belongs to that site, its owners and its sharing settings. A list in My lists sits in the creator's personal storage and follows their OneDrive sharing permissions. Most enterprises decide that shared business data lives in sites, and set the tenant controls to match.

One platform, three places a list can live

Sources: Microsoft Learn, Manage the Lists app in Microsoft Teams; Microsoft Support, Get started with lists in Teams and Share a list or list item (accessed 2026-11-07). Teams on mobile cannot create or pin lists yet, guests cannot create or delete lists, and administrators allow or block the Lists app in the Teams admin center under Teams apps, Manage apps (Microsoft Learn, accessed 2026-11-07).

What works the same in Microsoft Lists and SharePoint lists

• Templates. Microsoft Support names templates such as Issue tracker, Asset manager, Content scheduler, Employee onboarding, Event itinerary, Recruitment tracker and Travel requests; Microsoft Learn lists 18 template IDs administrators can switch off one by one.
• Rules. Set under Integrate, Rules, with triggers such as an item being modified; they notify people or a person column, not a group email address, and need Contribute permission.
• Views. List, Calendar and Gallery views, with List, Compact list or Tiles layouts; board view supports drag-and-drop reordering.
• Comments. Visible to anyone with access to the list unless an administrator turns them off; guests can read but not add them.
• Automation and audit. Power Automate flows and Power Apps list forms work on both, and list and item events appear in the Microsoft Purview audit log.

The governance controls that matter

1. Personal lists. Set-SPOTenant -DisablePersonalListCreation $true removes My lists from the save options, so users must choose a site; $false turns it back on (Microsoft Learn, Control settings for Microsoft Lists, accessed 2026-11-07).
2. Templates. Set-SPOTenant -DisableModernListTemplateIds removes a built-in template from the Lists app, Teams and SharePoint; EnableModernListTemplateIds restores it.
3. Comments. Set-SPOTenant -CommentsOnListItemsDisabled turns commenting on list items off or on.
4. Sharing. Only administrators set a site's external sharing, within the organization's limit; sharing a list needs manage permissions, which only site and list owners have by default (Microsoft Learn; Microsoft Support, accessed 2026-11-07).
5. Retention. Retention policies do not cover list items; retention labels do, except on system lists (Microsoft Learn, accessed 2026-11-07). Apply labels on lists that hold records.
6. Sensitivity labels. Labels protect the container (the team, group or site): privacy, external sharing and unmanaged-device access. Items do not inherit the container label (Microsoft Learn, accessed 2026-11-07).

Limits that shape list design

A list can hold up to 30 million items, but the list view threshold of about 5,000 items per database operation cannot be changed in SharePoint in Microsoft 365, so large lists need indexed columns (up to 20 per list) and filtered views. Microsoft supports 50,000 unique permissions per list and recommends no more than 5,000, and lists keep major versions only, 500 by default (Microsoft Learn, SharePoint limits; Microsoft Support, Manage large lists and libraries; How versioning works in lists and libraries, accessed 2026-11-07).

Changes to plan for

SharePoint alerts stop working by July 2026; Microsoft's pages differ on when new alert creation ended for every tenant (September 2025 in the SharePoint service description, January 2026 on the support retirement page), and both point to rules or Power Automate. SharePoint 2013 workflows were retired on April 2, 2026 with no extension (Microsoft Support, accessed 2026-11-07). Microsoft's InfoPath page states that support for InfoPath 2013 ended on July 14, 2026 and advises moving forms to supported Microsoft 365 solutions, which for list forms means Power Apps. See rebuilding workflows in Power Automate.

Where EPC Group helps

EPC Group writes the list governance standard with the client: where business lists live, which templates stay on, naming, retention labels for lists that hold records, and the move from alerts to rules and from InfoPath list forms to Power Apps. For the build steps see how to create a SharePoint site, list and document library; for list architecture at scale see the SharePoint lists enterprise guide.

Frequently Asked Questions

Talk to a senior architect

A one-hour call with a senior EPC Group architect covers where your business lists should live, which tenant controls to set, and how alerts and InfoPath forms move to rules, Power Automate and Power Apps. Email contact@epcgroup.net or call 888-381-9725.