
AWS Interconnect - multicloud Is Now GA with Microsoft Azure, So I Checked Out the AWS CLI and Pricing
This page has been translated by machine translation. View original
Introduction
On November 17, 2026, the Microsoft Azure connection for AWS Interconnect - multicloud became generally available (GA).
AWS Interconnect - multicloud is a feature that creates private connections between AWS and other cloud providers.
I covered the Azure connection during the Preview in a previous article.
This time, I re-ran the same commands as in the previous article to check the differences from the Preview, and retrieved the AWS-side and Azure-side pricing from their respective pricing APIs.
Verification with the AWS CLI
I ran the commands with AWS CLI 2.41.0.
Environments for Azure
I ran the following command in three regions: us-east-1, ap-southeast-2, and eu-central-1.
aws interconnect list-environments --region <リージョン>
The Azure-related entries in the response are as follows.
| AWS Region | Azure location | environmentId | state |
|---|---|---|---|
| us-east-1 | eastus | mce-aws-azure-iad-prod | available |
| ap-southeast-2 | australiaeast | mce-aws-azure-syd-prod | available |
| eu-central-1 | germanywestcentral | mce-aws-azure-fra-prod | available |
The environmentId and state were the same as in the Preview for all three regions.
Regarding bandwidth, in the Preview both available and supported in bandwidths were only 1Gbps. In GA, all three regions offer eight options: 500Mbps, 1Gbps, 2Gbps, 5Gbps, 10Gbps, 20Gbps, 50Gbps, and 100Gbps. The values for available and supported were the same.
In the Preview, us-west-1 (West US on the Azure side) was also supported, but it is not supported in GA.
Attach Points and input fields
I ran list-attach-points for each Azure Environment and also output the input skeleton for create-connection.
aws interconnect list-attach-points --environment-id mce-aws-azure-iad-prod --region us-east-1
aws interconnect create-connection --generate-cli-skeleton input
list-attach-points returned an empty array in all three regions.
{
"attachPoints": []
}
The skeleton has the following seven fields, the same as the output in the previous article.
{
"description": "",
"bandwidth": "",
"attachPoint": {
"directConnectGateway": "",
"arn": ""
},
"environmentId": "",
"remoteAccount": {
"identifier": ""
},
"tags": {
"KeyName": ""
},
"clientToken": ""
}
Pricing
When you create an Interconnect, charges are incurred separately on the AWS side and the Azure side. Since the two companies set prices independently, estimate the monthly cost by adding up the charges on both sides. Here I only cover the Interconnect charges themselves, and do not include the charges for surrounding services such as Direct Connect gateway.
Here are the AWS and Azure pricing pages.
AWS side
The AWS side is billed hourly, and the unit price is determined by bandwidth and Tier. There is no per-GB data transfer charge for Interconnect. There are five Tiers, 1 through 5, and Tier 1 applies when the VPCs that originate traffic are only in the Interconnect's local region. You can check which Tier your configuration falls under on the AWS pricing page.
I retrieved the unit prices for Azure from the Price List API.
aws pricing get-products --region us-east-1 --service-code AWSInterconnect --filters Type=TERM_MATCH,Field=partnerCloudServiceProvider,Value=AZR --output json
The unit prices (USD/hour) organized by bandwidth and Tier from the response are below. For the same bandwidth and Tier, the unit price was identical across the three regions us-east-1, ap-southeast-2, and eu-central-1.
| Bandwidth | Tier 1 | Tier 2 | Tier 3 | Tier 4 | Tier 5 |
|---|---|---|---|---|---|
| 500Mbps | 0 | - | - | - | - |
| 1Gbps | 1.37 | 2.05 | 2.74 | 5.75 | 9.59 |
| 2Gbps | 2.60 | 3.90 | 5.21 | 10.93 | 18.22 |
| 5Gbps | 6.51 | 9.76 | 13.01 | 27.33 | 45.55 |
| 10Gbps | 12.33 | 18.49 | 24.66 | 51.78 | 86.30 |
| 20Gbps | 24.66 | 36.99 | 49.32 | 103.56 | 172.60 |
| 50Gbps | 61.64 | 92.47 | 123.29 | 258.90 | 431.51 |
| 100Gbps | 116.44 | 174.66 | 232.88 | 489.04 | 815.07 |
Tier 4 for 10Gbps is 51.78 USD/hour, about 4.2 times the 12.33 USD/hour of Tier 1.
500Mbps is free for one connection in the local region (Tier 1), per combination of cloud provider and AWS Region.
Azure side
The Azure side is billed monthly, and is determined by Local / Premium, Zone, and bandwidth. Local can connect to the Azure region corresponding to the Interconnect's connection location. Premium can connect to Azure regions around the world. Zone is an Azure pricing zone, with Zones 1 through 3. The monthly fee includes unlimited inbound and outbound transfer.
I retrieved the unit prices from the Retail Prices API.
curl -sS "https://prices.azure.com/api/retail/prices?api-version=2023-01-01-preview&\$filter=contains(productName,%27Multicloud%27)"
The Data Transfer Out meter was 0 USD/GB for all of Local / Premium and Zones 1 through 3. For the same bandwidth, the monthly fee for Zone 2 is 1.2 times that of Zone 1, and Zone 3 is 1.6 times. Premium is 1.75 times Local for the same bandwidth and Zone.
The 500Mbps free tier is available for Local only, with one connection per subscription, no SLA, and a maximum of 90 days.
Monthly cost on both sides
For the same bandwidth, I lined up the monthly costs of AWS-side Tier 1 and Azure-side Zone 1 (USD). The AWS-side values are the hourly unit price multiplied by 730 hours.
| Bandwidth | AWS side Tier 1 | Azure side Local | Azure side Premium |
|---|---|---|---|
| 500Mbps | Free tier | Free tier | Not available |
| 1Gbps | 1,000.10 | 949.00 | 1,660.75 |
| 2Gbps | 1,898.00 | 1,898.00 | 3,321.50 |
| 5Gbps | 4,752.30 | 4,745.00 | 8,303.75 |
| 10Gbps | 9,000.90 | 9,490.00 | 16,607.50 |
| 20Gbps | 18,001.80 | 18,980.00 | 33,215.00 |
| 50Gbps | 44,997.20 | 47,450.00 | 83,037.50 |
| 100Gbps | 85,001.20 | 100,000.00 | 175,000.00 |
For example, with 10Gbps, AWS side at Tier 1, and Azure side at Local in Zone 1, the monthly cost is 9,000.90 + 9,490.00 = 18,490.90 USD.
Summary
After Google Cloud, AWS Interconnect - multicloud has now reached GA for Azure as well.
You can use a network with guaranteed bandwidth, billed hourly on the AWS side and monthly on the Azure side, with no charges for data transfer volume. If large amounts of data transfer occur between AWS and Azure, please consider using it.
The supported regions are limited to us-east-1 (N. Virginia), ap-southeast-2 (Sydney), and eu-central-1 (Frankfurt), but I look forward to future region expansion, including Tokyo.
