Power BI Microsoft Access integration for desktop databases
Power BI Microsoft Access integration brings the desktop databases that departments built over the years into shared reports. Microsoft documents an Access database connector that works in Import mode. It needs a database engine component on the machine, and scheduled refresh runs through a gateway. With those two points handled, an Access file becomes a dependable source instead of a private one.
- Access database connector
- Import mode
- Gateway for scheduled refresh
Last updated
How does Power BI Microsoft Access integration connect?
The author picks the Access database connector in Power BI Desktop and browses to the file. Then the navigator lists the tables and queries inside it. After that, Power Query loads the chosen ones into the semantic model.
One prerequisite trips people up. Microsoft's article says the machine needs the Access Database Engine provider, and its bit version must match Power BI Desktop. So a 64-bit Desktop needs the 64-bit provider.
The connector supports Import only, according to the same article. Power BI therefore copies the data at each refresh. Reports read that copy, so nobody locks the Access file while a colleague is typing in it.

Where should the Access file live?
Location decides whether scheduled refresh will work at all.
A server share
A stable network path suits refresh well. So the gateway account needs read rights on that folder.
Someone's laptop
Refresh fails whenever the laptop is off. Therefore we move the file before we build anything.
Split databases
Many Access apps keep forms in one file and tables in another. Then Power BI should point at the data file.
Linked tables
A linked table really lives in another system. However, it is often better to connect to that system directly.
Copies everywhere
Several versions of one file cause doubt. So we agree which copy is the master.
Backups
A single file is easy to lose. When reports depend on it, a backup routine matters more.
Should we keep Access or move the data?
Access is fine for a small team that enters data through forms. It struggles as users and rows grow. So the question comes up on almost every project.
Keeping it is reasonable when the file is stable and well kept. Power BI then adds shared reports on top, and the team changes nothing in its daily work. For example, a quality team may log inspections in Access and review trends in Power BI.
Moving makes sense when several people edit at once or the file keeps growing. In that case the tables can move to a server database while the Access forms stay as a front end. We explain both paths and let you decide, because the forms often hold years of know-how.
Pitfalls in a Power BI Microsoft Access integration
Most Access reporting problems come from this short list.
- Provider bit version that does not match
- No provider on the gateway machine
- A file path that only one person can reach
- Tables without keys or with duplicate rows
- Text fields holding dates and numbers
- Saved queries that hide business rules
Our steps for Power BI Microsoft Access integration
Four stages take an Access file from one desk to a shared report.
Inspect the database
First we open the file with its owner and learn the tables, queries and rules.
Settle location and access
Then we agree a server path and a gateway account, so refresh does not depend on one person.
Model the data
Next we load the tables, fix types and keys, and build measures in Power BI.
Schedule and hand over
Finally we schedule refresh, watch several runs and document the setup for your team.
Access databases in Power BI: questions owners ask
Does Power BI have a native Microsoft Access connector?
Yes. Microsoft's Power Query connector list includes an Access database connector, and its article marks it as generally available. The article lists Import as the supported capability. It also names a prerequisite, the Access Database Engine provider, whose bit version must match the Power BI Desktop version on the machine.
Does a Power BI Access database refresh need a gateway?
Yes, for scheduled refresh in the Power BI service. Microsoft's article says the online experience always needs an on-premises data gateway for this connector, with the 64-bit provider installed on the gateway machine. So the file must sit where that machine can read it, such as a server share.
Can Power BI use DirectQuery on a Microsoft Access file?
No. Microsoft's article lists Import only for the Access database connector. Power BI copies the data at refresh time, and reports read that copy. For most Access files this works well, since the data is small. When people need fresher figures, we schedule refresh more often.
Can Power BI read Access queries as well as tables?
The navigator shows the objects the file exposes, and saved queries usually appear beside the tables. However, a query can hide logic that nobody remembers. So we read each one with its owner first. Then we decide whether to load it or to rebuild the rule in Power BI where everyone can see it.
How do we talk to someone about our Access data?
Phone (480) 485-7373 or send a message. We reply within 2 hours and start with a free 30-minute assessment. Power BI Agency is a division of Sataware Technologies, a Microsoft Solutions Partner, and is not part of Microsoft. One of our consultants handles the work online.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.