CloudWatch Omni Adds Azure Logs, Metrics, and Traces (2026)

Abstract illustration of two telemetry streams merging into a central CloudWatch observatory

Written by

in

Takeaway: On November 21, 2026, AWS said Amazon CloudWatch Omni now supports collecting Azure resource logs, Azure Monitor platform metrics, virtual network (VNet) flow logs, and traces from Application Insights. Teams that run workloads on both AWS and Azure can view that Azure telemetry alongside their AWS telemetry in one place, including in Omni spaces, without building a custom monitoring pipeline.

The details below come from that official What’s New post and from AWS’s Send platform telemetry from Microsoft Azure documentation. This is a collection path for Azure platform telemetry into CloudWatch, not a new standalone product, and it is separate from the Bedrock Web Search language and country-field update AWS also posted today.

What you can collect

AWS says CloudWatch can now collect four Azure signal types: resource logs, Azure Monitor platform metrics, VNet flow logs, and traces from Application Insights. After the data lands in CloudWatch, Omni spaces can monitor applications and infrastructure across the two cloud providers. The What’s New example is an incident in which you trace a slow request from an Azure-hosted service to its AWS dependencies without switching consoles.

The documentation calls this Azure vended telemetry: it brings in what Azure services already record about your resources. You do not install or run any software in Azure to collect it. Official docs also draw a clear line around application-level data: this path collects what Azure records about a resource, such as a virtual machine’s CPU metrics, and it does not collect telemetry from inside a virtual machine or from your application code. For that, AWS points you to the CloudWatch agent.

On traces, the What’s New post uses the phrase “traces from Application Insights.” The documentation is more specific. Traces are supported only for the microsoft.insights/components resource type. Only that resource’s AppRequests and AppDependencies records become spans; other records, such as AppTraces, become log events. To collect traces, Transaction Search must be enabled in the AWS account and Region.

How setup works

To get started, AWS says you connect a Microsoft Entra ID tenant to your AWS account and Region, then choose the telemetry types, subscriptions, Azure regions, resource types, and tags to collect. You can set up the connectors in the CloudWatch Omni console or with the AWS CLI.

The documentation describes the same two paths. In the Omni web UI, a three-step wizard is available under Settings › Ingestion, with Azure as the cloud provider and Platform telemetry as the source; only a Space Admin can complete that setup in the UI. The AWS CLI path uses the same setup scripts and APIs, including a generated Bicep template that creates collection resources in Azure and a telemetry pipeline that reads from Azure and writes to CloudWatch.

AWS says no Azure secret or key is stored. CloudWatch signs in to Microsoft Entra ID with workload identity federation. Official docs also say you connect a given Azure tenant once per AWS account and Region, and that the telemetry scope can include tag filters. Those filters are exact match only and case-sensitive; exclude, prefix, and wildcard filters are not supported. You can name up to 100 resource types in a scope entry, and there is no option to select all types. Resources in the global location, such as Azure Front Door, are not supported. AWS publishes the full supported resource type list in the documentation linked above.

Availability, limits, and pricing

The What’s New post says Azure telemetry collection is available in all Azure Public Regions and can be ingested to all Regions where CloudWatch Omni is available. The documentation uses equivalent wording: the Azure public cloud on the Azure side, and every AWS Region where CloudWatch Omni is available on the AWS side. This article does not reproduce that Region list; AWS points readers to its Supported Regions documentation for CloudWatch Omni.

The documentation also lists service limits that the What’s New post does not repeat, including one connection per Azure tenant in an account and Region, 50 connections per account and Region, and a cap of 1,000 metric series per metric per resource, with additional series not collected. Metrics arrive about four minutes or more after Azure records them, at one-minute granularity at best. New resources are picked up within an hour, with no earlier history.

The What’s New post does not publish a price for Azure telemetry. It points to the CloudWatch Omni pricing page, which says standard CloudWatch rates apply for ingestion and storage. Official docs also warn that Azure charges apply for Event Hubs and storage created by setup, and that deleting the connection in CloudWatch does not remove those Azure resources; charges continue until you delete them.

What AWS did not announce

The November 21 post does not add a new Azure compute or networking service, and it does not say CloudWatch Omni replaces Azure Monitor. It also does not claim that every Azure resource type is supported, or that in-guest and application telemetry are included. For local testing of AWS APIs, we previously covered the AWS Emulator; this announcement is about live CloudWatch collection from Azure, not a local emulator.

Key facts

ItemWhat official sources say
AnnouncementAWS What’s New post, dated November 21, 2026.
ProductAmazon CloudWatch Omni, collecting Azure platform telemetry into CloudWatch.
SignalsAzure resource logs, Azure Monitor platform metrics, VNet flow logs, and traces from Application Insights.
Trace detailDocumented only for microsoft.insights/components. Only AppRequests and AppDependencies become spans; AppTraces become log events. Transaction Search must be enabled to collect traces.
What is not includedTelemetry from inside a virtual machine or from your application code. No software is installed in Azure for this platform path.
How to startConnect a Microsoft Entra ID tenant to an AWS account and Region, then choose telemetry types, subscriptions, Azure regions, resource types, and tags. Omni web UI or AWS CLI and setup scripts.
AuthenticationNo Azure secret or key is stored. CloudWatch uses workload identity federation with Microsoft Entra ID.
AvailabilityAll Azure Public Regions, ingested to all AWS Regions where CloudWatch Omni is available.
PricingWhat’s New points to the CloudWatch Omni pricing page (standard CloudWatch ingestion and storage rates). Azure Event Hubs and storage charges continue until those Azure resources are deleted.

FAQ

What did AWS announce on November 21, 2026?

AWS said Amazon CloudWatch Omni now supports collecting Azure resource logs, Azure Monitor platform metrics, VNet flow logs, and traces from Application Insights, so teams can view Azure telemetry alongside AWS telemetry in one place.

Do you have to install an agent in Azure?

Not for this platform telemetry path. Official documentation says you do not install or run any software in Azure to collect vended telemetry. The CloudWatch agent is the documented path for telemetry from inside a virtual machine or from your application code.

Which traces are included?

The What’s New post describes traces from Application Insights. The documentation says traces are supported only for microsoft.insights/components, and that only AppRequests and AppDependencies records become spans. Other records, such as AppTraces, become log events.

How do you connect Azure to CloudWatch?

AWS says you connect a Microsoft Entra ID tenant to your AWS account and Region, then choose the telemetry types, subscriptions, Azure regions, resource types, and tags to collect. Setup is available in the CloudWatch Omni console or with the AWS CLI and setup scripts.

Are Azure credentials stored in AWS?

AWS says no Azure secret or key is stored. CloudWatch signs in to Microsoft Entra ID with workload identity federation.

Which Regions are supported?

AWS says collection is available in all Azure Public Regions and can be ingested to all AWS Regions where CloudWatch Omni is available. This article does not list those AWS Regions; see AWS’s Supported Regions documentation for CloudWatch Omni.

Is every Azure resource type supported?

No. AWS publishes a supported resource type list, and the telemetry scope has no option to select all types. Resources in the global location, such as Azure Front Door, are not supported.

Did AWS publish a price for Azure telemetry?

The What’s New post does not state a price. It points to the CloudWatch Omni pricing page, which says standard CloudWatch rates apply for ingestion and storage. Official docs also say Azure charges for Event Hubs and storage continue until you delete those Azure resources.

Comments

Leave a Reply