在本周 SQL Azure 和 Azure DNS 出现众所周知的问题之后，我们刚刚在 Azure 门户中收到一条消息:
In the course of this week and next week starting 16 Sep 2016, we will be failing over SQL Azure DB connection router to increase capacity and provide additional resiliency in West Europe as one of the repair item from Azure SQL DB outage on 9/12 and 9/15 (Listed here: https://azure.microsoft.com/en-us/status/history) We have identified you who might be impacted by this change as you may be using outgoing firewall rules. As part of the failover process the IP address behind .database.windows.net will change. We recommend you add the following IP addresses to your rules to allow connections on port 1433 - Australia East: 13.75.149.87 - Australia South East: 13.73.109.251 - Japan East: 13.78.61.196 - Japan West: 104.214.148.156 - North Europe: 40.113.93.91 - South Central US: 13.66.62.124 - South East Asia: 104.43.15.0 - West Europe: 40.68.37.158 - West US: 104.42.238.205 Alternatively, please considering opening the outgoing firewall rules to the entire Azure IP address range set, available at https://www.microsoft.com/en-us/download/details.aspx?id=41653 For an overview of Azure SQL DB connectivity architecture for connections from inside and outside of Azure, please refer to this MDSN article https://azure.microsoft.com/en-us/documentation/articles/sql-database-develop-direct-route-ports-adonet-v12/ .
现在我们只需将一个非常标准的 ASP.NET MVC 应用程序部署到应用程序服务即可。它连接到托管在同一区域的 SQL Azure 数据库(主机名以 .database.windows.net 结尾)。这让我相信我们不需要对上面的消息做出任何反应，因为这一切都在“Azure 内部”。有人可以在此确认我们的想法吗？也许可以解释一下在哪些情况下需要对上述信息使用react？不幸的是，消息中的链接与此确切的更改并不是特别相关，因此这里的答案也许会让其他也收到此消息并希望确保他们没有遗漏任何内容的人受益。
最佳答案
在您的情况下，您似乎不需要执行任何操作:已有通用防火墙规则允许 Azure 资源(例如 Web 应用程序)访问 SQL 数据库。您应该已经启用了该规则。
出站防火墙规则将特定于尝试与基于 Azure 的 SQL 数据库实例建立连接并具有限制出站流量的事件防火墙的外部虚拟机/服务器(例如本地)。因此，任何拥有将 IP 范围列入白名单并允许 SQL 数据库访问的事件防火墙的人都需要相应地更新其防火墙的 IP 范围。
关于azure - SQL Azure DB 连接路由器修复消息 : Do I need to take action?，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/39546520/