Azure Monitor endpoint access and firewall configuration

If your monitored application or infrastructure is behind a firewall, you need to configure network access to allow communication with Azure Monitor services.

Azure Monitor uses service tags, which provide a more reliable and dynamic way to manage network access. Service tags are regularly updated and can be retrieved through an API, ensuring that you have the latest available IP address information without requiring manual updates.

If you're using Azure network security groups, you can manage access with Azure network service tags. For hybrid or on-premises resources, you can download the equivalent IP address lists as JSON files, which are refreshed weekly. To cover all necessary exceptions, use the service tags ActionGroup, ApplicationInsightsAvailability, and AzureMonitor. For more information, see Azure Service Tags Overview.

You need to open some outgoing ports in your server's firewall to allow the Application Insights SDK or Application Insights Agent to send data to the portal.

Application Insights Agent configuration is needed only when you're making changes.

The Application Insights team owns the *.applicationinsights.io domain.

The Log Analytics team owns the *.loganalytics.io domain.

You can query the list of IP addresses used by action groups by using the Get-AzNetworkServiceTag PowerShell command.

Managing changes to source IP addresses can be time consuming. Using service tags eliminates the need to update your configuration. A service tag represents a group of IP address prefixes from a specific Azure service. Microsoft manages the IP addresses and automatically updates the service tag as addresses change, which eliminates the need to update network security rules for an action group.

1. In the Azure portal under Azure Services, search for Network Security Group.

2. Select Add and create a network security group:

   1. Add the resource group name, and then enter Instance details information.
   2. Select Review + Create, and then select Create.

   

3. Go to Resource Group, and then select the network security group you created:

   1. Select Inbound security rules.
   2. Select Add.

   

4. A new window opens in the right pane:

   1. Under Source, enter Service Tag.
   2. Under Source service tag, enter ActionGroup.
   3. Select Add.

   

This section provides answers to common questions.

Yes, but you need to allow traffic to our services by either firewall exceptions or proxy redirects.

See IP addresses used by Azure Monitor to review our full list of services and IP addresses.

Route traffic from your server to a gateway on your intranet by overwriting endpoints in your configuration. If the Endpoint properties aren't present in your config, these classes use the default values which are documented in IP addresses used by Azure Monitor.

Your gateway should route traffic to our endpoint's base address. In your configuration, replace the default values with http://<your.gateway.address>/<relative path>.

If your product doesn't support service tags, take the following steps to ensure full connectivity:

• Check the latest IP ranges in the downloadable Azure IP ranges and service tags JSON file, which updates weekly.
• Review firewall logs for blocked requests and update your allowlist as needed.

For more information, see Azure Service Tags Overview.