Dataverse is Microsoft’s cloud-based data platform that sits at the heart of the Power Platform ecosystem. Think of it as a proper enterprise database — hosted in Azure, managed by Microsoft, and deeply integrated with Power Apps, Power Automate, Power BI, and Microsoft 365 — without requiring your organization to provision, maintain, or secure a database server of its own.
The simplest way to understand it: if Power Apps is the application layer, Dataverse is where the data lives.
How it’s structured
Dataverse organizes data into tables (what traditional databases call tables or what older Microsoft documentation called entities). Each table has columns with defined data types, and tables relate to each other through relationships — one-to-many, many-to-many — just like a relational database. If you know how to think in terms of relational data, Dataverse will feel familiar. If you’re coming from Access, the concepts map almost directly.
What makes Dataverse different from a plain relational database is that it comes with a layer of built-in metadata, business logic, and security baked into the data layer itself — not bolted onto the application sitting on top of it.
What it includes out of the box
Several capabilities that require significant custom development in traditional databases come standard in Dataverse.
Role-based security is built into the data layer. You define security roles that control which users can create, read, update, or delete records — and you can scope those permissions down to the individual record level if needed. A user can be allowed to see their own records but not anyone else’s, all within the same table, without any application-level logic to enforce it.
Audit logging tracks who created, modified, or deleted every record and when. In regulated environments — financial services, healthcare, legal — this is often a compliance requirement. In Access you’d have to build this yourself. In Dataverse it’s a configuration toggle.
Business rules let you define validation logic, field requirements, and conditional behavior at the table level rather than inside each individual app. A business rule that makes a field required when another field has a certain value applies in every Power App, every API call, and every integration that touches that table — not just in the form where you remembered to add the validation.
Calculated and rollup columns let you define fields whose values are derived automatically — a total that sums child records, a status field that updates based on related data — without writing code in every place that data is displayed.
Standard and custom tables. Dataverse ships with hundreds of pre-built standard tables covering common business concepts — Account, Contact, Opportunity, Task, Invoice, and many more. You can use these as-is, extend them with custom columns, or create entirely custom tables for concepts specific to your business. The standard tables also connect directly to Dynamics 365 if your organization uses it.
How it relates to Power Apps
When you build a model-driven app in Power Apps, Dataverse is not optional — it is the required data source. The app is essentially a configured view of Dataverse tables, with the security, forms, and views inheriting directly from the table definitions. When you build a canvas app, Dataverse is one data source option among many, but it’s the most capable and the most deeply integrated. Connecting a canvas app to Dataverse gives you access to offline capability, delegable queries against large datasets, and the full security model without additional configuration.
How it compares to alternatives
Versus SharePoint lists: SharePoint lists are fine for simple, low-volume data with basic structure. They lack proper relational capability, have a list view threshold that limits query performance, and offer no row-level security model. Dataverse handles all of these properly. For anything beyond simple list management, Dataverse is the better choice.
Versus SQL Server: SQL Server is more flexible for complex queries, stored procedures, and high-volume transactional workloads. Dataverse abstracts away the database administration entirely — no server to manage, no backups to schedule, no indexes to tune manually — but that abstraction comes with less raw query flexibility. For most business applications, Dataverse’s capabilities are more than sufficient and the reduced operational overhead is a significant advantage.
Versus Microsoft Access: Access is a local or network-hosted file with no built-in security model, limited concurrent user support, and no cloud access. Dataverse is a cloud-hosted enterprise platform with role-based security, full audit capability, and access from any device. The two serve similar conceptual purposes — structured business data storage — but Dataverse operates at a fundamentally different level of capability and scale.
Licensing
Dataverse is not included in base Microsoft 365 subscriptions the way SharePoint is. It requires Power Apps licensing — either a per-user plan or per-app plan — or is included with Dynamics 365 licenses. There is a limited Dataverse for Teams offering that comes with Microsoft Teams licenses, but it has storage and capability restrictions compared to the full platform. Licensing is one of the genuine friction points in Dataverse adoption, particularly for smaller organizations, and it’s worth mapping out the cost before designing an application around it.
When Dataverse is the right choice
Dataverse makes sense when your application needs proper row-level security, when multiple Power Apps need to share a common data layer, when you need audit trails for compliance, when you’re building something that may eventually connect to Dynamics 365, or when the data complexity has outgrown what SharePoint lists can handle cleanly.
It is overkill for simple, low-stakes applications where SharePoint lists would do the job, and it introduces licensing cost that has to be weighed against the benefit. But for serious business applications — the kind that used to be built in Access and are now being modernized — Dataverse is typically the right foundation.
Ready to talk through your options? Reach out to Anthony at AccessEvolved — email anthony@accessevolved.com or call 212-951-1010. No sales pitch, just a straight conversation about what makes sense for your situation.