Linking Access to SharePoint Lists: What Works and What Doesn\'t
Access can connect to SharePoint lists as linked tables. It sounds like an easy win — but there are real limitations. Here is what to expect before you commit.
Linking Access to SharePoint lists is one of those features that looks great in a demo and causes headaches in production. It is not useless — there are legitimate scenarios where it works well. But there are also real limitations that Microsoft does not advertise prominently.
This post covers how the integration works, where it performs well, where it falls apart, and how to decide whether it is the right path for your database.
How the Integration Works
Access can connect to SharePoint lists in two ways:
Linked tables — the SharePoint list appears as a table in Access. You can query it, build forms against it, and run reports. Data stays in SharePoint; Access reads and writes through the link.
Exported tables — you export an Access table to SharePoint, converting it to a SharePoint list. The original Access table can be replaced with a linked table pointing to the new list.
To link a SharePoint list:
- Go to External Data > New Data Source > From Online Services > SharePoint List
- Enter your SharePoint site URL
- Select the lists you want to link
- Choose whether to link (keep data in SharePoint) or import (copy data to Access)
Where It Works Well
Small lists with simple queries. If you have a lookup table — a list of product categories, status codes, or employee names — linking it to SharePoint works fine. The list is small, queries are simple, and the overhead of going through SharePoint is acceptable.
Replacing shared network drives. If your Access database currently uses a file-server backend and you want to move the data somewhere more accessible, SharePoint lists are a reasonable intermediate step. Users can access the data from a browser, and Access can still query it.
Simple data entry forms. A form that inserts or updates one record at a time against a SharePoint list will generally work. The latency is higher than a local table, but for occasional data entry it is tolerable.
Collaboration scenarios. SharePoint lists have built-in versioning, audit trails, and permissions. If those features matter for your data, linking to SharePoint gives you Access's form and report capabilities on top of SharePoint's governance features.
Where It Falls Apart
Complex queries. Access cannot push complex queries down to SharePoint. When you run a query against a linked SharePoint list, Access often has to download the entire list and filter locally. For a list with 50,000 rows, that means transferring 50,000 rows across the network every time the query runs.
Joins between SharePoint lists. Joining two linked SharePoint lists in Access is slow. Access downloads both lists in full, then performs the join locally. There is no server-side join optimization.
Aggregate queries. GROUP BY, COUNT, SUM — same problem. Access downloads the data, aggregates locally.
Large lists. SharePoint has a list view threshold of 5,000 items by default (configurable by admins, but often not changed). Queries that would return more than 5,000 rows may fail or return incomplete results.
Offline use. Linked SharePoint tables require a network connection. If your users work offline or on unreliable connections, linked tables will cause errors.
VBA and DAO. Some DAO operations that work against local tables do not work against linked SharePoint lists. If your VBA code uses dbOpenTable recordsets, bulk operations, or transactions, you may need to rewrite it.
Performance Expectations
Here is a rough guide to what you can expect:
| Scenario | Performance |
|---|---|
| Simple SELECT on a small list (<1,000 rows) | Acceptable |
| Simple INSERT/UPDATE on one record | Acceptable |
| SELECT with WHERE on an indexed column | Acceptable |
| SELECT on a large list (>10,000 rows) | Slow |
| JOIN between two SharePoint lists | Slow |
| Aggregate query (GROUP BY, SUM) | Slow |
| Bulk INSERT or UPDATE | Very slow |
If your database does a lot of the "slow" or "very slow" operations, linked SharePoint lists will frustrate your users.
The Sync Option
Access also offers a "Move to SharePoint" wizard that synchronizes data between Access and SharePoint. This creates a local cache of the SharePoint data that Access queries directly, syncing changes back to SharePoint periodically.
This improves read performance significantly — queries run against the local cache, not SharePoint. But it introduces sync complexity: conflicts when multiple users edit the same record, sync errors when the connection drops, and the overhead of managing the sync process.
For most teams, the sync model creates more problems than it solves.
When to Use It vs. When to Move On
Use linked SharePoint lists when:
- Your lists are small (under 5,000 rows)
- Queries are simple (no complex joins or aggregates)
- You need SharePoint's collaboration features (versioning, permissions, browser access)
- This is a temporary step toward a full Power Apps migration
Consider a different approach when:
- Your tables have more than 10,000 rows
- You rely on complex queries or joins
- Performance is already a concern in your current Access database
- Your VBA code uses advanced DAO operations
Move to Power Apps + Dataverse when:
- You want the full Microsoft 365 ecosystem (Teams integration, mobile apps, Power Automate flows)
- You need enterprise-grade performance and scalability
- You want to eliminate the Access dependency entirely
- Your team is already using Power Platform for other tools
The Honest Assessment
Linking Access to SharePoint is a useful bridge, not a destination. It can extend the life of an Access database by moving data to a more accessible location, but it does not solve the underlying limitations of Access as a platform.
If your goal is to modernize your database and give users a better experience, the SharePoint link is a stepping stone — not the final answer. The final answer is usually Power Apps with Dataverse, or SQL Server with a proper front-end.
The good news is that SharePoint lists can be migrated to Dataverse relatively easily, so if you do use the SharePoint link as an intermediate step, you are not creating a dead end.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Migrating Access tables to SharePoint Lists? Schedule a free call and get expert guidance on whether SharePoint Lists are the right destination for your data.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Power Platform
Migrating Access Reports to Power BI
Access reports are powerful but static. Power BI replaces them with interactive dashboards that refresh automatically. Here is how to make the transition without losing your reporting logic.
Building Your First Power App: A Guide for Access Developers
Power Apps looks nothing like Access at first. But the concepts map more closely than you might expect. Here is how to build your first canvas app if you already know Access.
Power Automate: Replacing Access VBA Automation
Much of the automation built into Access VBA — email notifications, file exports, scheduled tasks — can be rebuilt in Power Automate with less code and better reliability.