Dataverse

Microsoft Dataverse is the managed relational database service that sits underneath the Power Platform and Dynamics 365. Beyond storing rows and columns, Dataverse provides relationships, business rules, plug-ins, security roles, field-level security, audit, workflows, and REST/OData APIs. Standard tables ship pre-populated (Account, Contact, Activity, Task) and form a common schema shared by Dynamics 365. Dataverse is licensed by capacity (database, file, log storage in GB) and by user (Power Apps premium licensing required for users of any app built on it). A lightweight free Dataverse for Teams is included with Microsoft 365 for apps built inside Teams.

Why it's more than "a database" in practice

A SharePoint list or an Excel table can hold rows and columns too, but Dataverse's value is in what sits above that storage layer: relationships between tables that enforce referential integrity (a Contact genuinely belongs to an Account, and deleting the Account can cascade or block depending on the relationship's configuration, rather than silently leaving an orphaned row), security roles with field-level granularity (a specific column, like a customer's credit limit, can be hidden from users who otherwise have full access to that record), business rules and plug-ins that enforce logic at the data layer itself regardless of which app or flow is writing to it, and a genuine audit trail of who changed what and when. A Power Apps canvas app built against a SharePoint list has none of this available natively — the app itself has to enforce any validation logic, and there's no shared enforcement if a second app or a Power Automate flow writes to the same list without going through the same rules.

Worked example

A company builds a Power Apps model-driven app for tracking equipment loans to employees, with an Equipment table related to an Employee table (each loan record must reference a valid employee and a valid equipment item) and a business rule preventing a loan record from being saved without a return-by date. Because this logic lives in Dataverse itself rather than only inside the one Power Apps front-end, a separate Power Automate flow that also writes loan records — say, triggered from a Teams approval process — is bound by the exact same relationship integrity and business rule, without needing to reimplement the validation logic a second time. If the company later builds a second, simpler canvas app for warehouse staff to check equipment in and out, that app inherits the same underlying data integrity automatically, because both apps are reading and writing the same governed tables rather than each maintaining a separate, potentially inconsistent copy of the data.

Dataverse for Teams — the free, scoped-down entry point

Dataverse for Teams ships at no extra cost with Microsoft 365 specifically for apps built and used inside a single Team, with capacity, row, and API-call limits well below full Dataverse, and no support for apps intended to be used outside that Team's context. It's a genuinely useful on-ramp for lightweight departmental apps that don't need enterprise-wide reach — but a team that outgrows a Dataverse for Teams app (more users, cross-team usage, integration needs) has to explicitly migrate the app to full Dataverse; it isn't a transparent scaling path, and that migration effort is worth anticipating rather than discovering at the point an app has already outgrown its limits.

Common pitfalls

Underestimating Dataverse's per-user premium licensing requirement is a common early surprise: any user who runs an app built on Dataverse (even one they didn't build themselves) needs a Power Apps premium licence unless covered by an existing Dynamics 365 or equivalent entitlement — a pilot that works fine with a handful of licensed builders can hit an unexpected licensing wall the moment it's rolled out more broadly to users who were never issued that licence.