[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector
What the source says
Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Urgency: Monitor
Next action: Review affected accounts with the customer using the official announcement.
Commercial opportunities
Use the verified change to open a scoped customer conversation.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
The affected customer scope is unknown and must be confirmed before action.
Reading for it_manager_dsi
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Urgency: Monitor
Next action: Assess technical dependencies and ownership against the official update.
Commercial opportunities
Offer a scoped technical-readiness assessment if the customer confirms impact.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
The affected customer scope is unknown and must be confirmed before action.
Reading for partner_channel
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Urgency: Monitor
Next action: Prepare a source-backed customer conversation and confirm the affected estate.
Commercial opportunities
Qualify a partner-led assessment only after customer scope is confirmed.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
The affected customer scope is unknown and must be confirmed before action.
Reading for sales_manager
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces usin
Urgency: Monitor
Next action: Review portfolio exposure with account owners using the official source.
Commercial opportunities
Prioritize accounts that confirm affected products or workloads.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
The affected customer scope is unknown and must be confirmed before action.
Evidence and traceability
Each excerpt is linked to the primary source. Current raw version: 496.
Raw capture : 2026-08-26T14:18:57.653130+00:00 — hash 312623c6b959a07f…
Event
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.
[Launched] Generally Available: Ingest OTLP signals into Azure Monitor with the OpenTelemetry Collector Azure Monitor's support for native ingestion of OpenTelemetry Protocol (OTLP) signals is now generally available. This enables you to send telemetry data directly from OpenTelemetry-instrumented applications and platforms to Azure Monitor. You can configure your OpenTelemetry Collector to send data directly to Azure Monitor cloud ingestion endpoints to ingest OTLP metrics, logs and traces using Microsoft Entra for authentication. You can enable OTLP data ingestion in Azure Monitor using Application Insights OR by manually creating the required data collection endpoints, rules and workspaces. The Application Insights-based approach is recommended for most scenarios as it automates resource creation and includes built-in application performance management experiences. Ingested OTLP metrics are stored in Azure Monitor Workspaces and can be queried and alerted upon with Prometheus query language (PromQL). OTLP logs and traces are stored in Log Analytics workspaces using new OpenTelemetry tables and semantics. Learn more.