Short answer: Yes. You can keep your Access forms, queries and reports and move the data into Microsoft Dataverse, linking the tables back into Access. It’s one of the most practical ways to modernize a mature Access application without rebuilding it from scratch, but it comes with licensing costs and some features that need rework.
Think of it like moving your filing cabinet to a secure cloud vault while your team keeps using the same desk. Access stays the front end your users know. Dataverse becomes the back end, with cloud storage, security and audit logging built in.
How Access Connects to Dataverse
Access connects to Dataverse through linked tables, the same way it connects to SQL Server or SharePoint. Once linked, Dataverse tables behave like any other table in Access: you can build queries on them, drive forms from them and run reports against them. The data itself lives in the cloud.
The connector is built into Access for Microsoft 365 and Access 2024. There’s nothing extra to install. There are two ways in:
- Migrate existing tables. Access’s Export to Dataverse wizard creates the tables in Dataverse, moves your data, and replaces the local tables with linked ones automatically. Microsoft walks through it in Migrate Access data to Dataverse.
- Link to tables that already exist. If Dataverse tables are already used by a Power App, go to External Data > New Data Source > From Online Services > From Dataverse, sign in, and pick the tables. See Microsoft’s guide to linking Dataverse tables.
Either way, you’ll need a Dataverse environment and the right licenses first, covered below.
Why Move Your Access Data to Dataverse
This approach fixes the most common Access pain points without rebuilding the application:
- No more 2 GB limit. Dataverse storage isn’t tied to a file on a network share. (See Slow over VPN and the 2 GB limit.)
- Fewer multi-user problems. Dataverse handles many simultaneous users at the data layer, so file-in-use and locking errors largely go away.
- No more corrupted .accdb back end. The data isn’t a single file that can be damaged or deleted.
- Mobile and automation ready. The same records are available to Power Apps and Power Automate, so you can add a mobile app or automated workflow later.
- Real security and audit trails. Permissions move from folder access to Dataverse’s role-based security, with change tracking on every record and no custom VBA.
Your users keep the Access screens they know. Your data gets an enterprise-grade home.
What It Costs: Licensing
This is the part most guides skip. Dataverse isn’t free with every Microsoft 365 plan.
- Power Apps Premium (per user) is generally what each Access user needs. Per-app licenses are tied to a specific Power App, so they don’t cover an Access-only setup.
- Dataverse for Teams is included with many Microsoft 365 plans, but it has much tighter storage and record limits and fits only small databases.
Licensing rules change, so confirm the right plan for your user count before you migrate. We include a licensing estimate in every Access to Power Platform assessment.
What Works and What Needs Rework
Most day-to-day use works well. The friction comes from Access features that assume a local database.
| Usually works | Often needs rework |
|---|---|
| Forms that view and edit records | Make-table and complex action queries |
| Select queries and reports | Some aggregate queries and Access-only SQL syntax |
| Simple inserts and updates | VBA that manipulates recordsets directly |
| Lookups between linked tables | Attachment and multi-value fields |
| Reports over very large tables, where network speed matters |
The more complex and VBA-heavy your application, the more testing it needs. If your code relies on local recordset tricks, a VBA review before migrating saves surprises later.
Wondering whether your database is a good fit? Book a free diagnostic and we’ll tell you what will move cleanly and what won’t.
The Honest Assessment: A Bridge, Not a Destination
Using Access as a front end on Dataverse is a legitimate, practical modernization step. It fixes your data problems now and extends the life of an application that works.
It isn’t the final stop. Access is still a Windows desktop app, and Microsoft’s long-term investment is in Power Apps (see Is Microsoft Access Being Replaced?). The smart way to think about it is as a bridge: modernize the data now, then rebuild the screens in Power Apps when time and budget allow. Because the data is already in Dataverse, that second phase is much simpler.
Which Path Is Right for You?
- Simple database, Power Apps licenses already in place: go straight to a Power Apps rebuild. It’s the cleaner path. See The Case for Power Apps.
- Complex database, no budget for a full rebuild yet: link Access to Dataverse now for immediate improvements, and rebuild later.
- You want to keep Access long term and avoid per-user licensing: SQL Server may be the better back end.
Not sure you’re ready to move at all? Start with How to Know When It’s Time to Migrate Off Microsoft Access.
Frequently Asked Questions
Can Access use Dataverse as a back end?
Yes. Access for Microsoft 365 and Access 2024 can link to Dataverse tables directly. Your forms, queries and reports keep working, while the data lives in the cloud.
Do I need a license to connect Access to Dataverse?
Yes. Users generally need a Power Apps Premium per-user license, or a Microsoft 365 plan that includes Dataverse for Teams for smaller databases. Confirm with your licensing provider before migrating.
Is Dataverse better than SQL Server for Access?
It depends. Dataverse is better if you plan to add Power Apps or Power Automate later. SQL Server is often better if you want to keep Access long term, need heavy reporting, or want to avoid per-user licensing.
Will my VBA code still work?
Most of it will. Code that works with forms and simple queries usually runs fine. Code that manipulates recordsets directly or relies on make-table queries often needs to be rewritten and tested.
Anthony Passeri, MBA, is the founder of Access Evolved and a certified Microsoft Access Expert with 21+ years of Access and relational database experience. He helps businesses keep critical Access databases running and modernize them to Power Platform or SQL Server. More about Anthony
Talk to an Access Expert
Not sure what this means for your database? Book a free diagnostic call. No sales pitch, just a straight conversation about what makes sense for your situation.
Phone: 623-267-5720
Email: info@accessevolved.com
Access Evolved | 19580 W Indian School Rd, Ste 105 #815, Buckeye, AZ 85396
