Skip to content

Commit 08710a6

Browse files
edits
1 parent 3a3e779 commit 08710a6

File tree

2 files changed

+1
-2
lines changed

2 files changed

+1
-2
lines changed

articles/azure-monitor/app/asp-net.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ This procedure configures your ASP.NET web app to send telemetry to the [Applica
1717
1818
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
1919

20-
2120
## Prerequisites
2221
To add Application Insights to your ASP.NET website, you need to:
2322

articles/azure-monitor/app/custom-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions, devx-track-js
1212
To send data from Application Insights to certain regions, you'll need to override the default endpoint addresses. Each SDK requires slightly different modifications, all of which are described in this article. These changes require adjusting the sample code and replacing the placeholder values for `QuickPulse_Endpoint_Address`, `TelemetryChannel_Endpoint_Address`, and `Profile_Query_Endpoint_address` with the actual endpoint addresses for your specific region. The end of this article contains links to the endpoint addresses for regions where this configuration is required.
1313

1414
> [!NOTE]
15-
> [Connection strings](./sdk-connection-string.md?tabs=net) are the new preferred method of setting custom endpoints within Application Insights.
15+
> [Connection strings](./sdk-connection-string.md?tabs=net) are the new preferred method of setting custom endpoints within Application Insights.
1616
1717
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
1818
git

0 commit comments

Comments
 (0)