Microsoft Dataverse: The Database Behind Power Platform

If you have been exploring Microsoft Power Apps or Power Automate, you have probably encountered Dataverse — the cloud database that sits at the heart of the Power Platform. For Access developers, Dataverse represents both an opportunity and a significant shift in how you think about data storage.

What Is Dataverse?

Microsoft Dataverse (formerly Common Data Service) is a cloud-based data platform included with certain Microsoft 365 and Power Platform licenses. It stores data in tables (similar to Access tables) but adds a layer of business logic, security, and integration that goes far beyond what a file-based database can offer.

Key characteristics:

• Cloud-native — data lives in Microsoft's cloud, accessible from anywhere
• No file to manage — no .accdb file to back up, move, or share
• Built-in security — row-level security, column-level security, role-based access
• Integrated with Power Platform — Power Apps, Power Automate, and Power BI connect natively
• Standard tables — pre-built tables for common business entities (Account, Contact, Opportunity)
• Business rules — validation and automation logic stored in the database, not in the app

Dataverse vs. Access: The Key Differences

Feature	Microsoft Access	Dataverse
Storage	Local .accdb file	Microsoft cloud
Access method	File share / ODBC	API / connectors
Multi-user	Up to ~20 users	Unlimited
Mobile access	No (desktop only)	Yes (any device)
Offline	Yes	Limited
Built-in security	Basic (file-level)	Enterprise (row/column level)
Backup	Manual	Automatic (Microsoft managed)
Cost	Included with Office	Power Apps license required
Learning curve	Medium	High

Dataverse Tables

Dataverse tables are similar to Access tables but with important differences:

Standard columns — every Dataverse table automatically includes system columns: Created On, Created By, Modified On, Modified By, Owner, Status, and Status Reason. You cannot remove these.

Lookup columns — the Dataverse equivalent of a foreign key. A lookup column creates a relationship to another table and stores a reference to a specific row.

Choice columns — the equivalent of a lookup table for controlled vocabularies. Instead of a separate table, choices are defined directly on the column. Similar to a combo box with a value list.

File and Image columns — Dataverse has native support for storing files and images as column values, without the OLE Object limitations of Access.

Calculated and Rollup columns — similar to Access calculated fields, but defined at the table level and available everywhere the table is used.

Business Rules

One of Dataverse's most powerful features is business rules — logic defined at the table level that applies in every app that uses the table. Business rules can:

• Show or hide columns based on other values
• Set required/optional status dynamically
• Set default values
• Validate data and show error messages
• Lock columns based on conditions

This is similar to Access validation rules, but more powerful and applied consistently across all Power Apps that use the table.

When to Consider Dataverse

Dataverse makes sense when:

• You are building Power Apps that need to run on mobile devices
• You need enterprise-grade security with row-level permissions
• You want Microsoft to manage backups and infrastructure
• You are building multiple apps that share the same data
• You need to integrate with Dynamics 365

Dataverse is probably not the right choice when:

• You have complex reporting needs (Dataverse reporting is less mature than Access)
• You need offline-first functionality
• Your team is not ready for the learning curve
• You do not have Power Apps licenses

The Migration Path from Access to Dataverse

Migrating from Access to Dataverse is more involved than migrating to SQL Server:

1. Map your Access tables to Dataverse tables — standard tables may already exist for common entities (Account = Customer, Contact = Contact)
2. Export Access data to CSV and import into Dataverse using the Data Import Wizard
3. Rebuild forms as Power Apps canvas apps — there is no automated conversion
4. Rebuild reports in Power BI — Dataverse integrates natively with Power BI
5. Rebuild automation in Power Automate — replaces Access macros and VBA

This is a significant undertaking. Most organizations do it incrementally — migrating one process at a time rather than all at once.

Dataverse for Teams

If your organization uses Microsoft Teams, Dataverse for Teams is a lighter version of Dataverse built into Teams. It is free with Microsoft 365, has a simpler data model, and is a good starting point for teams new to the Power Platform.

Dataverse for Teams has lower limits than full Dataverse (1 million rows per environment, 2GB storage) but is sufficient for many departmental applications.

Conclusion

Dataverse is the long-term direction for Microsoft's business application platform. For Access developers, it represents a significant paradigm shift — from a local file to a cloud service, from VBA to Power Fx, from Access reports to Power BI. The migration is not trivial, but the result is a modern, scalable, mobile-accessible platform. Understanding Dataverse is essential for any Access developer planning their long-term roadmap.