Azure Community Forums

Hi everyone,

I'm encountering a persistent issue with accessing our Azure SQL Database. After a recent deployment/update (I'm not entirely sure which one caused it, but it started yesterday), we're unable to connect to the database from our on-premises development machines. The connection times out.

We haven't changed any firewall rules or network configurations from our end. Our application services hosted in Azure can still connect fine, which suggests the issue might be specific to external network access. I've checked the Azure portal, and the "Allow access to Azure services and resources" option is enabled, as are the specific IP address ranges for our office network.

Has anyone else experienced similar problems or have any ideas on what might be causing this?

Hi John,

I've seen a few reports of similar intermittent connectivity issues after certain platform updates. One common culprit can be a temporary misconfiguration or a transient issue with the network security group (NSG) associated with the VNet, even if you're not directly managing it.

Have you tried restarting the SQL Database server instance (if that's an option for the specific tier you're on) or checking the diagnostic logs for any network-related errors?

Also, sometimes clearing the DNS cache on your local machine can help resolve such issues.

Thanks Alice! Restarting the instance isn't directly available for the serverless tier we're using, but I'll check the diagnostic logs. I also tried clearing the DNS cache and flushing the local network adapters, but no luck so far. The application connectivity remains stable.

I suspect it's something on the Azure side. I'll open a support ticket as well.

Hello John,

We are aware of a recent platform update that may have impacted external connectivity for some Azure SQL Databases. Our engineering team has identified the root cause and is deploying a fix. We expect the issue to be fully resolved within the next few hours.

If you continue to experience problems after 12 PM UTC today, please reach out to Azure Support directly, referencing the internal incident ID #AZUREDB-67890. We apologize for any inconvenience this may have caused.

You can monitor the Azure status page for real-time updates: https://azure.microsoft.com/status/