A glowing network operations visualization links data centers to cloud infrastructure, with monitoring dashboards highlighting system alerts.
Azure Network Watcher has a new public-preview tool for a long-running hybrid-networking problem. The tool is Connection analyzer for ExpressRoute circuits. Its job is to show whether packet loss between Azure and on-premises begins at Microsoft's edge or somewhere else.

A glowing network operations visualization links data centers to cloud infrastructure, with monitoring dashboards highlighting system alerts. What Microsoft announced​

The Azure Updates entry (ID 578617) was published on November 17, 2026. The Azure Updates page itself returned only its generic shell when we retrieved it, so the feature description below comes from an independent listing of the same update, 365Fanatic Cloud. That listing carries the update's title and ID. Check the Microsoft entry once it renders in full.

According to that listing, the analyzer addresses a familiar complaint. When customers see packet loss between Azure and on-premises, it's hard to tell whether the cause is the Microsoft Enterprise Edge (MSEE), the connectivity provider, or the customer's own network. That uncertainty tends to produce long back-and-forth investigations.

The described mechanism:

  • It runs on-demand iPerf test traffic from an Azure virtual machine to an on-premises destination, over the ExpressRoute circuit.
  • It captures packets at the MSEE.
  • It reports whether packet loss is occurring at the MSEE and flags out-of-order packet delivery.
  • It makes the full packet capture (pcap) available to download for deeper analysis.

The listing says the feature was built specifically for Azure-to-on-premises traffic. It is not a general-purpose path tester.

Why the MSEE matters​

Microsoft's own ExpressRoute troubleshooting documentation defines the MSEE as the edge of the Microsoft network, the first point of contact into it and the last hop when leaving it. The same documentation says the MSEE isn't in the Azure cloud, because ExpressRoute sits at the edge of the Microsoft network. That is why packet-level evidence at this point is useful. If the capture shows loss at the MSEE, you have something concrete to hand to Microsoft. If it doesn't, the listing says you can narrow your focus to the provider or your own network.

Until now, teams had to piece this together by hand. Microsoft's existing guide describes counting packets arriving at and leaving the Microsoft edge on the MSEE devices. It also says that when matches are seen on both MSEEs, that indicates healthy traffic, and any loss is downstream from the MSEEs. The new analyzer appears to turn that kind of reasoning into a packaged, on-demand test with a downloadable capture.

How it differs from Connection Monitor​

Don't confuse this with continuous monitoring. Connection Monitor checks connectivity at regular intervals across Azure and hybrid endpoints and reports aggregated packet loss, latency and status codes. The new analyzer, as described, runs on demand and focuses on localizing loss at one point. In practice the two should complement each other:

  1. Use Connection Monitor or ExpressRoute metrics to notice degradation over time.
  2. Use the analyzer to produce packet-level evidence when you're trying to assign responsibility.

Our read is that the analyzer is a fault-isolation tool, not an early-warning system.

What the API reference shows​

The Microsoft Learn REST reference for Network Watcher Connection Analyzers (API version 2026-01-01) shows that the resource exists in the management API. It supports creating or updating a connection analyzer under a Network Watcher resource. Its documented diagnostic operation types include NextHop, NSG, PortScan, ConnectivityCheck and ExpressRouteDiagnostic.

The reference also documents ExpressRoute-specific settings for the ExpressRouteDiagnostic operation: the resource ID of the ExpressRoute circuit, and a bandwidth value in Mbps. Results are written to a storage account that you specify.

The reference's worked example is a generic ConnectivityCheck from a VM to an external address,. It is not the ExpressRoute workflow. This reference does not prove how the ExpressRoute test behaves. The listing's description of the iPerf test and MSEE capture also hasn't been matched to API fields, so we aren't mapping one to the other.

Preview caveats​

Microsoft's Azure Updates page defines "In preview" as available to all Azure customers for non-production use and testing, which is the Azure Updates wording, not this feature's terms. The independent listing gives a preview start of November 30, 2026, which we couldn't confirm on Microsoft's own page.

The announcement text we could retrieve doesn't cover several things:

  • Required permissions
  • Supported regions
  • Circuit prerequisites
  • Test duration or traffic volume
  • Pricing
  • Capture retention
  • Known limitations

Plan around those gaps. Iperf-style tests generate real traffic over a paid circuit, and the bandwidth parameter in the API suggests you choose the test rate. Run any early tests in a maintenance window, and start low until Microsoft documents the impact.

Practical guidance​

  • Use it when the symptom is packet loss on Azure-to-on-premises traffic over ExpressRoute, and you can reach an on-premises endpoint to test against.
  • Keep the evidence. Save the loss report and the pcap with your incident record, then compare them with your provider's and your own telemetry.
  • Don't over-read a negative result. Loss that isn't at the MSEE points you to the provider or customer side. It doesn't tell you which.
  • Don't use it for production decisions yet. Preview status means you should confirm the applicable terms first.

If it works as described, the analyzer should cut down on the "your side, no, yours" exchanges that slow hybrid network troubleshooting. We'll know more once Microsoft publishes the full documentation.

 

References

  1. (In preview) Public Preview: Azure Network Watcher – Connection analyzer Azure Updates 2026-11-17T20:00:32Z
  2. Public Preview: Azure Network Watcher | 365Fanatic Cloud cloud.365fanatic.com
  3. Azure updates | Microsoft Azure azure.microsoft.com