Share via

Action required for your Azure SQL Database service

Anonymous
2023-08-01T08:55:50.0833333+00:00

You're receiving this notification because you use Azure SQL Database.

To improve performance and reduce login latency, 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.

Regions:Central US

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 as outlined in our documentation.

If you use zone redundant configuration in SQL Database, ensure that your client can communicate with all gateways in their respective region.

Please let us know action is actually required from DBA prospective?

Azure SQL Database

2 answers

Sort by: Most helpful
  1. SSingh-MSFT 16,461 Reputation points Moderator
    2023-08-03T04:01:38.8566667+00:00

    Hi Priyanka Roy (ns),

    Welcome to Microsoft Q&A forum.

    As I understand, you want to know what actions are needed to be performed for Azure SQL Database on the notification received.

    The changes that needs to be done 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.

    Hope this helps. If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    Thanks

    Was this answer helpful?


  2. Alberto Morillo 35,506 Reputation points MVP Volunteer Moderator
    2023-08-01T14:22:07.4166667+00:00

    I have received similar emails in the past. The only thing I do is add the IPs of the new gateways on the firewall rules on the Azure SQL Database logical server as shown on the image below.

    User's image

    Please add these IP addresses to your firewall 52.246.152.0, 20.38.144.1. These IP addresses are associated to US Central Gateways.

    You do not have to do anything else. Based on my experience everything keeps working as usual.

    Was this answer helpful?


Your answer

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