Action required for Azure SQL databases

Question

We got a notification - All Azure SQL Database traffic in the listed regions will be migrated to Gateway IP address subnets on or after 31 August 2023. As a result, the public IP addresses of your SQL databases in these regions may change.

To avoid service disruptions, update your network configuration to allow communication with all Gateway IP address subnets in the listed regions by 31 August 2023

my question - where the network configuration must be made to allow gateway IP address subnets . can you pls help ?

Answer 1

Please proceed to add the IP addresses of the Gateways on the firewall rules on the Azure SQL Database logical server as shown on the image below.

Add the IP addresses associated to the location of the Azure SQL Database server. Here you will find the IP addresses you need to add.

Answer 2

Hi Krishnamurthy, K (Karthik),

Welcome to Microsoft Q&A forum.

In addition to Alberto's answer,

The changes that you may need to make are listed in our docs here : https://learn.microsoft.com/en-us/azure/azure-sql/database/connectivity-architecture?view=azuresql-db#gateway-ip-addresses.

Logins for SQL Database or dedicated SQL pools (formerly SQL DW) in Azure Synapse can land on any of the Gateway IP address subnets in a region. For consistent connectivity to SQL Database or dedicated SQL pools (formerly SQL DW) in Azure Synapse, allow network traffic to and from all the Gateway IP address subnets in a region.

If above information does not help, we recommend you to raise support case as allowing listing traffic from customers infrastructure (either on-premises or in Azure) is something that is very subjective based on the architecture.
You may check with your internal IT team, and they will do the allow listing at the appropriate firewall device.

Do let us know if further queries, thanks