Dataverse explained
Dataverse is Microsoft's relational database for the Power Platform. Here's what it does and when you actually need it.
Microsoft Dataverse is the relational database behind the Power Platform and Dynamics 365. It's a managed database service, but it's also a lot more: it ships with a security model, audit trail, business rules, workflows, APIs, and integration with the broader Microsoft 365 stack.
What Dataverse provides
Beyond a database in the SQL sense, Dataverse includes:
- Relational tables with strong typing, lookups, choice fields, file/image columns, decimal/currency types, geography fields.
- Relationships — many-to-one, one-to-many, many-to-many — with referential integrity.
- Row-level security through Dataverse security roles with hierarchical and team-based scoping.
- Field-level security to hide specific columns from specific users.
- Business rules — visual logic that runs on form fields.
- Plug-ins — server-side .NET extensions that run on data events.
- Workflows and Power Automate triggers that fire on data changes.
- Audit log of every change to tracked tables.
- Microsoft Graph API access and REST/OData web APIs.
- Native Dynamics 365 compatibility — model-driven apps and Dynamics share Dataverse tables.
This is what "more than a database" means in practice: a row in a Dataverse table can have business rules, security, automation, and audit attached without any of that being external code.
Common tables
Dataverse comes pre-populated with standard tables for common entities: Account, Contact, Activity, Email, Task, User, Team. Custom tables extend the schema for your specific domain.
The standard tables matter because they're the lingua franca of the Power Platform ecosystem — many ISV solutions, Microsoft features, and connectors expect them.
Dataverse vs SharePoint lists
A common decision: should structured data go in Dataverse or SharePoint lists?
- SharePoint lists: free with Microsoft 365, simpler, fine up to about 5,000 active items per view, no relational integrity, weak transactional semantics.
- Dataverse: paid (premium Power Apps licensing), proper relational engine, role-based security, audit, performance at scale.
If the data set is small, owned by one team, and never going to feed Dynamics 365 — SharePoint is fine. If it's the system of record for a business process, has many tables, needs row-level security, or might grow into a Dynamics scenario — Dataverse.
Dataverse for Teams
A free, lightweight Dataverse instance is included with Microsoft 365 plans for apps inside Teams: when you create an app from a Teams team, you get a slim Dataverse environment scoped to that team. Capacity is limited (1 million rows or 2 GB per environment), connectors are restricted to standard, and the apps can't be promoted to full Dataverse without rebuilding.
Use it for quick wins inside Teams. Don't build the company's master CRM on it.
Licensing
Full Dataverse requires Power Apps premium licensing (per-user or per-app) for users of any app built on it. Dataverse capacity is licensed separately and consumed across the environment — database, file, and log storage.
For a serious business application, the cost is usually trivial compared to the value. Just don't accidentally build it expecting Dataverse to be free.