Amazon CloudWatch Omni now collects Azure logs, metrics and traces
AWS added Microsoft Azure support to Amazon CloudWatch Omni, covering resource logs, platform metrics, flow logs and Application Insights traces. Teams on both clouds view Azure and AWS telemetry in one place.
By JetherVerse News

Amazon Web Services announced on November 21, 2026 Microsoft Azure support in Amazon CloudWatch Omni. The service now collects Azure resource logs, Azure Monitor platform metrics, virtual network flow logs and traces from Application Insights.
Teams with workloads on both AWS and Azure no longer need separate monitoring tools or custom pipelines to see the whole environment. Central operations, DevOps and site reliability engineering teams view Azure telemetry beside AWS telemetry in one place. AWS gives an example: during an incident, an engineer traces a slow request from an Azure-hosted service to its AWS dependencies without switching consoles.
Setup starts with a connection between a Microsoft Entra ID tenant and your AWS account and Region. You then choose the telemetry types, subscriptions, Azure regions, resource types and tags to collect. Azure data lands in Amazon CloudWatch, and Omni spaces monitor applications and infrastructure across cloud providers. You configure the connectors in the CloudWatch Omni console or with the AWS CLI. Collection works in all Azure Public Regions, and data goes to every region where CloudWatch Omni is available. AWS points to the CloudWatch Omni User Guide for steps and to its pricing page for costs. The announcement does not list a price.
Why this matters: many companies run more than one cloud, often by choice and sometimes through acquisitions or client demands. Each extra monitoring tool adds cost, training and gaps between dashboards. A single view shortens the time to find which side of the cloud boundary caused a fault. For agencies and software teams serving clients on Azure and AWS, one telemetry layer means fewer tabs and fewer handoffs during an outage.
Check pricing before you connect Azure data, since ingest volume drives monitoring bills on any platform. Start with one subscription and a short list of resource types, then expand.
Read the full report at Amazon Web Services.
Source: Amazon Web Services
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

