SharePoint Lists vs Microsoft Lists

Microsoft offers half a dozen places to put structured data, and the choice has real consequences. The first decision is usually between SharePoint lists, Microsoft Lists, Dataverse, and a humble Excel file.

SharePoint lists

A SharePoint list is a structured list that lives inside a SharePoint site. It has columns (text, number, choice, date, person, lookup, taxonomy), views, formulas, and permissions tied to the site. SharePoint lists have existed since SharePoint 2001 and are the foundation of many internal apps.

Microsoft Lists

Microsoft Lists is a newer, friendlier surface on top of the same SharePoint lists engine. It's a separate app (lists.microsoft.com, Teams tab, mobile app) that focuses the experience on the list itself: templates, ready-made designs, conditional formatting, calendar view, gallery view. Lists you create in Microsoft Lists are still SharePoint lists — they just live in a specific site (usually your personal one) and benefit from the better UI.

When SharePoint lists are the right call

• Up to ~5,000 items per view (with indexing, up to the 30-million-item list limit).
• Data is naturally tied to a site or team.
• No transactional or relational requirements.
• Users will edit through the SharePoint or Microsoft Lists UI.

Typical fit: project trackers, inventory, request logs, asset registers, contact lists.

When you should pick Dataverse instead

Dataverse is Microsoft's relational database in the Power Platform. Reach for it when:

• You need real relational tables and referential integrity.
• You need row-level security and field-level security.
• You're building a serious model-driven Power App.
• You're storing data that drives Dynamics 365 or Copilot agents.
• Volumes or concurrency are beyond SharePoint's comfort zone.

Dataverse costs more (it requires premium Power Apps or Dynamics licensing), but it's a database. SharePoint lists are documents that happen to look like a database.

When Excel is fine

For ad-hoc data that one person owns, an Excel file in OneDrive co-authored by a small team often beats either option. It's faster to set up and easier to share. Reach for a list once you need permissions, views, automation triggers, or many editors.

The migration path

Start in Excel, graduate to a Microsoft List when you need shared views and permissions, graduate to Dataverse when you need a database. Skipping straight to Dataverse for "future flexibility" usually slows you down.