Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
Anonymous
Not applicable

encryption support warning message

I am trying to connect to an on-prem SQL Server DB.  I use CNames (aliases) for my SQL Servers.  So, I am connecting to the desired DB with a server name like cname1.domain.com.  Power BI Desktop is throwing the following warning message:

Encryption Support

The server name provided doesn't match the server name on the SQL Server SSL certificate.  Please contact your administrator or see the link below for more information.  Alternatively, you could change your Connection encryption setting.  Would you like to continue using an unencrypted connection?

 

If I click OK and continue with an unencrypted connection, the connection is successful.  However, in doing so, am I creating a security risk?  I clicked on the link that was provided, but I don't understand what it's telling me.  If this is a security risk, how do I resolve it?

1 ACCEPTED SOLUTION
amitchandak
Super User
Super User

@Anonymous , sql server should be ssl enabled.

refer this for certificate

https://powerbi.microsoft.com/en-us/blog/ssl-security-error-with-data-source/

Share with Power BI Enthusiasts: Full Power BI Video (20 Hours) YouTube
Microsoft Fabric Series 60+ Videos YouTube
Microsoft Fabric Hindi End to End YouTube

View solution in original post

2 REPLIES 2
amitchandak
Super User
Super User

@Anonymous , sql server should be ssl enabled.

refer this for certificate

https://powerbi.microsoft.com/en-us/blog/ssl-security-error-with-data-source/

Share with Power BI Enthusiasts: Full Power BI Video (20 Hours) YouTube
Microsoft Fabric Series 60+ Videos YouTube
Microsoft Fabric Hindi End to End YouTube
Anonymous
Not applicable

It turns out that, at least in my particular situation, it's more complicated than mere SSL enabling.  My SQL Server data source forces encryption.  So, it's not true that the connection is unencrypted when I agree to the warning message.  It's the same situation as when a web server that uses an SSL certificate with a host name not specified in the certificate.  The connection is still encrypted, but it's the user's choice about whether to continue browsing the site.

 

Because we use CNAMEs, it's just a notification that the connection string name is different than the actual SQL Server name.  To resolve, I simply need to include all of the aliases and CNAMEs as subject alternative names in the certificate for the SQL Server SSL configuration. 

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Top Solution Authors