Connection getting failed from Azure synapse link with Qliksense Cloud

Hi Bias CRM

This error mean the user is invalid in the database that you are trying to connect, usually related to a AAD user that does not have user created on SQL DB that you are trying to connect (User DB or Master DB) or that the user is not the AAD Server Admin

Recommended fix

Use SQL authentication:

1. Create a SQL login + user in your Synapse SQL pool:

CREATE LOGIN qlik_user WITH PASSWORD='StrongPassword!';
CREATE USER qlik_user FROM LOGIN qlik_user;
ALTER ROLE db_datareader ADD MEMBER qlik_user;

In Qlik, choose SQL (username/password) authentication.

Also Check Networking

• Ensure Public network access is enabled for Synapse SQL.
• Add Qlik Cloud outbound IPs to the SQL firewall, or enable Allow Azure services.

If you must use Azure AD
You need to register a service principal, assign permissions, and create an EXTERNAL PROVIDER user — but Qlik often has limited AAD support, so SQL authentication is generally the reliable method.

Once SQL auth + firewall rules are set correctly, Qlik’s connection test should succeed.

Hope this helps, Please let us know if you have any questions and concerns.

If this solution helped resolve your issue, please consider clicking ‘Accept Answer’ or giving it an upvote to help others find it easily.

The error Login failed for user '<token-identified principal>' indicates that Qlik Sense is not sending the Databricks/Synapse access token in the way the connector expects, or the connection properties (username/password/HTTP path) are not set correctly.

For Qlik Sense connecting to a Databricks/Synapse SQL endpoint, configure the connection as follows:

1. In Qlik Sense, when defining the connection:
   • Set Database name to the target database name.
   • Set HTTP Path to the HTTP path of the SQL endpoint.
2. In the Credentials section:
   • Set User name to the literal value token (not an actual user name).
   • Set Password to the actual access token that grants access to the Synapse/Databricks endpoint.
3. In SSL Options, enable the following:
   • Enable SSL
   • Allow Self-signed Server Certificate
   • Allow Common Name Host Name Mismatch
   • Use System Trust Store
4. Test the connection again.

If the username is not token or the password is not a valid token, the backend will treat the login as a regular SQL login and fail with the token-identified principal error shown in the screenshot.

References:

• Connect to Qlik Sense