You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/ip-collection.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.reviewer: mmcc
8
8
9
9
# Geolocation and IP address handling
10
10
11
-
This article explains how geolocation lookup and IP address handling work in Application Insights.
11
+
This article explains how geolocation lookup and IP address handling work in [Application Insights](app-insights-overview.md#application-insights-overview).
12
12
13
13
## Default behavior
14
14
@@ -32,7 +32,14 @@ When IP addresses aren't collected, city and other geolocation attributes also a
32
32
>
33
33
> To learn more about handling personal data, see [Guidance for personal data](../logs/personal-data-mgmt.md).
34
34
35
-
To enable IP collection and storage, the `DisableIpMasking` property of the Application Insights component must be set to `true`. You can set this property through Azure Resource Manager templates (ARM templates) or by calling the REST API.
35
+
To enable IP collection and storage, the `DisableIpMasking` property of the Application Insights component must be set to `true`.
36
+
37
+
Options to set this property include:
38
+
39
+
-[ARM template](#arm-template)
40
+
-[Portal](#portal)
41
+
-[REST API](#rest-api)
42
+
-[PowerShell](#powershell)
36
43
37
44
### ARM template
38
45
@@ -100,7 +107,7 @@ If you need to modify the behavior for only a single Application Insights resour
100
107
101
108
The following [REST API](/rest/api/azure/) payload makes the same modifications:
0 commit comments