Azure Monitor Expands OpenTelemetry Support: What This Means for Multi-Cloud Observability

Microsoft has announced the public preview of OpenTelemetry Protocol (OTLP) support in Azure Monitor, a significant development for organizations seeking standardized observability across multi-cloud environments. This enhancement allows teams to send OpenTelemetry logs, metrics, and traces directly to Azure Monitor, centralizing telemetry data from diverse sources while maintaining the flexibility of open standards.

What's New in the Preview

The public preview introduces several key capabilities that bridge the gap between open-source observability tools and Azure's managed services:

• Direct OTLP ingestion for logs, metrics, and traces
• Automated onboarding for Azure Kubernetes Service (AKS) workloads
• Application Insights integration for distributed tracing and performance monitoring
• Pre-built Grafana dashboards for quick visualization
• Prometheus-compatible metric storage and querying
• OpenTelemetry semantic conventions ensuring standardized schema

This integration represents Microsoft's strategic response to the industry's shift toward OpenTelemetry as the de facto standard for telemetry collection. By supporting OTLP natively, Azure Monitor positions itself as a more attractive option for organizations with hybrid or multi-cloud strategies.

Implementation Paths

The preview offers multiple ingestion paths to accommodate different deployment scenarios:

For AKS Environments

Organizations running workloads on Azure Kubernetes Service can leverage automated instrumentation. The Azure Monitor OpenTelemetry distribution supports auto-instrumentation for Java and Node.js applications, with limited preview support for .NET and Python. This approach minimizes configuration overhead while providing comprehensive observability out of the box.

For Virtual Machines and Azure Arc

For traditional virtual machines, VM scale sets, and Azure Arc-enabled compute resources, the Azure Monitor Agent (AMA) serves as the ingestion point. The agent receives OTLP signals from applications and exports them to Azure Monitor, maintaining compatibility with existing monitoring deployments while adding OpenTelemetry support.

For Any Environment

The most flexible option leverages the OpenTelemetry Collector, a vendor-agnostic component that can receive OTLP signals from any source and export them directly to Azure Monitor's cloud ingestion endpoints. This approach is ideal for hybrid environments or those with strict networking requirements.

Technical Architecture

Under the hood, Azure Monitor handles telemetry data differently based on type:

• Metrics are stored in Azure Monitor Workspaces, which provide a Prometheus-compatible metrics store
• Logs and traces are stored in Log Analytics workspaces using a schema based on OpenTelemetry semantic conventions
• Application Insights enhances this data with distributed tracing capabilities and end-to-end performance investigations

The integration includes an Application Map specifically designed for OpenTelemetry signals, providing visual representations of dependencies and performance characteristics across distributed systems.

Enhanced Visualization Capabilities

A notable addition is the Application Map specifically designed for OpenTelemetry signals. This visual tool provides representations of dependencies and performance characteristics across distributed systems, enabling teams to identify bottlenecks and unusual patterns at a glance. The Application Map leverages the standardized schema from OpenTelemetry semantic conventions to ensure consistent visualization regardless of the source environment.

Competitive Landscape

Microsoft's move to support OpenTelemetry positions Azure Monitor against other cloud providers' observability solutions:

• Amazon Web Services offers OpenTelemetry support through Amazon Managed Service for Prometheus and Amazon CloudWatch, though integration requires additional components
• Google Cloud Platform provides OpenTelemetry integration through Cloud Monitoring, with varying levels of support across different services
• Unlike some competitors, Azure's approach maintains Application Insights as a distinct layer, providing both standardization and enhanced visualization capabilities

This support for open standards addresses a common concern about vendor lock-in, allowing organizations to instrument applications once and maintain telemetry portability across environments.

Business Impact

The introduction of OTLP support in Azure Monitor delivers several business benefits:

Standardization and Portability

By instrumenting applications with OpenTelemetry, organizations establish a consistent telemetry approach that remains portable across environments. This eliminates the need for multiple instrumentation strategies when moving workloads between on-premises, different cloud providers, or hybrid setups.

Operational Efficiency

The reduction in custom exporters and proprietary pipelines translates to lower maintenance overhead. Teams can focus on deriving insights rather than managing complex telemetry infrastructure.

Faster Troubleshooting

The correlation of metrics, logs, and traces within Azure Monitor's interface accelerates the debugging process. When alerts occur, teams can trace issues from symptoms to root causes with fewer context switches and less guesswork.

Reduced Time to Value

Pre-built Grafana dashboards and Application Insights integrations provide immediate value without requiring extensive customization. This is particularly valuable for organizations adopting observability practices or expanding their monitoring capabilities.

Migration Considerations

Organizations considering this preview should evaluate several factors:

Existing Investments

Teams with substantial investments in Application Insights or Azure Monitor will benefit most from this integration, as it enhances rather than replaces existing tools. For those heavily invested in other observability platforms, the migration path should be carefully evaluated.

Skill Requirements

While OpenTelemetry abstracts much of the complexity, teams should assess their familiarity with observability concepts, distributed tracing, and metrics collection. The learning curve may be steeper for organizations new to modern observability practices.

Cost Implications

The preview doesn't specify pricing changes, but organizations should consider how storing telemetry in Azure Monitor Workspaces and Log Analytics workspaces will impact their overall Azure costs, particularly for high-volume telemetry environments.

Getting Started

Microsoft provides several entry points for organizations to explore the preview:

1. For AKS workloads, the Azure Monitor OpenTelemetry distribution offers automated instrumentation
2. For VMs and Azure Arc-enabled resources, the Azure Monitor Agent provides OTLP support
3. For any environment, the OpenTelemetry Collector serves as a universal ingestion point

Each approach has detailed documentation and getting started guides available through Microsoft's resources.

Future Outlook

This preview represents Microsoft's commitment to supporting open standards while enhancing its observability offerings. Future developments may include expanded language support, deeper integration with Azure's AI capabilities, and enhanced automation for telemetry pipeline management.

For organizations with hybrid or multi-cloud strategies, this support for OpenTelemetry in Azure Monitor simplifies observability architecture while maintaining the flexibility to adapt to changing requirements. As the telemetry landscape continues to evolve, Microsoft's approach balances open standards with managed services, offering a compelling option for enterprises seeking both flexibility and ease of use.

Organizations interested in exploring this preview should evaluate their specific telemetry requirements, consider their existing monitoring investments, and plan a phased approach to adoption that balances innovation with stability.