TILLGÄNGLIGT NU

Azure SQL Database gateways changes effective September 15, 2020

Publiceringsdatum: 19 augusti, 2020

Beginning September 15, 2020, new Azure SQL Database gateways in these regions will start accepting traffic: 

Australia Southeast

13.77.48.10

Canada East

40.86.226.166 and 52.242.30.154

UK South

51.140.184.11 and 51.105.64.0

Beginning September 15, 2020, this existing Azure SQL Database gateways in these region will start accepting traffic: 

Australia Southeast

191.239.192.109 and 13.73.109.251

Central US

13.67.215.62, 52.182.137.15, 23.99.160.139, 104.208.16.96, and 104.208.21.1

East Asia

191.234.2.139, 52.175.33.150, and 13.75.32.4

East US

40.121.158.30, 40.79.153.12, 191.238.6.43, and 40.78.225.32

East US 2

40.79.84.180, 52.177.185.181, 52.167.104.0, 191.239.224.107, and 104.208.150.3

France Central

40.79.137.0 and 40.79.129.1

Japan West

104.214.148.156, 40.74.100.192, 191.238.68.11, and 40.74.97.10

North Central US

23.96.178.199, 23.98.55.75, and 52.162.104.33

Southeast Asia

104.43.15.0, 23.100.117.95, and 40.78.232.3

West US

104.42.238.205, 23.99.34.75, and 13.86.216.196

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.  

  • Azure SQL Database
  • Services

Tillhörande produkter