This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
On 31 March 2025, technical support for instrumentation key–based global ingestion in the Application Insights feature of Azure Monitor will end. Your Applications Insights resources will continue to receive data, but instrumentation key-based global ingestion will no longer receive any updates, bug fixes, or customer support.
After migrated to use connection strings instead of instrumentation key, the View Application Insights data => option is not available anymore because the APPLICATIONINSIGHTS_CONNECTION_STRING app setting has been added in app configuration, and the APPINSIGHTS_INSTRUMENTATIONKEY one has been removed already.
I think the Azure portal needs to be updated to reflect this transition to use connection strings of Application Insights.
With APPINSIGHTS_INSTRUMENTATIONKEY app setting:
Without APPINSIGHTS_INSTRUMENTATIONKEY app setting:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 12%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
Hi @bharathn-msft I have Application-insights resource with connection string "InstrumentationKey=00000000-0000-0000-0000-000000000000;IngestionEndpoint=https://{region}.in.applicationinsights.azure.com/;LiveEndpoint=https://{region}.livediagnostics.monitor.azure.com/"
as per the https://learn.microsoft.com/en-us/azure/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings documentation we need to use connection string instead of instrumentation key however connection string contains instrumentation key. so, If i have application insights resource with the above format does it mean that we need not to do anything. can you please help to understand better ?
To migrate to connection strings, please follow the steps outlined in this guide.
If you have any additional queries regarding this retirement, please use comments on this thread to ask your specific queries and we will try our best to answer those queries. Thank You!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 79%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
The documentation on using connection strings has examples using a connection string with an instrumentation key, but no region-specific endpoint. Will that style of connection string still be supported past 31 March 2025, or is an IngestionEndpoint required in the connection string to continue to receive support?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 46%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Do we have to use the Connection String in AD B2C custom policies?
In other words, is this setup going to change?
Cristian.