AWS Interconnect - multicloud has preview support for Microsoft Azure, so I tried checking it with the AWS CLI

Introduction

On August 31, 2026, Microsoft Azure was added as a Public Preview destination for AWS Interconnect - multicloud. Announcements have been made by both AWS and Microsoft.

https://aws.amazon.com/about-aws/whats-new/2026/08/aws-announces-AWS-interconnect-multicloud-microsoft-azure-preview/

https://aws.amazon.com/blogs/networking-and-content-delivery/aws-and-microsoft-azure-collaborate-to-expand-multicloud-networking/

https://azure.microsoft.com/en-us/blog/introducing-azure-multicloud-interconnect-for-aws/

An overview of AWS Interconnect - multicloud itself and the details confirmed when OCI was added as a destination are described in the previous article.

https://dev.classmethod.jp/articles/aws-interconnect-multicloud-oci-added-check/

This time as well, we will not operate the Azure portal and will verify using only the AWS CLI.

Verification Details

We will examine the state and bandwidth of the Environment for Azure, and then follow the input items to be decided before creating a Connection.

Checking the Environment

We verified in a list whether Environments for Azure are returned in the 4 regions mentioned in the AWS blog.

aws interconnect list-environments --region us-east-1
aws interconnect list-environments --region us-west-1
aws interconnect list-environments --region ap-southeast-2
aws interconnect list-environments --region eu-central-1

Listing only the Environments for Azure, the results were as follows.

Bandwidth is returned in separate lists: available for what is currently usable, and supported for what is planned to be supported. All 4 Azure entries have only 1Gbps in supported as well, meaning there is only one bandwidth option to choose from.

remoteIdentifierType indicates the type of identifying information passed as the counterpart account when creating a Connection. The reference defines account and email, but all 4 Azure entries were account. For create-connection's remoteAccount, you pass an account identifier rather than an email address.

Extracting the Azure elements from the us-east-1 response is as follows.

{
    "provider": {
        "cloudServiceProvider": "azure"
    },
    "location": "eastus",
    "environmentId": "mce-aws-azure-iad-prod",
    "state": "available",
    "bandwidths": {
        "available": [
            "1Gbps"
        ],
        "supported": [
            "1Gbps"
        ]
    },
    "type": "Multicloud",
    "remoteIdentifierType": "account"
}

Coexisting Environments

In us-east-1, a total of 4 entries were returned, including destinations other than Azure.

limited means the Environment itself is usable, but there is a limitation on overall capacity (list-environments CLI reference).

In the other 3 regions (us-west-1 / ap-southeast-2 / eu-central-1), 2 entries were returned for Azure and Google Cloud. The state for Google Cloud was limited in all cases. The OCI Environment was only returned in us-east-1.

Attach Points and Input Items

To create a Connection, an Attach Point is needed as the connection destination on the AWS side. Attach Points that are accessible to the caller and valid in the specified Environment can be retrieved with list-attach-points. We ran this specifying the Azure-targeted Environment in us-east-1.

aws interconnect list-attach-points --environment-id mce-aws-azure-iad-prod --region us-east-1

{
    "attachPoints": []
}

Since we had not created a Direct Connect Gateway this time, an empty array was returned.

What needs to be determined when creating a Connection can be read from the skeleton output. --generate-cli-skeleton input does not send an API request and only outputs the JSON for input.

aws interconnect create-connection --generate-cli-skeleton input

{
    "description": "",
    "bandwidth": "",
    "attachPoint": {
        "directConnectGateway": "",
        "arn": ""
    },
    "environmentId": "",
    "remoteAccount": {
        "identifier": ""
    },
    "tags": {
        "KeyName": ""
    },
    "clientToken": ""
}

Of the 7 fields listed, the ones required according to the create-connection CLI reference are bandwidth, attachPoint, and environmentId.

According to the AWS Interconnect User Guide, the Attach Point on the AWS side is always a Direct Connect Gateway. On the remote side, in the case of multicloud, it becomes the CSP's router. The JSON has two keys, directConnectGateway and arn, but since they are defined as a tagged union in the reference, only one of them can be specified.

Creating a Connection proceeds with two actions: Create and Accept. The Activation Key returned in the Create response is passed to the Azure portal to Accept.

On the Azure side, the feature corresponding to this connection is called Azure Multicloud Interconnect. When looking up procedures on the Azure side, this name serves as a useful reference. The interconnect specifications are published as an open API.

https://github.com/aws/Interconnect

Summary

Microsoft Azure is now available for preview use with AWS Interconnect - multicloud.

At this time, there are limitations on the available regions and bandwidth options. However, both AWS and Microsoft have announced plans for future expansion in their respective blogs, with Microsoft stating that up to 100Gbps will be available at GA.

If you are currently using Site-to-Site VPN or third-party interconnect services for connectivity between AWS and Microsoft, please try out the preview environment.