Merge pull request #102951 from hrasheed-msft/patch-137

Update hdinsight-management-ip-addresses.md

Author: PRMerger15

articles/hdinsight/hdinsight-management-ip-addresses.md

@@ -13,7 +13,7 @@ ms.date: 12/16/2019
 # HDInsight management IP addresses
 
 > [!Important]
-> Use the [service tag](hdinsight-service-tags.md) feature for network security groups. New regions will only be added for service tags and the static IP addresses will eventually be deprecated.
+> In most cases, you can now use the [service tag](hdinsight-service-tags.md) feature for network security groups, instead of manually adding IP addresses. New regions will only be added for service tags and the static IP addresses will eventually be deprecated.
 
 If you use network security groups (NSGs) or user defined routes (UDRs) to control inbound traffic to your HDInsight cluster, you must ensure that your cluster can communicate with critical Azure health and management services.  Some of the IP addresses for these services are region specific, and some of them apply to all Azure regions. You may also need to allow traffic from the Azure DNS service if you aren't using custom DNS.