🚀 Ready to transform your cloud infrastructure? Get Started →

AWS Interconnect multicloud guide showing a private MACsec-encrypted link between an AWS VPC and an Azure VNet.

AWS Interconnect Multicloud with Azure: Private AWS-to-Azure Links Made Simple

On 17 November 2026, AWS announced the general availability of AWS Interconnect – multicloud with Microsoft Azure. With this launch, AWS customers get one consistent way to build private, resilient connections from their Amazon VPCs to Microsoft Azure, Google Cloud and Oracle Cloud Infrastructure (OCI).

Until now, most teams running workloads on both AWS and Azure built a “do-it-yourself” network: Direct Connect on one side, ExpressRoute on the other, a colocation provider in the middle, cross-connects, VLANs and BGP sessions to maintain. This guide explains what AWS Interconnect – multicloud changes, how it works, what it costs and how to plan a rollout.

What Is AWS Interconnect – multicloud?

The AWS Interconnect User Guide describes AWS Interconnect as a family of managed private connectivity services. It has two offerings:

  • Interconnect – multicloud: connects your AWS VPCs directly to VPCs or VNets in other public clouds.
  • Interconnect – last mile: connects branch offices, data centers and remote locations to AWS through qualified delivery partners.

According to the AWS Interconnect – multicloud product page, AWS calls it the first purpose-built product of its kind. AWS and the other provider pre-provision capacity pools between their networks, so you do not configure physical or virtual routers, order cross-connects or manage BGP peering yourself. The API specification behind the service is open for other providers to adopt, which is why Azure, Google Cloud and OCI can all offer the same experience.

Why the Azure GA Matters

Microsoft Azure launched support for AWS Interconnect in public preview in August 2026, and the 17 November announcement made it generally available on the AWS side. At launch, Interconnect – multicloud with Azure is available in three AWS Regions:

  • us-east-1 (N. Virginia)
  • ap-southeast-2 (Sydney)
  • eu-central-1 (Frankfurt)

For organizations that run Microsoft 365, Entra ID or .NET workloads on Azure alongside data and analytics on AWS, this removes one of the hardest parts of a multicloud design: a private, high-bandwidth path between the two clouds that does not cross the public internet.

One thing to check before you plan: at the time of writing, Microsoft’s own documentation still labels the Azure side as Azure Multicloud Interconnect Preview, with a preview scope of 1 Gbps bandwidth and no Azure service or egress charge during preview. Confirm the current Azure status, limits and pricing for your subscription before you commit production traffic.

How AWS Interconnect – multicloud Works

Key building blocks

  • Interconnect: a single logical object in your AWS account that represents the redundant capacity to the other provider.
  • Attach point: on AWS, this is always a Direct Connect gateway. On the remote side, it is the provider’s router.
  • Activation key: a token created when one side starts the request. The other side uses it to accept, so both sides validate before resources are committed.

Built-in resiliency and encryption

Each Interconnect is provisioned across redundant devices in at least two physically separate facilities with independent power and networking. Multicloud connections use a four-connection model with Equal-Cost Multi-Path (ECMP) load balancing. Physical links between AWS routers and partner devices are encrypted with IEEE 802.1AE MACsec by default, and traffic is only sent while the encryption session is active. Traffic stays on the AWS global backbone until it is handed off directly to the other provider.

Which AWS networking services can attach?

Through the Direct Connect gateway, you can use Virtual Private Gateways, Transit Gateways or AWS Cloud WAN:

  • Virtual Private Gateways and Transit Gateways are Regional. They can only reach an Interconnect that is local to their Region.
  • Cloud WAN is global. Any Core Network Edge (CNE) can reach any Interconnect attached to the same Direct Connect gateway.

Step-by-Step: Create Your First Multicloud Interconnect

