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(105.60000000000001, 25%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEM%3C/text%3E%3C/svg%3E)
Hi community,
We're currently facing a critical issue with our Azure SQL Server in the Central US region. All attempts to create or update firewall rules (via Portal, Azure CLI, and PowerShell) result in a GatewayTimeout error:
(GatewayTimeout) The gateway did not receive a response from 'Microsoft.Sql' within the specified time period.
This is blocking all external connectivity to our database, and our customers are without service. We wanted to check if anyone else is experiencing this or if there are any known workarounds.
Any insights or suggestions are welcome.
Thanks in advance!
On Azure Portal please verify there are no temporary issues affecting your Azure SQL.
If you find that an incident is affecting your Azure SQL, and have DR enable then failover as a workaround.
Hi Alberto,
Thank you for your guidance.
Although Resource Health now shows the incident as “Available” and indicates the issue was recently resolved, I am still unable to access or manage my Azure SQL Database.
Current situation:
I cannot connect to the database or export data.
In the Networking/Firewall settings, I receive this error: “An error occurred while fetching firewall rule details. Please try loading the firewall rule again.”
This prevents me from viewing or updating any firewall rules, which means all access to the database remains blocked.
I have attached a screenshot of this error for reference.
It seems the platform issue is not fully resolved, as I cannot manage networking/firewall settings and the database remains inaccessible. Is this a known post-incident problem? Is there any workaround, or should I wait for a full backend recovery from Azure?
Thank you for your help.
Attachments:
Microsoft Support has investigated and found that one of the nodes in the underlying infrastructure for our Azure SQL Server was in an unhealthy state. They will move the service to a healthy node to restore normal operations.
I would like to mention that I had to pay for a $100 support request to get this issue escalated
Eduardo Muñoz Thank you for reaching out and sorry about the issue you faced in your Azure SQL DB.
Thanks for sharing that update. It’s great to hear that issue was identified and the root cause was due to an unhealthy node in the infrastructure—and is moving your Azure SQL Server to a healthy node to restore service.
Could you please kindly share the support ticket you have raised on this issue.
Are you on a basic support plan?
Regards,
Oury
Thank you Eduardo for sharing the cause of the incident
![](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(252.8, 60%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
Hi Eduardo Muñoz,
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
Issue:
We're currently facing a critical issue with our Azure SQL Server in the Central US region. All attempts to create or update firewall rules (via Portal, Azure CLI, and PowerShell) result in a GatewayTimeout error:
(GatewayTimeout) The gateway did not receive a response from 'Microsoft.Sql' within the specified time period.
This is blocking all external connectivity to our database, and our customers are without service. We wanted to check if anyone else is experiencing this or if there are any known workarounds.
Solution:
Microsoft Support has identified that one of the nodes in the underlying infrastructure for our Azure SQL Server was in an unhealthy state. They will migrate the service to a healthy node to restore normal operations.
If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.
Hope this helps. Do let us know if you have any further queries.
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.