News

AWS Restores Private Preview Access to Azure After Removal

AWS and Azure are launching the Interconnect preview with 1 Gbit/s-but without an Azure SLA. Before general availability, AWS will delete the circuits.

By Tobias Massow September 7, 2026 4 min read

AWS Restores Private Preview Access to Azure After Removal

Since August 31, 2026, AWS and Microsoft have offered the same private connection between their clouds. In Frankfurt, it’s available in preview mode with 1 Gbit/s and no Azure SLA. AWS will remove the preview circuits before general availability.

Key Takeaways

AWS Interconnect-multicloud and Azure Multicloud Interconnect entered public preview on August 31, 2026. Frankfurt is included among the four launch regions.
The preview delivers 1 Gbit/s and no Azure SLA. AWS will remove the preview circuits before general availability.
Routing, network segmentation, and circuit encryption are handled by the provider. Address planning, gateway, firewall, and workload encryption remain the customer’s responsibility.
The Frankfurt preview is a 1 Gbit/s test. AWS will delete preview circuits from accounts before general availability-no specific timeline is provided by either provider.

Related:AWS Meets Google Cloud in Frankfurt: What DACH Means / Terraform in the Cloud: Can You Run Commands from the U.S.?

What is AWS Interconnect-multicloud? A managed private connection between an AWS VPC and another cloud provider’s environment, ordered directly through the cloud console.

AWS and Azure Offer the Same Connection Path

On August 31, 2026, AWS and Microsoft launched the same private connection in public preview. AWS calls it Interconnect-multicloud, while Microsoft brands it Azure Multicloud Interconnect. Both providers rely on the same open interface specification, with customers ordering the circuit via the AWS console or Azure portal. Traffic bypasses the public internet entirely.

Four regions are live at launch: AWS’s Virginia North, California North, Sydney, and Frankfurt, paired with Azure’s East US, West US, Australia East, and Germany West Central. Frankfurt is the sole European preview region.

According to AWS, Google Cloud and Oracle Cloud are already generally available via AWS Interconnect-multicloud. Azure is now filling the gap in preview mode.

A 1-Gigabit Preview with No SLA-Connections Drop Before General Availability

According to Microsoft Learn, the preview is capped at 1 Gbit/s, and there is no Azure SLA during this phase. Neither provider charges for the preview connection; AWS allows one preview connection per customer and region. The connection costs nothing-which is why both treat it as a time-limited test product.

The critical clause appears in AWS documentation: Before general availability, AWS removes all 1 Gbit/s preview connections from accounts. During this interim period, no new interconnects can be established with this provider. A productively used preview connection thus disappears as planned.

Microsoft promises up to 100 Gbit/s from day one of general availability. Robert Kennedy, VP of Network Services at AWS, highlights MACsec by default, four-nines availability, and click-based scalability. Meanwhile, Azure’s preview documentation limits the offering to 1 Gbit/s in four regions and provides no SLA.

1 Gbit/s

Bandwidth limit for the Azure-to-AWS preview. General availability is expected to allow up to 100 Gbit/s.

Microsoft Learn, Availability and limits, August 31, 2026

„MACsec security out of the box, four-nines availability, and scalability at the click of a button.“

Robert Kennedy, VP Network Services AWS, Azure Blog, August 31, 2026

Providers Manage the Connection-Customers Retain Address Control

Azure and AWS handle network segmentation (VLAN), connection addressing, and the BGP routing protocol. Physical link encryption (MACsec) is enabled by default. A logical interconnect runs across redundant devices and paths at separate locations, eliminating the need for cross-connects in carrier-equipped data centers.

While providers take on part of the workload, customers retain most responsibilities. On both ends, the connection terminates at existing cloud network gateways. Address spaces must not overlap. Firewalling, routing, inspection, and workload encryption remain the customer’s responsibility. The path is entirely private-Microsoft’s public services remain inaccessible.

The preview does not replace existing Direct Connect or ExpressRoute carrier-based connections. These remain operational until a product with an SLA and higher bandwidth is available. Neither provider specifies when general availability will arrive; AWS only confirms it will remove preview connections beforehand.

Frequently Asked Questions

What did AWS and Azure launch on August 31, 2026?

A managed private path between both clouds in public preview. AWS calls the product Interconnect-multicloud, while Microsoft names it Azure Multicloud Interconnect. Frankfurt is one of the four launch regions.

Does the preview apply outside Frankfurt?

Yes. Alongside Frankfurt (Germany West Central), the preview is available in North Virginia (East US), Northern California (West US), and Sydney (Australia East). Neither provider has announced a timeline for additional regions.

What is known about general availability?

Microsoft mentions up to 100 Gbit/s from day one, while AWS highlights built-in MACsec and four nines availability. Neither provider has disclosed a release date, pricing, or SLA details.

What tasks remain with the customer?

Address planning without overlap, ExpressRoute Gateway, Direct Connect Gateway, firewall configuration, routing, and workload encryption. The provider handles BGP, VLAN, and MACsec on the physical link.

Does the preview replace Direct Connect plus ExpressRoute?

No. The preview serves as a testbed in Frankfurt. For production workloads, it lacks bandwidth, SLAs, and service guarantees until general availability.

Editor’s Picks

AWS, Azure, Google: The True Cost of Egress, Availability Zones, and Exit Fees
GitHub: Azure Now Powers Over Half of All Traffic
Timestream Backup: Restore Without a Support Ticket