What causes DF-SQLDW-IncorrectLinkedServiceConfiguration?

The server name or workspace endpoint in the linked service is wrong — e.g. using a SQL Server endpoint instead of the Synapse dedicated pool endpoint. Authentication type is set to SQL auth but the Synapse pool is configured for Azure AD only. The database name refers to a database that does not exist or was renamed in the Synapse workspace. The linked service was migrated from a different environment and the server or database name was not updated

How do I fix DF-SQLDW-IncorrectLinkedServiceConfiguration?

In ADF Studio, open Manage > Linked services and select the Synapse (SQL DW) linked service.. Verify the server name format — for Synapse dedicated pools it should be .sql.azuresynapse.net; for SQL on-demand use -ondemand.sql.azuresynapse.net.. Verify the database name matches the Synapse dedicated pool name exactly — check the Synapse workspace in the Azure portal.. Check the authentication type — if the Synapse workspace is configured for Azure AD-only, switch authentication to Managed Identity or Service Principal in the linked service.. Click Test connection to verify the corrected settings, then save and retry the pipeline.

Medium severitydata source

Power BI Refresh Error:
DF-SQLDW-IncorrectLinkedServiceConfiguration

What does this error mean?

A property in the Azure Synapse Analytics (SQL DW) linked service is incorrect or inconsistent.

Common causes

1The server name or workspace endpoint in the linked service is wrong — e.g. using a SQL Server endpoint instead of the Synapse dedicated pool endpoint
2Authentication type is set to SQL auth but the Synapse pool is configured for Azure AD only
3The database name refers to a database that does not exist or was renamed in the Synapse workspace
4The linked service was migrated from a different environment and the server or database name was not updated

How to fix it

1In ADF Studio, open Manage > Linked services and select the Synapse (SQL DW) linked service.
2Verify the server name format — for Synapse dedicated pools it should be <workspace-name>.sql.azuresynapse.net; for SQL on-demand use <workspace-name>-ondemand.sql.azuresynapse.net.
3Verify the database name matches the Synapse dedicated pool name exactly — check the Synapse workspace in the Azure portal.
4Check the authentication type — if the Synapse workspace is configured for Azure AD-only, switch authentication to Managed Identity or Service Principal in the linked service.
5Click Test connection to verify the corrected settings, then save and retry the pipeline.

Frequently asked questions

What is the correct server endpoint format for Synapse Analytics?

For dedicated SQL pools: <workspace-name>.sql.azuresynapse.net. For serverless SQL pools: <workspace-name>-ondemand.sql.azuresynapse.net. Find the exact endpoint in the Azure portal under your Synapse workspace > Overview > Connection strings.

How is this different from auth credential errors?

IncorrectLinkedServiceConfiguration is about the structural properties of the linked service (server name, database, endpoint format). Auth errors occur when the properties are correct but the credentials (password, token, managed identity permission) are wrong.

Can this error appear after a Synapse workspace migration or rename?

Yes — if a Synapse workspace was renamed or the dedicated pool was moved to a different workspace, the server endpoint in the linked service will be stale. Update it to the new endpoint.

Will downstream Power BI datasets be affected?

Yes — the pipeline cannot connect to Synapse and will fail without loading any data. Downstream datasets will show stale data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide