This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 13%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWK%3C/text%3E%3C/svg%3E)
I have created firewall exceptions in the console for my IP address, but something else is going on and I don't know how to troubleshoot. Can someone help?
An Azure relational database service.
A couple of hours later after you posted, does the issue still persist? It could be that you came in the middle of a failover, and the database was temporarily available.
Another thing to try is to check Trust Server Certificate in the connection dialog in SSMS. That should not be necessary, because you should have a root certificate in your trusted certificate store. However, it's worth trying as a means of troubleshooting.
Since you shared your server name (which I don't recommend), I tried to connecting myself, but I was told in very clear terms that my IP address did not qualify for the firewall. So that suggests that the firewall is in order.
This is usually an intermittent error, an error associated with pre-login handshakes caused by network delays or delays in certificate validation by the SqlClient driver. Pre-login handshake should ideally complete in 100-200 ms. Please consider collecting a network trace to verify the existence latencies greater than expected.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 24%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Wesley Kalata,
This error typically means the connection reaches Azure SQL, but the SSL/TLS handshake or login phase is being interrupted. Since your IP is already allowed, the issue is usually related to encryption settings, drivers, or network restrictions.
Ask the customer to first confirm they are using the latest version of SSMS or an up-to-date SQL client, as older clients may not support the required TLS versions used by Azure SQL. They should also ensure that “Encrypt connection” is enabled and “Trust server certificate” is checked in the connection settings.
Next, have them verify that TLS 1.2 is enabled on their machine, as Azure SQL requires it. If they are on an older OS or using outdated drivers, this can cause the connection to be forcibly closed.
It’s also important to check whether a corporate firewall, proxy, or antivirus is interfering with outbound traffic on port 1433. Even if Azure firewall rules are correct, local network security can terminate the connection.
Additionally, confirm they are connecting using the correct server name format (servername.database.windows.net) and SQL authentication format (username@servername).
If the issue persists, ask them to try connecting using Azure Data Studio or sqlcmd to isolate whether it is a client-specific issue, and capture a network trace or error logs for deeper analysis.
Hi Wesley Kalata,
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.