Azure SQL Database gateways changes effective September 15, 2020
Published date: August 19, 2020
Beginning September 15, 2020, new Azure SQL Database gateways in these regions will start accepting traffic:
184.108.40.206 and 220.127.116.11
18.104.22.168 and 22.214.171.124
Beginning September 15, 2020, this existing Azure SQL Database gateways in these region will start accepting traffic:
126.96.36.199 and 188.8.131.52
184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, and 126.96.36.199
188.8.131.52, 184.108.40.206, and 220.127.116.11
18.104.22.168, 22.214.171.124, 126.96.36.199, and 188.8.131.52
East US 2
184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, and 126.96.36.199
188.8.131.52 and 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, and 126.96.36.199
North Central US
188.8.131.52, 184.108.40.206, and 220.127.116.11
18.104.22.168, 22.214.171.124, and 126.96.36.199
188.8.131.52, 184.108.40.206, and 220.127.116.11
These new gateways could change the public IP address to which the domain name system (DNS) will resolve for your current and newly created SQL databases. You may be affected if:
- You’ve hard-coded the IP address for a particular gateway in your on-premises firewall.
- You have any subnets using Azure SQL Database as a service endpoint, but can’t communicate with the gateway IP addresses in the region.
- You use the zone redundant configuration for your database.
We recommend that you allow network traffic to and from all SQL Database gateways for these regions as outlined in this table.
Read additional details on how traffic will be migrated to new SQL Database gateways in specific regions.
If you have questions or concerns, please contact us.