Access Database Migration to Azure SQL DB fails

Question

Access Database Migration to Azure SQL DB fails

Stephan Hölzer 20

I tried to connect the Azure SQL database to my Access program. Unfortunately, I always get this error when I select DB as the schema in ODBC.

Using other methods, I can only select the “master” or “Default” schema, and then the tables are not there.

My Access is up to date an also my ODBC driver. I thought picking Azure DB would work out of the box.

User's image

Anonymous

2025-09-22T10:28:09+00:00
Hi @Stephan Hölzer,

Thanks for contacting to Microsoft QA.

It looks like you're running into a common issue when trying to connect Microsoft Access to an Azure SQL Database using ODBC. The error you're seeing—about referencing master.sysdatabases—is expected behavior in Azure SQL.

Unlike traditional SQL Server, Azure SQL is a cloud-based service (PaaS), and it works a bit differently. It doesn’t give direct access to system databases like master, model, or msdb, which Access sometimes tries to query behind the scenes. That’s why you’re getting the error—it’s trying to reach something that Azure SQL doesn’t allow.

Set Up Your ODBC Connection Properly

When configuring your ODBC connection, make sure you’re pointing to your actual Azure SQL database—not the default or master database.

In Access, double-check that you’re selecting the correct schema (like dbo or any custom schema you’ve created). Avoid choosing “master” or “default” as those won’t work in Azure SQL.

Check Your DSN Settings

Ensure your Data Source Name (DSN) includes the correct server name, database name, and authentication method.

The database name should match the one you’re working with—not the system default.

Use the Right ODBC Driver

If you haven’t already, install the latest version of the https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server. Some users find better compatibility with version 17.

Try SSMS or Azure Data Studio

If Access continues to give you trouble, try connecting to your Azure SQL Database using

https://learn.microsoft.com/en-us/sql/ssms/sql-server-management-studio-ssms

or https://learn.microsoft.com/en-us/sql/azure-data-studio/download-azure-data-studio.

These tools can help confirm that your tables and schema are set up correctly.

Your patience and understanding are truly appreciated.

Thanks,
Vrishabh
Anonymous

2025-09-23T03:49:33.8033333+00:00

Hi @Stephan Hölzer,

May I kindly ask if the solution we provided earlier was helpful for you? Please let us know if you need any further assistance—we’d be happy to assist you.

Thanks,
Vrishabh
Anonymous

2025-09-24T09:00:58.1266667+00:00

Hi @Stephan Hölzer,

Just checking if the steps provided above have resolved your concern, or if you need any further assistance.

Thanks,
Vrishabh
Stephan Hölzer 20 Reputation points

2025-09-24T09:08:59.1233333+00:00

Hello, thank you for your support. New user was the easiest way to avoid this issue.

Access still asks for user password every time i open it. But i have the hope, that is just a configuration issue.

Answer accepted by question author

0 additional answers

Your answer

Anonymous

2025-09-22T10:28:09+00:00

Hi @Stephan Hölzer,

Thanks for contacting to Microsoft QA.

It looks like you're running into a common issue when trying to connect Microsoft Access to an Azure SQL Database using ODBC. The error you're seeing—about referencing master.sysdatabases—is expected behavior in Azure SQL.

Unlike traditional SQL Server, Azure SQL is a cloud-based service (PaaS), and it works a bit differently. It doesn’t give direct access to system databases like master, model, or msdb, which Access sometimes tries to query behind the scenes. That’s why you’re getting the error—it’s trying to reach something that Azure SQL doesn’t allow.

Set Up Your ODBC Connection Properly

When configuring your ODBC connection, make sure you’re pointing to your actual Azure SQL database—not the default or master database.

In Access, double-check that you’re selecting the correct schema (like dbo or any custom schema you’ve created). Avoid choosing “master” or “default” as those won’t work in Azure SQL.

Check Your DSN Settings

Ensure your Data Source Name (DSN) includes the correct server name, database name, and authentication method.

The database name should match the one you’re working with—not the system default.

Use the Right ODBC Driver

If you haven’t already, install the latest version of the https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server. Some users find better compatibility with version 17.

Try SSMS or Azure Data Studio

If Access continues to give you trouble, try connecting to your Azure SQL Database using

https://learn.microsoft.com/en-us/sql/ssms/sql-server-management-studio-ssms

or https://learn.microsoft.com/en-us/sql/azure-data-studio/download-azure-data-studio.

These tools can help confirm that your tables and schema are set up correctly.

Your patience and understanding are truly appreciated.

Thanks,
Vrishabh
Anonymous

2025-09-23T03:49:33.8033333+00:00

Hi @Stephan Hölzer,

May I kindly ask if the solution we provided earlier was helpful for you? Please let us know if you need any further assistance—we’d be happy to assist you.

Thanks,
Vrishabh
Anonymous

2025-09-24T09:00:58.1266667+00:00

Hi @Stephan Hölzer,

Just checking if the steps provided above have resolved your concern, or if you need any further assistance.

Thanks,
Vrishabh
Stephan Hölzer 20 Reputation points

2025-09-24T09:08:59.1233333+00:00

Hello, thank you for your support. New user was the easiest way to avoid this issue.

Access still asks for user password every time i open it. But i have the hope, that is just a configuration issue.

Answer 1

Hello Stefan !

Thank you for posting on Microsoft Learn.

You can fix your it by connecting directly to your target database with a modern SQL Server ODBC driver and a contained user. Instead of browsing for databases OR schemas, you can create a contained user in the target DB so you avoid using the server admin whose default DB is master:

-- Run in your TARGET database, not master
CREATE USER app_access WITH PASSWORD = 'Strong#Password123!';
ALTER ROLE db_datareader ADD MEMBER app_access;
ALTER ROLE db_datawriter ADD MEMBER app_access;
ALTER USER app_access WITH DEFAULT_SCHEMA = dbo;

Or create a DSN that pins the database (Access then External Data then ODBC Database then Machine Data Source then New):

Driver: ODBC Driver 18 for SQL Server (not the legacy SQL Server driver).
Server: yourserver.database.windows.net
Authentication: SQL login app_access / password
Click Options and set Database = YourDatabaseName
Encrypt = Yes and Trust Server Certificate = No (Driver 18 defaults are fine).

Equivalent connection string for File DSN or linked table manager:

Driver={ODBC Driver 18 for SQL Server};
Server=tcp:yourserver.database.windows.net,1433;
Database=YourDatabaseName;
Uid=app_access;Pwd=Strong#Password123!;
Encrypt=yes;TrustServerCertificate=no;

Then link tables in Access, under External Data then ODBC Database then Link to the data source then choose your DSN.

When Access asks for owner, pick dbo. Your tables should appear.