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

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

WantBuilt into Access?Practical alternative
Ask questions about the data in plain EnglishNoDatabaseAI, or Copilot in Excel on exported data
Write a queryNoCopilot Chat or ChatGPT with your schema
Write or fix VBANoCopilot Chat or ChatGPT with the code and form names
Design a form or reportNoAI suggests layout and controls; you build in Design View
Summarise records or notesNoVBA calling an AI API, writing results to a field
Build charts and dashboardsNoPower 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.

AspectCopilot in Excel on exported dataDatabaseAI on the Access file
Data freshnessAs of last refreshLive file
Multiple tables and joinsOnly what you exportedUses the database's tables and relationships
Write riskNone to the databaseNone: read-only, SELECT only
LicenceMicrosoft 365 CopilotPer-user DatabaseAI licence
PlatformExcel desktop or webWindows 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

At the time of writing, Microsoft Access does not have a built-in Copilot pane like Excel, Word, PowerPoint and Outlook. You cannot open Copilot inside Access and ask it about your tables. Check Microsoft's Access release notes, as this may change.

Yes. Copilot Chat, like other AI assistants, can write Access SQL, VBA, form designs and table structures if you describe your database. It cannot see the database itself, so you provide table and field names and test the output.

Indirectly. Export a query to Excel, or connect Excel to the Access database with Power Query, save the workbook to OneDrive or SharePoint, and Copilot in Excel can analyse that table. The analysis is of the exported snapshot, not the live database.

A natural-language query tool built for Access, such as DatabaseAI, reads the schema, turns questions into read-only SQL, and runs them against the live file. It avoids exporting data to another application and shows the SQL behind each answer.

Not for Copilot alone. Moving to SharePoint lists, Dataverse with Power Apps, or SQL Server with Power BI brings Copilot features, but also cost, retraining and redevelopment. Decide based on users, data volume, remote access and maintenance, then treat AI features as a bonus.