Skip to content

Commit dea9b3b

Browse files
author
Jill Grant
authored
Merge pull request #269089 from AaronMaxwell/aaronmax-ip-addr-link-to-private-test
Linking to existing doc on availability testing
2 parents 8860f58 + 478d06a commit dea9b3b

File tree

1 file changed

+3
-116
lines changed

1 file changed

+3
-116
lines changed

articles/azure-monitor/ip-addresses.md

Lines changed: 3 additions & 116 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: IP addresses used by Azure Monitor | Microsoft Docs
33
description: This article discusses server firewall exceptions that are required by Azure Monitor
44
ms.topic: reference
5-
ms.date: 11/15/2023
5+
ms.date: 03/14/2024
66
ms.servce: azure-monitor
77
ms.author: aaronmax
88
ms.reviewer: saars
@@ -28,14 +28,11 @@ You need to open some outgoing ports in your server's firewall to allow the Appl
2828
| Purpose | URL | Type | IP | Ports |
2929
| --- | --- | --- | --- | --- |
3030
| Telemetry | dc.applicationinsights.azure.com<br/>dc.applicationinsights.microsoft.com<br/>dc.services.visualstudio.com<br/>\*.in.applicationinsights.azure.com<br/><br/> |Global<br/>Global<br/>Global<br/>Regional<br/>|| 443 |
31-
| 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).*|Global<br/>Global<br/>Global<br/><br/>Regional<br/>|20.49.111.32/29<br/>13.73.253.112/29| 443 |
31+
| 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|Global<br/>Global<br/>Global<br/><br/>Regional<br/>|20.49.111.32/29<br/>13.73.253.112/29| 443 |
3232

