It is very common see Azure SQL customers open support incidents because they couldn’t connect to their Azure SQL Database server which was ultimately due to the incorrect assumption that the server’s IP address is static. However, the reality is the IP address of your Azure SQL logical server is not static and is subject to change at any time. All connections should be made using the fully qualified DNS name (FQDN) rather than the IP address.
Microsoft may do an online migration of your logical server between clusters within a region, load balancing capacity across the clusters within the region. This move is a live operation and there is no loss of availability to your database during the operation. When the migration completes, existing connections to your logical server are terminated and upon reconnecting via fully qualified domain name your ETL tool will be directed to the new cluster. However, if your ETL Tool caches or connects by IP address instead of FQDN then your connection attempts will fail.
While you allow authorization for DNS resolution on the network, you can identify the IP address of the Azure SQL server by pinging the logical Azure SQL server from a network with DNS resolution allowed. The ping will not get a successful reply from the server but it will give the current IP address of the logical server.