Expert guide
Does Copilot Work with Microsoft Access?
What Microsoft's AI can and cannot do for Access users today, and what to use instead
Call us at +1 (385) 386-3860
Short answer: not directly. At the time of writing Access has no built-in Copilot pane, so Copilot cannot read your tables or forms from inside Access. What works: Copilot Chat (or any AI assistant) to write Access SQL and VBA from a schema you describe, Copilot in Excel on Access data exported or linked through Power Query, and dedicated tools such as DatabaseAI that answer plain-English questions directly against the Access file.
When businesses buy Microsoft 365 Copilot licences, Access users are often the first to be disappointed. Excel gets a Copilot button; Word and Outlook get one; Access does not. Given how many operations, inventory and billing systems still run on Access, this is a real gap. The good news is that most of what people want Copilot to do for Access can be done another way.
What Access Users Want From Copilot
| Want | Built into Access? | Practical alternative |
|---|---|---|
| Ask questions about the data in plain English | No | DatabaseAI, or Copilot in Excel on exported data |
| Write a query | No | Copilot Chat or ChatGPT with your schema |
| Write or fix VBA | No | Copilot Chat or ChatGPT with the code and form names |
| Design a form or report | No | AI suggests layout and controls; you build in Design View |
| Summarise records or notes | No | VBA calling an AI API, writing results to a field |
| Build charts and dashboards | No | Power BI or Excel connected to Access, with their Copilot features |
Workaround 1: Copilot Chat for SQL and VBA
Microsoft 365 Copilot Chat is a general assistant, so it handles Access SQL and VBA the same way ChatGPT does. The key is to tell it you are in Access, because Access SQL differs from SQL Server SQL in wildcards, date literals and join syntax.
I'm using Microsoft Access (ACE SQL).
Tables: tblJobs(JobID, CustomerID, Technician, ScheduledDate, Status),
tblCustomers(CustomerID, CompanyName, City).
Write a query listing jobs scheduled next week that are not Completed,
with company and city, sorted by date. Use # date literals,
bracket field names, and Access-style joins.Full guidance: using ChatGPT to write Access SQL and using AI for Access VBA. Both apply to Copilot Chat.
Workaround 2: Copilot in Excel on Access Data
In Excel: Data → Get Data → From Database → From Microsoft Access Database, pick the query or table.
Load it as a Table. Save the workbook to OneDrive or SharePoint.
Open Copilot in Excel and ask questions about the table.
Refresh the query when you need current data.
This works well for analysis of a defined dataset, such as last year's orders. It is not a live view, and it puts a copy of the data in a workbook that may be shared more widely than the database. Check what you are exporting.
Workaround 3: A Dedicated AI Tool for Access
Natural-language query tools built for Access read the schema directly, turn questions into read-only SQL, and run them against the actual file.
| Aspect | Copilot in Excel on exported data | DatabaseAI on the Access file |
|---|---|---|
| Data freshness | As of last refresh | Live file |
| Multiple tables and joins | Only what you exported | Uses the database's tables and relationships |
| Write risk | None to the database | None: read-only, SELECT only |
| Licence | Microsoft 365 Copilot | Per-user DatabaseAI licence |
| Platform | Excel desktop or web | Windows desktop |
How these tools work, and how to prepare your database so the answers are accurate, is covered in asking your Access database questions in plain English.
Workaround 4: AI Inside Your Own Forms
For record-level tasks, such as summarising job notes or classifying incoming requests, VBA can call an AI API and write the result into a field on the form. That gives Access users a "Copilot button" for a specific job. The code is in connecting MS Access to the OpenAI API.
Should You Move Off Access to Get Copilot?
Microsoft's AI investment is concentrated in Power Platform, Dataverse, SQL Server and Power BI. Moving there brings Copilot features, but the decision should rest on the usual factors.
Stay on Access when
Users are on one site or a stable remote desktop, data is well under 2 GB, forms and VBA work, and the team can maintain it.
Move the back end to SQL Server when
Data volume, concurrency or corruption is the problem. Forms can stay in Access; Power BI and other tools gain direct access to the data.
Rebuild in Power Apps or a web app when
Users need mobile or browser access from anywhere, and the budget covers redevelopment and per-user licensing.
Our comparison of Access vs Power Apps goes deeper, and our migrate and upgrade service covers each path. An Access consultant can give you a written recommendation before you spend anything.
FAQ
Copilot and Microsoft Access FAQ
Current limits and practical alternatives