Request for Entra ID Support in Application Insights Integration

[LauraDamianTNA]

Technical Feedback

To enable tracing for agents, we need to connect the Foundry Project to Application Insights. Currently, the only supported authentication method is via a secret key.

Desired Outcome

Ideally, we would prefer to use Entra ID for authentication, similar to how it's done with Azure AI Search.

Current Workaround

Is there a plan to support Entra ID authentication for Application Insights in the future? Where can we follow updates on this feature?

[leestott]

Hi @LauraDamianTNA Microsoft Entra ID authentication is already supported for Application Insights ingestion and API access, so you’re not limited to secret keys anymore.

Current Support for Entra ID
You can now:

• Ingest telemetry using managed identities or service principals
• Query telemetry via the Application Insights API using OAuth2 flows (client credentials, auth code, etc.)
• Disable local authentication to enforce Entra-only access

This aligns with how Azure AI Search handles identity and is especially useful for secure, scalable agent-based architectures like Foundry.

SDK Limitations
Some SDKs still don’t support Entra ID, including:

• Application Insights JavaScript SDK
• OpenCensus Python SDK (v3.4/3.5)
• Profiler for .NET

For browser-based telemetry, Microsoft recommends using Azure API Management as a proxy to inject Entra-authenticated telemetry.

Stay Updated
You can track updates and roadmap items here:

• [Microsoft Learn: Entra Auth for Application Insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/azure-ad-authentication)
• [Azure Updates Portal](https://azure.microsoft.com/en-us/updates/)
• [Azure Monitor GitHub Discussions](https://github.com/microsoft/ApplicationInsights-dotnet/discussions)

[LauraDamianTNA]

Hi @leestott,
Thanks for your prompt answer.
My concern is the infrastructure code for creating this connection.

Connecting an Azure AI Foundry Porject to App Insights supports only API Key currently.

Other resources like AI Search support Entra ID.

We would prefer to use Entra ID for authentication in the infrastructure, similar to how it's done with Azure AI Search.