What is the difference between Dataverse and SharePoint lists?
By Emil Björk · Microsoft business apps consultant, Gothenburg
SharePoint lists are documents-with-columns — great for team-managed data with up to a few thousand rows and no complex relationships. Dataverse is a relational application platform with typed columns, referential integrity, row-level security, plugins, and a stable API. Use SharePoint lists for tracking; use Dataverse anywhere a real application would use a database.
The failure mode is building a proper business app on lists because they're free with the Microsoft 365 licence. It works — until the app needs to enforce that a Case must belong to a Contact, or that only a manager can see certain rows, or that a plugin recalculates a total when a line item changes. Lists do none of that; Dataverse does all of it.
The reverse mistake is provisioning Dataverse for a two-column tracker one team uses. That is exactly what a SharePoint list is for. The right question is 'is this data operational' (transactions, relationships, integrations) or 'is this data collaborative' (a running record a team updates). The answer picks the store.
Go deeper
- What is Microsoft Dataverse?Microsoft Dataverse is the relational data platform underneath Dynamics 365 CRM apps and Power Platform — what it is, why it's more than a database.
- Power Apps vs Dynamics 365 CRMPower Apps vs Dynamics 365 CRM: both run on Dataverse — when to buy the packaged Sales or Service app and when to build a custom model-driven app instead.
- Dataverse data model fundamentalsThe Dataverse data model — tables, columns, relationships, choices, security roles, and how it sits under Dynamics 365 and the Power Platform.