# Choose the OTLP transport for the actual Azure Monitor ingestion path

> Can the same OTLP protocol and port configuration be reused for AMA, AKS and Collector ingestion?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:53+00:00
- Modified: 2026-09-10T02:11:19+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Can the same OTLP protocol and port configuration be reused for AMA, AKS and Collector ingestion?

## Potentially affected

Nonproduction evaluations of Azure Monitor's preview OpenTelemetry ingestion paths.

## DSE recommendation

Document the application's immediate receiver and its required transport before copying an OTLP endpoint configuration.

## Article

## Source facts

Azure Monitor’s documented OpenTelemetry experience is preview and is not recommended for production workloads. Its AMA path uses local gRPC: port 4317 for metrics and 4319 for logs and traces. Port 4319 is AMA-specific, not a canonical OTLP port. The AKS integration supports HTTP/protobuf, not JSON or OTLP/gRPC, while the Collector’s Azure export also uses HTTP/protobuf. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data).

## Applicability

Use this comparison during a bounded preview evaluation. Identify each hop separately: an application’s connection to a local receiver and that receiver’s export to Azure are not automatically the same protocol contract.

## DSE recommendation

Document the application’s immediate receiver and its required transport before copying an OTLP endpoint configuration. Have the application and platform owners agree which ingestion path is being tested. Keep signal-specific endpoints explicit, and do not infer that a familiar port number makes gRPC and HTTP payloads interchangeable. Avoid changing network controls until the selected transport matches the documented receiver.

## Verification

Inspect the effective exporter endpoint, signal type and protocol in the test deployment. Send an approved identifiable sample through each intended signal path and check receiver errors as well as destination data. Record which hop accepted the sample and whether it reached the expected experience. A reachable socket alone is not the acceptance result; retain unresolved protocol mismatches before expanding the preview test.

## Official references

[Microsoft Learn: OpenTelemetry ingestion paths, preview](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data). Source reviewed September 9, 2026.

## Primary reference

- Name: Collect and analyze OpenTelemetry data with Azure Monitor (Preview) - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/containers/collect-use-observability-data
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose the OTLP transport for the actual Azure Monitor ingestion path,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-543-choose-the-otlp-transport-for-the-actual-azure-monitor-ingestion-path/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.