What is Microsoft Dataverse? Pricing, capacity and Dataverse vs SharePoint or SQL
In short: Dataverse is Microsoft’s cloud data platform for business applications. Dynamics 365 Sales and Customer Service store their data in it, and Power Apps and Power Automate build on it. It works with tables, relationships, role-based security and server-side business logic. It has no price of its own: the use rights come with Power Apps or Dynamics 365 licences, and storage accrues to the tenant as database, file and log capacity.
What is Microsoft Dataverse?
According to Microsoft Learn, Dataverse lets you securely store and manage data used by business applications. Data is stored in tables: a table is a set of rows (formerly records) and columns (formerly fields). Dataverse includes a base set of standard tables for typical scenarios (account, contact, activity and so on), and you can create your own custom tables.
How does Dataverse relate to Dynamics 365 and the Power Platform?
The Dynamics 365 CRM apps (Sales, Customer Service, Field Service, Customer Insights – Journeys) store their data in Dataverse. So a Power Apps app or a Power Automate flow can work directly with Dynamics data without integration, under the same business rules and security. This is not automatic for the finance and operations apps, which need separate data integration.
In practice, a large part of a Dynamics 365 implementation is Dataverse work: tables and relationships, security roles, plug-ins, integrations. We cover the Web API and how to test it in API testing for Dynamics 365.
How does Dataverse capacity work?
Since 2019 Microsoft has split storage into three capacity types:
| Capacity type | Purpose | What counts (examples) |
|---|---|---|
| Database | table definitions and data | the rows in most tables |
| File | attachments, images, documents | note and e-mail attachments, file and image columns |
| Log | history of data changes, for auditing | audit log, plug-in trace log |
- Default capacity: the tenant receives a one-time default entitlement with its first Power Apps, Power Automate, Power Pages, Copilot Studio or selected Dynamics 365 subscription.
- Accrual per user: according to the Power Platform Licensing Guide (November 2026), each Power Apps Premium licence adds 250 MB of database and 2 GB of file capacity; the entitlements of Dynamics 365 licences are set out in the Dynamics 365 Licensing Guide.
- Add-ons: extra database, file and log capacity can be bought in 1 GB increments, or individual environments can be linked to pay-as-you-go billing.
How much does Dataverse cost?
You do not buy Dataverse on its own but through the licences built on it:
As a CSP reseller we supply these licences too: Microsoft 365 and Dynamics 365 licensing.
Dataverse vs SharePoint vs SQL: which one when?
| Criterion | SharePoint list | Dataverse | Azure SQL Database |
|---|---|---|---|
| Best for | simple lists and documents within Microsoft 365 | relational business data with business logic and fine-grained security | custom applications, large data volumes, full control |
| Relationships, logic | limited (lookup columns) | table relationships, business rules, plug-ins, flows | anything, but written in code |
| Security | site, list and item level | role-based, row-level and column-level security | database level, handled by the application |
| Dynamics 365 | no direct link | the same data layer | via integration |
| Licensing | included in Microsoft 365 | premium Power Apps or Dynamics 365 licence | Azure subscription, pay per use |
Our rule of thumb: if the data is a list or a document library and users already work in Microsoft 365, SharePoint is enough. If you need relationships between tables, row-level security, business rules or a link to Dynamics 365, choose Dataverse. For a custom-built application, very large data volumes or an analytical data warehouse, choose Azure SQL or a data platform.
The line is not sharp: a SharePoint list can move to Dataverse later, and Dataverse can surface SQL data through virtual tables. But decide early, because redesigning the security model and logic later is expensive.
What to watch out for in a Dataverse project
- API limits: Dataverse applies service protection limits (concurrent connections, requests and execution time within a five-minute sliding window), and the daily request entitlement per user depends on the licence. Plan for this in bulk loads and integrations.
- Backups: system backups of production environments with Dynamics 365 apps are kept for 28 days, sandbox backups for 7 days.
- Environments: separate development, test and production environments, with customisations packaged in solutions.
- Test data: a sandbox should not be a plain copy of production customer data, see test data management for Dynamics 365.
How we help
We design the data model and security, assess whether Dataverse, SharePoint or SQL fits the job, implement Dynamics 365 and Power Platform solutions and supply the licences from one source. Details: Dynamics 365 consulting.
Frequently asked questions
What is Microsoft Dataverse in simple terms?
Microsoft’s cloud database platform for business applications: tables, relationships, security and business logic in one place. Dynamics 365 and Power Apps are built on it.
Is Dataverse the same as the Common Data Service?
Yes. Microsoft renamed the Common Data Service to Dataverse; the terms changed as well: entities became tables, fields became columns, records became rows.
Do I need a separate Dataverse licence for Dynamics 365?
No. A Dynamics 365 Sales or Customer Service licence includes Dataverse use for the licensed app. A separate Power Apps licence is needed if you also run your own apps that are independent of the Dynamics app.
Is Dataverse included in Microsoft 365?
Only in a limited way: the Business plans include Dataverse for Teams and limited Power Apps rights. Standalone premium Dataverse apps need Power Apps Premium or a Dynamics 365 licence.
What happens when Dataverse storage runs out?
Microsoft notifies you and then restricts, depending on how long the overage lasts: first creating, copying and restoring environments, after 30 days access to sandboxes, after 90 days the sandboxes are disabled. The fix: clean up data, set retention or add capacity.
Let’s talk about your project.
Tell us what you are planning and we will get back to you within a few days.
Get in touch