Infographic shows Azure, AWS, and Google Cloud linked by private fiber through Azure Multicloud Interconnect.
Azure Multicloud Interconnect has two release stages as of November 17, 2026. The AWS connection is generally available, and the Google Cloud connection is in public preview. The Azure Updates item carries a "Launched" tag. That tag covers only AWS and shouldn't be read as GA for every provider.

Infographic shows Azure, AWS, and Google Cloud linked by private fiber through Azure Multicloud Interconnect. What Microsoft announced​

Microsoft says the Azure Multicloud Interconnect connection with Amazon Web Services is now generally available, and the connection with Google Cloud Platform is in public preview. Microsoft's Azure Networking post describes a third item as well. It is a collaboration with Lumen on last-mile connectivity. That one is carrier-side work for connecting on-premises sites to Azure over ExpressRoute. It is not a third cloud provider.

According to Microsoft, the GA service is a production-ready private connection built on Azure ExpressRoute. Microsoft and AWS operate it cooperatively. Redundant paths across physically separate locations are meant to limit exposure to a single device, link or site failure. The two providers coordinate the lifecycle of the managed connection, including maintenance and recovery of the underlying paths.

What the service is​

Microsoft's documentation describes it as a managed service for private connectivity between Azure and a supported cloud provider. It doesn't cross the public internet. Some practical details from Microsoft Learn:

  • Resource model: You create an Azure Multicloud Interconnect resource, not a traditional ExpressRoute circuit. ExpressRoute is the underlying technology.
  • Activation keys: Either side can generate a key and the other redeems it. The key confirms that the provider, Azure region, bandwidth and provider account all match before provisioning starts. If validation fails, provisioning doesn't start. You correct the mismatch and restart activation.
  • No BGP work: Azure and the provider manage the underlying VLANs, point-to-point addressing and BGP sessions.
  • Gateway required: Traffic entering Azure uses an ExpressRoute virtual network gateway.
  • Encryption: MACsec is on by default on the physical links. Workload-level encryption is still your job where your requirements call for it.

On the AWS side, AWS introduced Interconnect – multicloud in preview at re:Invent 2025 and published an open API specification for network interoperability. Azure adopted that specification for its August preview.

Google Cloud: still preview​

Google's own announcement confirms the preview. Partner Cross-Cloud Interconnect for Azure is jointly supported by Google Cloud and Microsoft. It is a private, high-bandwidth connection set up programmatically in minutes, with no physical infrastructure to manage.

The preview is available in three Google Cloud regions: us-east4 (N. Virginia), us-west2 (Los Angeles) and europe-west3 (Frankfurt). Google says it will add more regions as the Azure offering moves to GA. Those are Google-side regions. They don't establish the Azure-side pairings, bandwidth, pricing or SLA.

Microsoft says customers can validate workload-specific bandwidth, availability and security profiles in staging before scaling to production. That is sensible advice for any preview service.

What is still unconfirmed​

Several details are not confirmed for the GA release:

  • Documentation lag: Microsoft Learn pages I could see still carry preview labels. They list AWS as the only provider, four Azure regions (Australia East, East US, Germany West Central and West US), 1 Gbps and no SLA. The FAQ page shows a "last updated" date of November 17, 2026, but it still says preview. Treat those figures as preview-era limits. They are not confirmed GA terms.
  • Product page: Microsoft's product page, as it appeared in search results, still carried a preview label. It said pricing details will be provided when the service becomes generally available. I found no confirmed GA pricing.
  • Speed and SLA: Microsoft said in August that the service would support up to 100 Gbps at GA. It also targeted a 99.99% availability SLA, though no SLA applies while a service is in preview. The November announcement doesn't restate either figure. Treat them as earlier stated targets, not confirmed GA terms. Check them before you build on them.
  • Regions: I found no confirmed list of GA regions.

What admins should do​

  1. AWS users: The change is the move from preview to a production offering. Microsoft tells customers to check the current documentation for the AWS GA scope. It also says to pick a representative workload and confirm locations, bandwidth, addressing, security, commercial and recovery requirements with your account team and cloud-provider contacts.
  2. Google Cloud users: Treat it as preview. Confirm eligibility, region pairing, support terms and limits before you rely on it for production.
  3. Plan the parts you still own. Microsoft's FAQ says customers manage their own virtual networks, gateways, connections and attachments. They also manage address planning (non-overlapping address spaces), route intent, firewalls, traffic inspection, access policies, workload encryption and application-level resilience.
  4. Last-mile needs: For on-premises sites, Lumen availability and onboarding go through Microsoft or Lumen account teams. Microsoft says ordering and billing integration may evolve separately from provisioning.

Analysis​

This is a real step for Azure networking, but it is only partly finished. The AWS path is now a supported production option. The Google Cloud path is a preview that Microsoft and Google describe in similar terms. The unanswered questions are the usual ones for a new GA: price, regions, bandwidth tiers and SLA. Until Microsoft publishes them, hold off on committing capacity or contracts based on them.

Microsoft's framing is also partly promotional. "Clearer operations" and "built-in resilience" describe design intent. Your own failure testing and recovery planning still decide whether the connection meets your needs.

 

References

  1. (Launched) Generally Available: Azure Multicloud Interconnect new cloud service provider support Azure Updates 2026-11-17T20:00:32Z
  2. Introducing Azure Multicloud Interconnect for AWS azure.microsoft.com
  3. Cross-Cloud Interconnect for Microsoft Azure cloud.google.com