%3CLINGO-SUB%20id%3D%22lingo-sub-1254208%22%20slang%3D%22en-US%22%3ELesson%20Learned%20%23127%3A%20Using%20Azure%20SQL%20Database%20Private%20Link%20and%20PowerBI%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1254208%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20I%20worked%20on%20a%20service%20request%20that%20our%20customer%20received%20an%20error%20message%20connecting%20from%20PowerBI%20to%20Azure%20SQL%20Database%20using%20Private%20Link.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20error%20message%20was%3A%20The%20server%20name%20provided%20doesn't%20match%20the%20server%20name%20on%20the%20SQL%20Server%20SSL%20certificate.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20found%20that%20this%20issue%20ocurred%20when%20our%20customer%20uses%20in%20the%20connection%20string%20the%20FQDN%3A%20servername.privatelink.database.windows.net%20instead%20of%20servername.database.windows.net.%20When%20the%20server%20recieves%20the%20connection%20the%20SSL%20certificate%20validate%20the%20name.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20first%20suggestion%20was%20to%20use%20servername.database.windows.net%20because%20at%20the%20moment%20of%20the%20definition%20of%20the%20private%20link%20you%20could%20create%20a%20private%20DNS%20that%20will%20be%20added%20in%20your%20VNET%2FSubnet.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOther%20options%20are%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20could%20continue%20working%20even%20after%20the%20message%2C%20basically%20you%20could%20press%20OK%20and%20continue%20using%20PowerBI..%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EIf%20your%20DNS%20didn't%20allow%20or%20you%20cannot%20add%20an%20entry%20in%20your%20DNS%2C%20you%20could%20add%20in%20the%20host%20windows%20file%20the%20entry%20of%20your%20server.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEnjoy!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1254208%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20I%20worked%20on%20a%20service%20request%20that%20our%20customer%20received%20an%20error%20message%20connecting%20from%20PowerBI%20to%20Azure%20SQL%20Database%20using%20Private%20Link.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20error%20message%20was%3A%20The%20server%20name%20provided%20doesn't%20match%20the%20server%20name%20on%20the%20SQL%20Server%20SSL%20certificate.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E

Today, I worked on a service request that our customer received an error message connecting from PowerBI to Azure SQL Database using Private Link. 

The error message was: The server name provided doesn't match the server name on the SQL Server SSL certificate. 

 

We found that this issue ocurred when our customer uses in the connection string the FQDN: servername.privatelink.database.windows.net instead of servername.database.windows.net. When the server recieves the connection the SSL certificate validate the name.

 

Our first suggestion was to use servername.database.windows.net because at the moment of the definition of the private link you could create a private DNS that will be added in your VNET/Subnet.

 

Other options are:

 

  • You could continue working even after the message, basically you could press OK and continue using PowerBI.. 
  • If your DNS didn't allow or you cannot add an entry in your DNS, you could add in the host windows file the entry of your server. 

 

Enjoy!