Merge pull request #220274 from kainawroth/patch-4

Info about necessity of adding regional IPs to firewall

Author: prmerger-automator[bot]

articles/azure-monitor/app/ip-addresses.md

@@ -26,7 +26,8 @@ You need to open some outgoing ports in your server's firewall to allow the Appl
 | Telemetry | dc.applicationinsights.azure.com<br/>dc.applicationinsights.microsoft.com<br/>dc.services.visualstudio.com<br/>*.in.applicationinsights.azure.com<br/><br/> || 443 |
 | Live Metrics | live.applicationinsights.azure.com<br/>rt.applicationinsights.microsoft.com<br/>rt.services.visualstudio.com<br/><br/>{region}.livediagnostics.monitor.azure.com<br/><br/>*Example for {region}: westus2<br/>Find all supported regions in [this table](#addresses-grouped-by-region-azure-public-cloud).*|20.49.111.32/29<br/>13.73.253.112/29| 443 |
 
-
+> [!IMPORTANT]
+> For Live Metrics, it is *required* to add the list of IPs for the respective region aside from global IPs.
 
 > [!NOTE]
 > These addresses are listed by using Classless Interdomain Routing notation. As an example, an entry like `51.144.56.112/28` is equivalent to 16 IPs that start at `51.144.56.112` and end at `51.144.56.127`.