About Azure SQL Managed Connector

srikanthp24 — Fri, 16 Oct 2026 18:02:01 GMT

Hi Community,

We are trying to configure a Databricks Lakeflow Connect managed SQL Server connector to ingest data from Azure SQL Database into Databricks.

We are using a contained SQL database user that has access only to the specific source database, with no access to the "master" database.

However, during connection validation, we are encountering the following error:

Authentication failure while obtaining the connection to the source database: Error while creating connection pool for catalog master. Login failed for user '<contained_db_user>'.

Our understanding:

It appears that the Lakeflow Connect managed SQL Server connector attempts to establish a connection to the master database during connection validation, even though the intended source is a specific Azure SQL database.

Since we are using a contained database user, authentication to "master" fails.

Our security requirement:

We need to restrict the service account to the source database only, without granting access to "master".

Questions for the community:

Has anyone successfully configured the Lakeflow Connect managed SQL Server connector using a contained database user with access restricted to a single Azure SQL database?
Is there a supported configuration to bypass master database authentication and connect directly to the specified source database?
Is access to "master" mandatory for this connector, even when ingesting from only one database?
Are there any recommended workarounds that preserve database-level security isolation while still using the managed Lakeflow Connect connector?

We would prefer to use the managed Lakeflow Connect connector rather than building a custom JDBC ingestion framework.

If you have any better approach suggest?
Any insights, experiences, or recommendations would be greatly appreciated.

Thanks!

topic About Azure SQL Managed Connector in Data Engineering

About Azure SQL Managed Connector