3333
> [!NOTE]
3434
> Application Insights ingestion endpoints are IPv4 only.
3535
36-
> [!IMPORTANT]
37-
> For Live Metrics, it is *required* to add the list of [IPs for the respective region](#addresses-grouped-by-region-azure-public-cloud) aside from global IPs.
38-
3936
## Application Insights Agent
4037

4138
Application Insights Agent configuration is needed only when you're making changes.
@@ -53,117 +50,7 @@ Application Insights Agent configuration is needed only when you're making chang
5350

5451
## Availability tests
5552

56-
This is the list of addresses from which [availability web tests](./app/availability-overview.md) are run. If you want to run web tests on your app but your web server is restricted to serving specific clients, you must permit incoming traffic from our availability test servers.
57-
58-
> [!NOTE]
59-
> For resources located inside private virtual networks that can't allow direct inbound communication with the availability test agents in public Azure, the only option is to [create and host your own custom availability tests](app/availability-azure-functions.md#review-trackavailability-test-results).
60-
61-
### Service tag
62-
63-
If you're using Azure network security groups, add an *inbound port rule* to allow traffic from Application Insights availability tests. Select **Service Tag** as the **Source** and **ApplicationInsightsAvailability** as the **Source service tag**.
64-
65-
>[!div class="mx-imgBorder"]
66-
>:::image type="content" source="./app/media/ip-addresses/add-inbound-security-rule.png" lightbox="./app/media/ip-addresses/add-inbound-security-rule.png" alt-text="Screenshot that shows selecting Inbound security rules and then selecting Add.":::
67-
68-
>[!div class="mx-imgBorder"]
69-
>:::image type="content" source="./app/media/ip-addresses/add-inbound-security-rule2.png" lightbox="./app/media/ip-addresses/add-inbound-security-rule2.png" alt-text="Screenshot that shows the Add inbound security rule tab.":::
70-
71-
Open port 80 (HTTP) and port 443 (HTTPS) for incoming traffic from these addresses. IP addresses are grouped by location.
72-
73-
> [!NOTE]
74-
> Validate your Azure App Service access restrictions, as you might need to also enable access for availability test IP addresses. For more information, see [Azure App Service access restrictions](../app-service/overview-access-restrictions.md).
75-
76-
### IP addresses
77-
78-
If you're looking for the actual IP addresses so that you can add them to the list of allowed IPs in your firewall, download the JSON file that describes Azure IP ranges. These files contain the most up-to-date information. After you download the appropriate file, open it by using your favorite text editor. Search for **ApplicationInsightsAvailability** to go straight to the section of the file that describes the service tag for availability tests.
79-
80-
For Azure public cloud, you need to allow both the global IP ranges and the ones specific for the region of your Application Insights resource which receives live data. You can find the global IP ranges in the [Outgoing ports](#outgoing-ports) table at the top of this document, and the regional IP ranges in the [Addresses grouped by region](#addresses-grouped-by-region-azure-public-cloud) table below.
81-
82-
#### Azure public cloud
83-
84-
Download [public cloud IP addresses](https://www.microsoft.com/download/details.aspx?id=56519).
85-
86-
#### Azure US Government cloud
87-
88-
Download [US Government cloud IP addresses](https://www.microsoft.com/download/details.aspx?id=57063).
89-
90-
#### Microsoft Azure operated by 21Vianet cloud
91-
92-
Download [China cloud IP addresses](https://www.microsoft.com/download/details.aspx?id=57062).
93-
94-
#### Addresses grouped by region (Azure public cloud)
95-
96-
Add the subdomain of the corresponding region to the Live Metrics URL from the [Outgoing ports](#outgoing-ports) table.
97-
98-
> [!NOTE]
99-
> As described in the [Azure TLS 1.2 migration announcement](https://azure.microsoft.com/updates/azuretls12/), Application Insights connection-string based regional telemetry endpoints only support TLS 1.2. Global telemetry endpoints continue to support TLS 1.0 and TLS 1.1.
100-
>
101-
> If you're using an older version of TLS, Application Insights will not ingest any telemetry. For applications based on .NET Framework see [Transport Layer Security (TLS) best practices with the .NET Framework](/dotnet/framework/network-programming/tls) to support the newer TLS version.
102-
103-
| Continent/Country | Region | Subdomain | IP |
104-
| --- | --- | --- | --- |
105-
|Asia|East Asia|eastasia|52.229.216.48/28<br/>20.189.111.16/29|
106-
||Southeast Asia|southeastasia|52.139.250.96/28<br/>23.98.106.152/29|
107-
|Australia|Australia Central|australiacentral|20.37.227.104/29<br/><br/>|
108-
||Australia Central 2|australiacentral2|20.53.60.224/31<br/><br/>|
109-
||Australia East|australiaeast|20.40.124.176/28<br/>20.37.198.232/29|
110-
||Australia Southeast|australiasoutheast|20.42.230.224/29<br/><br/>|
111-
|Brazil|Brazil South|brazilsouth|191.233.26.176/28<br/>191.234.137.40/29|
112-
||Brazil Southeast|brazilsoutheast|20.206.0.196/31<br/><br/>|
113-
|Canada|Canada Central|canadacentral|52.228.86.152/29<br/><br/>|
114-
|Europe|North Europe|northeurope|52.158.28.64/28<br/>20.50.68.128/29|
115-
||West Europe|westeurope|51.144.56.96/28<br/>40.113.178.32/29|
116-
|France|France Central|francecentral|20.40.129.32/28<br/>20.43.44.216/29|
117-
||France South|francesouth|20.40.129.96/28<br/>52.136.191.12/31|
118-
|Germany|Germany West Central|germanywestcentral|20.52.95.50/31<br/><br/>|
119-
|India|Central India|centralindia|52.140.108.216/29<br/><br/>|
120-
||South India|southindia|20.192.153.106/31<br/><br/>|
121-
|Japan|Japan East|japaneast|52.140.232.160/28<br/>20.43.70.224/29|
122-
||Japan West|japanwest|20.189.194.102/31<br/><br/>|
123-
|Korea|Korea Central|koreacentral|20.41.69.24/29<br/><br/>|
124-
|Norway|Norway East|norwayeast|51.120.235.248/29<br/><br/>|
125-
||Norway West|norwaywest|51.13.143.48/31<br/><br/>|
126-
|Qatar|Qatar Central|qatarcentral|20.21.39.224/29<br/><br/>|
127-
|South Africa|South Africa North|southafricanorth|102.133.219.136/29<br/><br/>|
128-
|Switzerland|Switzerland North|switzerlandnorth|51.107.52.200/29<br/><br/>|
129-
||Switzerland West|switzerlandwest|51.107.148.8/29<br/><br/>|
130-
|United Arab Emirates|UAE North|uaenorth|20.38.143.44/31<br/>40.120.87.204/31|
131-
|United Kingdom|UK South|uksouth|51.105.9.128/28<br/>51.104.30.160/29|
132-
||UK West|ukwest|20.40.104.96/28<br/>51.137.164.200/29|
133-
|United States|Central US|centralus|13.86.97.224/28<br/>20.40.206.232/29|
134-
||East US|eastus|20.42.35.32/28<br/>20.49.111.32/29|
135-
||East US 2|eastus2|20.49.102.24/29<br/><br/>|
136-
||North Central US|northcentralus|23.100.224.16/28<br/>20.49.114.40/29|
137-
||South Central US|southcentralus|20.45.5.160/28<br/>13.73.253.112/29|
138-
||West US|westus|40.91.82.48/28<br/>52.250.228.8/29|
139-
||West US 2|westus2|40.64.134.128/29<br/><br/>|
140-
||West US 3|westus3|20.150.241.64/29<br/><br/>|
141-
142-
#### Upcoming regions (Azure public cloud)
143-
144-
> [!NOTE]
145-
> The following regions are not supported yet, but will be added in the near future.
146-
147-
| Continent/Country | Region | Subdomain | IP |
148-
| --- | --- | --- | --- |
149-
|Canada|Canada East|TBD|52.242.40.208/31<br/><br/>|
150-
|Germany|Germany North|TBD|51.116.75.92/31<br/><br/>|
151-
|India|West India|TBD|20.192.84.164/31<br/><br/>|
152-
||Jio India Central|TBD|20.192.50.200/29<br/><br/>|
153-
||Jio India West|TBD|20.193.194.32/29<br/><br/>|
154-
|Israel|Israel Central|TBD|20.217.44.250/31<br/><br/>|
155-
|Poland|Poland Central|TBD|20.215.4.250/31<br/><br/>|
156-
|South Africa|South Africa West|TBD|102.37.86.196/31<br/><br/>|
157-
|Sweden|Sweden Central|TBD|51.12.25.192/29<br/><br/>|
158-
||Sweden South|TBD|51.12.17.128/29<br/><br/>|
159-
|Taiwan|Taiwan North|TBD|51.53.28.214/31<br/><br/>|
160-
||Taiwan Northwest|TBD|51.53.172.214/31<br/><br/>|
161-
|United Arab Emirates|UAE Central|TBD|20.45.95.68/31<br/><br/>|
162-
|United States|West Central US|TBD|52.150.154.24/29<br/><br/>|
163-
164-
### Discovery API
165-
166-
You might also want to [programmatically retrieve](../virtual-network/service-tags-overview.md#use-the-service-tag-discovery-api) the current list of service tags together with IP address range details.
53+
For more information on availability tests, see [Private availability testing](./app/availability-private-test.md).
16754

16855
## Application Insights and Log Analytics APIs
16956

0 commit comments

Comments
 (0)