Based on the AWS getting started guide and Microsoft’s activation key guide, the flow looks like this:

  1. Plan the network. Choose Virtual Private Gateway, Transit Gateway or Cloud WAN, and review IP allocations so your VPC and VNet CIDRs do not overlap.
  2. Prepare a Direct Connect gateway. Create a new one or reuse an existing one as the attach point.
  3. Create the Interconnect in AWS. In the AWS Direct Connect console, choose AWS Interconnect, then Create new multicloud Interconnect. Select the provider, your source AWS Region, the destination region on the other cloud, bandwidth, the Direct Connect gateway and your account ID on the other provider.
  4. Copy the activation key. AWS sends the request to the provider and shows the key.
  5. Accept on Azure. In the Azure portal, under Hybrid connectivity, create a Multicloud Interconnect circuit with the Azure Multicloud Interconnect port type, and redeem the AWS activation key with matching provider, region and bandwidth.
  6. Connect your VNets. On Azure, connect virtual networks through an ExpressRoute gateway, since ExpressRoute is the underlying technology.
  7. Verify and monitor. The Interconnect attaches to your Direct Connect gateway. Check routing and propagation, then test traffic.

You can also start from the other provider and use Accept multicloud Interconnect in the AWS console with a key generated there. Everything can be done in the console, CLI or API.

Pricing: What You Pay on the AWS Side

The AWS Interconnect – multicloud pricing page sets out a simple model:

  • You pay hourly per Interconnect, based on bandwidth and an automatically assigned pricing tier (Tier 1 to Tier 5).
  • There are no per-GB data transfer charges from AWS.
  • The tier depends on the distance between the source Regions of your VPC traffic and the Interconnect’s local Region.
  • AWS’s example: a 10 Gbps Tier 1 Interconnect from us-east-1 costs $12.33 per hour, or $9,000.90 for a 730-hour month.
  • You can create one Free Tier Interconnect (500 Mbps) per cloud provider, per Region.

Watch out with Cloud WAN: your tier is set by the highest-tier CNE in your topology. AWS’s own example shows a us-east-1 Interconnect with CNEs in us-east-1 and Singapore landing in Tier 4, not Tier 1. The other provider also charges separately for its side.

Monitoring and Operations

Every Interconnect includes one CloudWatch Network Synthetic Monitor at no extra cost, which reports round-trip latency and packet loss. A percentage utilization metric in CloudWatch shows how much of your provisioned capacity is in use. Set alarms on both, and resize bandwidth from the console when needed, without reprovisioning.

Best Practices for a Production Rollout

  • Start with the free 500 Mbps tier to validate routing, DNS and latency before paying for higher bandwidth.
  • Fix overlapping CIDRs first. Plan a clean IP scheme across your AWS VPC design and Azure VNets.
  • Pick Transit Gateway for a single Region and Cloud WAN for a global design, keeping the pricing tier impact in mind.
  • Keep application-layer encryption. MACsec protects the physical links; TLS still protects your data end to end.
  • Compare against your current setup. If you pay for colocation, cross-connects and router maintenance today, include those costs in the comparison.

FAQ

Which clouds does AWS Interconnect – multicloud support?

According to AWS, it supports Microsoft Azure, Google Cloud and Oracle Cloud Infrastructure. The Azure connection became generally available on 17 November 2026.

Does AWS charge for data transfer over an Interconnect?

No. AWS charges an hourly rate based on bandwidth and pricing tier, with no per-GB data transfer charges. The other cloud provider bills its side separately.

Is traffic encrypted?

Yes. Physical links between AWS and the partner provider use MACsec encryption by default. You should still use TLS or other application-level encryption for sensitive data.

Do I still need Direct Connect?

You do not order Direct Connect circuits or cross-connects, but you use a Direct Connect gateway as the attach point on the AWS side.

Plan Your AWS and Azure Multicloud Network

AWS Interconnect – multicloud turns weeks of circuit ordering and BGP work into a managed connection you can create in minutes. The real work is still in the design: IP planning, routing, tier-aware cost modelling and security. Our team helps companies build hybrid and multicloud architectures across AWS and Azure. If you want a second opinion on your multicloud network, talk to Shanav.