Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
We have a few Azure SQL Servers hosting SQL Databases.
We also have an Azure VPN set up and we have set up "Private Access", providing us with privatelink URLs - [server name].privatelink.database.windows.net
When connecting to the SQL Servers using the private link URLs and using "Database" authentication, we are presented with the following error messages. Clicking OK then grants us access.
But when attempting to do the same using "Windows" or "Microsoft account" for Azure AD Authentication, the above error messages keep on popping up when clicking OK.
The System log shows the following 36884 event
The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is [server name].privatelink.database.windows.net. The TLS connection request has failed. The attached data contains the server certificate.
The SSPI client process is Microsoft.Mashup.Container.NetFX45 (PID: 39140).
Hi @ChrisMT ,
Based on the error message provided above, it seems to indicate that the name of the certificate is wrong. You need a certificate with the correct name.
Please follow these articles and check it:
How To: Troubleshoot AD LDAPS Connection Issues
Hope it helps,
Best Regards,
Community Support Team _ Caitlyn
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Thanks, but we don't use LDAPS and the certificate does not match because the server name is [server name].database.windows.net but we are connecting on [server name].privatelink.database.windows.net to use the Azure VPN.
The following setting resolves this in SQL Server Management Studio, but the same does not seem present in Power BI.
The private endpoint documentation on the Power BI side might help:
https://docs.microsoft.com/en-us/power-bi/enterprise/service-security-private-links
Hi and thanks, but the guide describes using a VM to connect to Power BI, but we are looking to connect directly from the user's machines (like we do with SSMS) and not via an RDP VM.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.