An engineer monitors server connections and performance as data flows to a cloud platform.
Azure ExpressRoute Direct is getting a long-requested capability. Microsoft has put link groups into public preview, so administrators can bundle several physical links into one logical connection. The Azure Updates entry is dated November 17, 2026. It is aimed at network architects running high-throughput private connectivity into Azure, not at the average Windows desktop admin.

An engineer monitors server connections and performance as data flows to a cloud platform. What Microsoft announced​

Azure ExpressRoute is introducing link groups for ExpressRoute Direct. The pitch is to let high-throughput workloads scale connectivity while reducing operational complexity. Instead of managing several independent ExpressRoute connections, you aggregate multiple physical links into a single logical connection. Microsoft's announcement lists four capabilities:

  • Scale: group multiple ExpressRoute Direct links into one logical connection to increase capacity.
  • Resiliency: use Link Aggregation Control Protocol (LACP), including dynamic link negotiation and failover.
  • Simpler operations: manage and monitor aggregated connectivity at the group level, not per connection.
  • Availability tuning: configure the minimum number of active links the group needs in order to remain operational.

The update carries the "In preview" label. Microsoft's Azure Updates page defines that status as available to all Azure customers, but for non-production use and testing. "Launched" is the label for fully released, production-ready features.

Why this is a notable shift​

Until now, Microsoft's own documentation has been explicit about the limitation. The ExpressRoute Direct overview states that the service doesn't support Link Aggregation Control Protocol (LACP) or Multi-Chassis Link Aggregation (MLAG). That page predates the preview. The link groups announcement is the first sign that Microsoft is moving toward LACP-based bundling for this product. I haven't seen Microsoft Learn pages updated to describe link groups.

A GitHub issue in the Azure CLI repository also hints at tooling. It describes ExpressRoute "LAG" resource management, including link and member queries and Letter of Authorization generation. The issue notes a minimum API version of 2025-09-01 and describes an LACP timer with Fast or Slow options. It is an engineering tracking item, not a Microsoft deployment guide. I'd treat it as a clue about how the feature is exposed, not as confirmed behavior. The issue's reference to "LAG" resources is my inference for how link groups map to the API, and Microsoft hasn't confirmed that mapping in the material I reviewed.

How it compares with the existing model​

Today's setup revolves around a port pair. Microsoft's configuration guide shows an ExpressRoute Direct resource with two links, link1 and link2. Administrators enable each one and then create circuits on the resource. Microsoft's FAQ describes the service as offering dual 100 Gbps or 10-Gbps connectivity-class port pairs. The FAQ lists massive data ingestion, physical isolation for regulated markets, and dedicated burst capacity such as rendering as the scenarios that benefit most.

The concept isn't unique to Microsoft. AWS Direct Connect has offered link aggregation groups for some time. AWS describes a LAG as a logical interface that uses LACP to aggregate multiple connections at a single endpoint. AWS also lists a minimum-links setting, which controls how many links must be active for the bundle to pass traffic. Microsoft's announced minimum-active-links option appears to serve the same purpose. The comparison is conceptual, and Microsoft's implementation details may differ. AWS also requires all LAG connections to use the same bandwidth and terminate at the same endpoint, and Microsoft hasn't published equivalent rules.

What is not yet known​

The announcement is thin on specifics. None of the following has been published in the sources I reviewed:

  • Maximum links per group or supported link speeds and mixtures.
  • Exact failover behavior and what happens when the group falls below its minimum.
  • How traffic is distributed across member links.
  • Portal, PowerShell, CLI and API availability, and supported regions.
  • Pricing, including whether grouping changes billing.
  • Preview limitations or any enrollment requirement.

Don't assume link groups change existing service rules. Microsoft's FAQ says port-pair billing starts 45 days after resource creation or when one or both links are enabled, whichever comes first. That's the current model. Nothing I found says grouping changes it. Likewise, existing circuit quotas and bandwidth accounting are documented for the current model, and the announcement doesn't say they change.

Practical guidance for administrators​

If you run ExpressRoute Direct, this is a feature to evaluate in a lab, not to deploy into production yet. A sensible approach, based on the announced capabilities and the preview status:

  1. Keep production on the documented model. Preview status means non-production use and testing.
  2. Confirm eligibility. Existing ExpressRoute Direct usage requires subscription enrollment, so check whether the preview has its own prerequisites.
  3. Decide your minimum-active-links value deliberately. Test what happens to traffic when links drop below it.
  4. Test link loss and recovery. Failover timing hasn't been quantified, so measure it against your own design.
  5. Check your carrier and colocation side. The physical cross-connects and your router's LACP support still have to line up.
  6. Verify billing before you enable extra links. Don't assume grouping is cost-neutral.

Bottom line​

Link groups address a real gap for customers who've outgrown a single port pair. They'd also bring Azure closer to how other cloud providers handle bundled dedicated connections. For now, the evidence is an announcement-level summary with no published limits, procedures or pricing. Watch for Microsoft Learn documentation and portal support before planning around it.

 

References

  1. (In preview) Public Preview: Scale ExpressRoute Direct connectivity with link groups Azure Updates 2026-11-17T20:15:03Z
  2. azure-docs/articles/expressroute/how-to-expressroute-direct-portal.md at main · MicrosoftDocs/azure-docs · GitHub github.com
  3. azure-docs/articles/expressroute/expressroute-erdirect-about.md at main · MicrosoftDocs/azure-docs · GitHub github.com