Azure Application Insights
azure.microsoft.com
- Free plan
- Windows
- Linux
- Web
- iPhone and iPad
- Android
- API
What Azure Application Insights is
Azure Application Insights collects and analyzes application telemetry as part of Azure Monitor. Teams can use alerts, metrics, logs, workbooks, Grafana dashboards, and investigation tools such as application maps, live metrics, transaction search, availability monitoring, failure analysis, and performance views. Usage analytics cover users, sessions, events, funnels, flows, and cohorts. For .NET applications, diagnostic options include profiling and a snapshot debugger for exceptions. Applications can send telemetry through supported OpenTelemetry scenarios; Microsoft recommends its Azure Monitor OpenTelemetry Distro for most code-based server-side setups and the Application Insights JavaScript SDK for browser telemetry. Telemetry is stored in a Log Analytics workspace, and the service can work with apps hosted outside Azure. A daily ingestion cap can pause collection until the next UTC day, while sampling can reduce data volume. The listed no-charge retention period is 90 days; retaining data longer is charged by volume. Pricing is on request, with usage-based ingestion and the first 5 GB per month per billing account free.
Who it suits
It suits teams that need application monitoring, diagnostics, and usage analytics across supported workloads, including applications hosted outside Azure. Teams with regional compliance needs should consider the regional endpoint guidance and browser teams should note the JavaScript SDK requirement.
Good to know, and what to watch
- Tracks users, sessions, events, funnels, flows, and cohorts.
- Includes application maps, transaction search, and failure analysis.
- Supports OpenTelemetry in supported scenarios.
- Entra ID and managed-identity telemetry authentication are supported.
- Daily ingestion caps and sampling offer volume controls.
- Global endpoint does not guarantee regional data residency.
- Browser OpenTelemetry JavaScript is unsupported and not recommended.
- Retention beyond 90 days is charged.
- Excess telemetry is ignored after the daily cap until next UTC day.
Plans
Every plan and pricePay-as-you-go (Azure Monitor Logs)
Pricing on request
The verdict
Application Insights combines telemetry collection, diagnostics, and usage analytics with several ways to control ingestion. Review endpoint choice, browser instrumentation, and retention charges against your requirements.
What the maker publishes
- Browser instrumentation limit
- The Application Insights JavaScript SDK is used for browser telemetry; Microsoft says OpenTelemetry JavaScript for browsers is unsupported and not recommended. source
- Code analysis
- For .NET applications, code analysis tools include a profiler and a snapshot debugger. source
- Code diagnostics
- Code analysis features include .NET profiling, AI code optimizations, and a snapshot debugger for exceptions in .NET applications. source
- Cost controls
- A daily data cap can stop ingestion after its limit is reached for the rest of the UTC day, and sampling can reduce telemetry volume. source
- Dashboards and alerts
- Application Insights supports alerts, metrics, logs, workbooks, and Grafana dashboards for monitoring and reporting. source
- Data handling
- Telemetry is stored in a Log Analytics workspace, and the FAQ says the service works with apps hosted anywhere, not only in Azure. source
- Data residency
- Microsoft says the global endpoint does not guarantee regional data residency and recommends regional Application Insights endpoints for regional compliance requirements. source
- Diagnostics
- Its investigation tools include application maps, live metrics, transaction search, availability monitoring, failure analysis, and performance views. source
- Founded
- 1975 source
- Headquarters
- Redmond, Washington, United States source
- Instrumentation
- Microsoft recommends the Azure Monitor OpenTelemetry Distro for most code-based server-side scenarios; browser apps use the Application Insights JavaScript SDK. source
- Integrations
- Documented integrations include Azure SDK tracing, Cosmos DB SDK observability, .NET OpenTelemetry, Azure Container Apps, Azure Data Explorer, and Azure AI Foundry. source
- Monitoring tools
- Its tools include alerts, metrics, logs, workbooks, Grafana dashboards, and SDK statistics. source
- OpenTelemetry
- For supported scenarios, applications can use vendor-neutral OpenTelemetry to collect telemetry for analysis in Application Insights. source
- Pricing model
- Azure Monitor pricing lists usage-based ingestion and other metered features; its pricing page displays some rates as "$-" rather than a numeric price. source
- Purpose
- Application Insights is an Azure Monitor service for collecting and analyzing application telemetry. source
- Retention limit
- The pricing page lists 90 days of no-charge retention for classic or workspace-based Application Insights data; longer retention is charged by retained data volume. source
- Security
- Application Insights supports Microsoft Entra ID authentication and can be configured to accept telemetry authenticated exclusively through managed identities and Entra ID. source
- Security
- Application Insights supports TLS 1.2 and 1.3, and Microsoft Entra authentication can restrict telemetry ingestion to authenticated identities. source
- Support
- Microsoft directs Azure technical support issues to Azure support tickets, general questions to Microsoft Q&A, and coding questions to Stack Overflow. source
- Support
- Microsoft recommends its Azure Monitor OpenTelemetry Distro for new projects and describes it as supported by Microsoft. source
- Supported workloads
- The documentation gives setup paths for web apps, virtual machines, JavaScript apps, Azure Functions, Kubernetes, and AI agents. source
- Usage limits
- Application Insights lets users set a daily ingestion cap; after the cap is reached, excess data is ignored until the next UTC day. source
- User analytics
- Usage features cover users, sessions, events, funnels, flows, and cohorts. source
Checked against the maker's pages on 7 Oct 2026.