Merge pull request #193802 from AaronMaxwell/aaronmax-remove-dupe-info-notices

Aaronmax remove dupe info notices

Author: PRMerger13

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

@@ -47,9 +47,6 @@ The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Micro
 - A functioning ASP.NET Core application. If you need to create an ASP.NET Core application, follow this [ASP.NET Core tutorial](/aspnet/core/getting-started/).
 - A valid Application Insights connection string. This string is required to send any telemetry to Application Insights. If you need to create a new Application Insights resource to get a connection string, see [Create an Application Insights resource](./create-new-resource.md).
 
-> [!IMPORTANT]
-> [Connection Strings](./sdk-connection-string.md?tabs=net) are recommended over instrumentation keys. New Azure regions require using connection strings instead of instrumentation keys. Connection strings identify the appropriate endpoint for your Application Insights resource which provides the fastest way to ingest your telemetry for alerting and reporting. You will need to copy the connection string and add it to your application's code or to an environment variable.
-
 ## Enable Application Insights server-side telemetry (Visual Studio)
 
 For Visual Studio for Mac, use the [manual guidance](#enable-application-insights-server-side-telemetry-no-visual-studio). Only the Windows version of Visual Studio supports this procedure.

articles/azure-monitor/app/create-new-resource.md

@@ -46,9 +46,6 @@ When your app has been created, a new pane opens. This pane is where you see per
 
 The instrumentation key identifies the resource that you want to associate your telemetry data with. You will need to copy the instrumentation key and add it to your application's code.
 
-> [!IMPORTANT]
-> [Connection Strings](./sdk-connection-string.md) are recommended over instrumentation keys. New Azure regions **require** the use of connection strings instead of instrumentation keys. Connection string identifies the resource that you want to associate your telemetry data with. It also allows you to modify the endpoints your resource will use as a destination for your telemetry. You will need to copy the connection string and add it to your application's code or to an environment variable.
-
 ## Install the SDK in your app
 
 Install the Application Insights SDK in your app. This step depends heavily on the type of your application.

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

@@ -11,9 +11,6 @@ ms.custom: references_regions, devx-track-js
 
 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.
 
-> [!NOTE]
-> [Connection strings](./sdk-connection-string.md?tabs=net) are the new preferred method of setting custom endpoints within Application Insights.   
-
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
 
 

articles/azure-monitor/app/java-2x-get-started.md

@@ -25,8 +25,6 @@ Application Insights is an extensible analytics service for web developers that
 
 ## Get an Application Insights instrumentation key
 
-> [!IMPORTANT]
-> [Connection Strings](./sdk-connection-string.md?tabs=java) are recommended over instrumentation keys. New Azure regions **require** the use of connection strings instead of instrumentation keys. Connection string identifies the resource that you want to associate your telemetry data with. It also allows you to modify the endpoints your resource will use as a destination for your telemetry. You will need to copy the connection string and add it to your application's code or to an environment variable.
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 2. In the Azure portal, create an Application Insights resource. Set the application type to Java web application.
 

includes/azure-monitor-instrumentation-key-deprecation.md

@@ -11,4 +11,4 @@ ms.custom: "include file"
 ---
 
 >[!NOTE] 
->On March 31st, 2025, support for instrumentation key ingestion will end. Instrumentation key ingestion will continue to work, but we’ll no longer provide updates or support for the feature. [Transition to connection strings](../articles/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings.md) to remain supported.
+>On March 31st, 2025, support for instrumentation key ingestion will end. Instrumentation key ingestion will continue to work, but we’ll no longer provide updates or support for the feature. [Transition to connection strings](../articles/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings.md) to remain supported and take advantage of new capabilities.