Share via

SQL Azure Failover Group Deployment Fails - Gateway Timeout

Drew F 1 Reputation point
2025-01-11T00:53:39.0666667+00:00

I've been trying to create a failover group for a SQL Azure Database Pool (DTU model). The failover database (in location East US) has the same configuration (credentials and service level) as the primary database (in location South Central US). When deploying the failover group it always ends up with a GatewayTimeout error and the message "The gateway did not receive a response from 'Microsoft.Sql' within the specified time period" after quite a while.

The failover group is being marked as a standby replica and there are 142 databases within the pool that are being selected.

I've followed the guidance at https://zcusa.951200.xyz/en-us/azure/azure-sql/database/failover-group-sql-db?view=azuresql

I don't think this matters, however I did not select the failover database region as North Central US which I believe is paired to South Central US as my subscription does not allow creating resources in North Central US for some unknown reason. https://zcusa.951200.xyz/en-us/azure/reliability/cross-region-replication-azure

Does anyone have any advice on how to successfully deploy this failover group?

Azure SQL Database

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alberto Morillo 34,436 Reputation points MVP
    2025-01-11T02:31:46.65+00:00

    While you mentioned that you cannot use North Central US, using paired regions is recommended for better performance and reliability. If possible, try to resolve the subscription issue preventing you from using North Central US. Using a paired region, I doubt you will face timeouts.

    In addition, could you please try to whitelist the Gateways IP Addresses of the regions involved on the Azure SQL Firewall entries of the Azure SQL logical servers? Here is the list.

    0 comments
  2. RahulRandive 10,066 Reputation points
    2025-01-11T15:53:17.9566667+00:00

    Hi @Drew F

    1. Try re-registering the resource provider Microsoft.Sql as the error seems related to it.

    User's image

    2nd, at the server level, under Networking, enable the option Allow Azure Services and resources to access this server.

    1. If the issue persists, you may need to open a support case to either:
      1. Allow your subscription to create a server in the paired region, or
      2. Investigate the gateway-related error you are encountering

    Thank You!

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.