> [!NOTE]
> **Note:** This page includes instructions about Azure products. Google doesn't guarantee that this guidance is up to date or that the sample configuration choices are ideal for your use case. For the most current information, refer to the [Azure documentation](https://learn.microsoft.com/azure/?product=networking) .

When you use Cross-Cloud Interconnect, Google provisions physical connections on your
behalf between the Google Cloud network and the Microsoft Azure network.

Before Google can establish these connections, you must order ports from both Google and
Azure. In preparation for that process, identify the Google Cloud locations
and the corresponding Azure locations that you want to use for your connections.

## Best practices for selecting a location

When deciding where to place your connections, consider questions such as the following:

- Where are most of your Google Cloud resources?
- Where are most of your Azure resources?

If your resources from both clouds are in the same place, then the choice is simple.
However, if they are not, consider whether you want your connections to be closer to your
Google Cloud resources or closer to your Azure resources. If the connections
are closer to your Azure resources, then your traffic spends more time
traveling on the Google network, which in general is desirable. However, you should also consider
the outbound data transfer costs that you're likely to incur from both clouds.

## Factors affected by location

This section describes factors that are affected by your location choice.

### VLAN attachments
and ExpressRoute circuits


After your Cross-Cloud Interconnect connection is established, you must configure
several resources in Google Cloud and Azure. In Google Cloud, these resources
include VLAN attachments. A VLAN attachment is a logical connection between your remote cloud
network and a single region in your Virtual Private Cloud network.

In Azure, you must create a similar resource. The
Azure resource is called an ExpressRoute circuit.

When you choose a location for your ports, you limit the set of regions where you can place
both VLAN attachments and virtual interfaces. For this reason, the supported locations table
includes columns for the Google Cloud and Azure regions that are served by
each port location.

<br />

> [!NOTE]
> **Note:** In Google Cloud, the location of the VLAN attachment
> doesn't have to limit which Google Cloud regions receive your Azure routes.
> To advertise Azure routes to all of your Google Cloud regions, configure
> [global
> dynamic routing](https://docs.cloud.google.com/network-connectivity/docs/router/concepts/learned-routes#dynamic-routing-mode-effects-on-learned-routes).
>
> In Azure, you can use
> [premium circuits](https://learn.microsoft.com/azure/expressroute/expressroute-introduction),
> which allow you to attach your circuit to any region.

### Edge availability domains

Each metropolitan area has two Google Cloud edge availability domains. Two domains in the
same metropolitan area are not scheduled to be down for maintenance at the same time. For this
reason, when you select a location for a primary and redundant port,
each port must use a different edge availability domain within the same metropolitan area. This is
true regardless of how you order your ports. However, when you use the Google Cloud CLI, you
must specify each edge availability domain explicitly. When you use the Google Cloud console, you
simply select a location, and Google Cloud reserves a port for you in each domain.

In the gcloud CLI version of the location name, the edge availability domain is the
second piece of information. For example, if the location name is `iad-zone1-1`,
the edge availability domain is `zone1`. If the location name is
`iad-zone2-1`, the edge availability zone is `zone2`.

### Colocation facilities


Azure requires that connections are provisioned in the same facility. For that reason, each
pair of locations in the supported locations table represents a single facility.

## List of supported locations

The following table lists the supported Azure locations and the corresponding
Google Cloud locations.

You must specify the Google Cloud location of your Cross-Cloud Interconnect
port, and additionally specify where in your other cloud provider to connect it. This latter
Azure location is referred to as the *remote location* in this documentation
set and within Google Cloud. Make sure to use the remote location name
when you order the Cross-Cloud Interconnect. Your remote cloud provider has a different,
although similar, name for the location, which you use when you order the port with that
cloud provider.

For each location name, some syntax variations exist. For example:

- The remote location name varies depending on whether you are interacting with Azure or Google Cloud.
- When interacting with Google Cloud, the Google Cloud console displays the remote location *description* next to the location name to help you choose the correct location.
- In Google Cloud, the Google Cloud console Cloud Interconnect location (not the remote location) shows facility information rather than the actual Cloud Interconnect location name.

> [!NOTE]
> **Note:** You can also use the gcloud CLI to list locations.
> For more information, see the reference page for the
> [`gcloud compute interconnects remote-locations list` command](https://docs.cloud.google.com/sdk/gcloud/reference/compute/interconnects/remote-locations/list).

> [!NOTE]
> **Note:** For the most up-to-date information about Azure locations, see [ExpressRoute partners and peering locations](https://learn.microsoft.com/azure/expressroute/expressroute-locations-providers) in the Azure documentation.

| Google Cloud regions | Microsoft Azure regions | Metropolitan area | Remote location || Google Cloud locations |
| Google Cloud regions | Microsoft Azure regions | Metropolitan area | Google Cloud | Microsoft Azure | Google Cloud locations |
|---|---|---|---|---|---|
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Hong Kong | azure-equinix-hong-kong-hk1 | Equinix-Hong-Kong-HK1 | - hkg-zone1-1118 - hkg-zone2-1118 |
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Osaka | azure-equinix-osaka-os1 | Equinix-Osaka-OS1 | - kix-zone1-1791 - kix-zone2-1791 |
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Seoul | azure-kinx-seoul-gasan | KINX-Seoul-Gasan | - icn-zone1-7674 - icn-zone2-7674 |
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Singapore | azure-equinix-singapore-sg1 | Equinix-Singapore-SG1 | - sin-zone1-2260 - sin-zone2-2260 |
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Singapore | azure-global-switch-singapore | Global-Switch-Singapore | - sin-zone1-388 - sin-zone2-388 |
| - asia-east1 - asia-east2 - asia-northeast1 - asia-northeast2 - asia-northeast3 - asia-southeast1 - asia-southeast2 - asia-southeast3 | - East Asia - Southeast Asia | Tokyo | azure-equinix-tokyo-ty4 | Equinix-Tokyo-TY4 | - nrt-zone1-1893 - nrt-zone2-1893 |
| - australia-southeast1 - australia-southeast2 | - Australia Central - Australia Central 2 | Sydney | azure-equinix-sydney-sy2 | Equinix-Sydney-SY2 | - syd-zone1-1605 - syd-zone2-1605 |
| - australia-southeast1 - australia-southeast2 | - Australia Central - Australia Central 2 | Sydney | azure-nextdc-sydney-s1 | NextDC-Sydney-S1 | - syd-zone1-1660 - syd-zone2-1660 |
| - me-central1 - me-central2 - me-west1 - europe-central2 - europe-north1 - europe-north2 - europe-southwest1 - europe-west1 - europe-west2 - europe-west3 - europe-west4 - europe-west6 - europe-west8 - europe-west9 - europe-west10 - europe-west12 | - France Central - France South - Germany North - Germany West Central - North Europe - Norway East - Norway West - Sweden Central - Switzerland North - Switzerland West - UK West - UK South - West Europe | Amsterdam | azure-equinix-amsterdam-am5 | Equinix-Amsterdam-AM5 | - ams-zone1-1236 - ams-zone2-1236 |
| - me-central1 - me-central2 - me-west1 - europe-central2 - europe-north1 - europe-north2 - europe-southwest1 - europe-west1 - europe-west2 - europe-west3 - europe-west4 - europe-west6 - europe-west8 - europe-west9 - europe-west10 - europe-west12 | - France Central - France South - Germany North - Germany West Central - North Europe - Norway East - Norway West - Sweden Central - Switzerland North - Switzerland West - UK West - UK South - West Europe | Frankfurt | azure-equinix-frankfurt-fr7 | Equinix-Frankfurt-FR7 | - fra-zone1-683 - fra-zone2-683 |
| - me-central1 - me-central2 - me-west1 - europe-central2 - europe-north1 - europe-north2 - europe-southwest1 - europe-west1 - europe-west2 - europe-west3 - europe-west4 - europe-west6 - europe-west8 - europe-west9 - europe-west10 - europe-west12 | - France Central - France South - Germany North - Germany West Central - North Europe - Norway East - Norway West - Sweden Central - Switzerland North - Switzerland West - UK West - UK South - West Europe | London | azure-equinix-london-ld5 | Equinix-London-LD5 | - lhr-zone1-832 - lhr-zone2-832 |
| - me-central1 - me-central2 - me-west1 - europe-central2 - europe-north1 - europe-north2 - europe-southwest1 - europe-west1 - europe-west2 - europe-west3 - europe-west4 - europe-west6 - europe-west8 - europe-west9 - europe-west10 - europe-west12 | - France Central - France South - Germany North - Germany West Central - North Europe - Norway East - Norway West - Sweden Central - Switzerland North - Switzerland West - UK West - UK South - West Europe | Paris | azure-interxion-paris-par5 | Interxion-Paris-PAR5 | - cdg-zone1-1536 - cdg-zone2-1536 |
| - me-central1 - me-central2 - me-west1 - europe-central2 - europe-north1 - europe-north2 - europe-southwest1 - europe-west1 - europe-west2 - europe-west3 - europe-west4 - europe-west6 - europe-west8 - europe-west9 - europe-west10 - europe-west12 | - France Central - France South - Germany North - Germany West Central - North Europe - Norway East - Norway West - Sweden Central - Switzerland North - Switzerland West - UK West - UK South - West Europe | Zurich | azure-interxion-zurich-zur2 | Interxion-Zurich-ZUR2 | - zrh-zone1-81 - zrh-zone2-81 |
| - asia-south1 - asia-south2 | - India West - India Central - India South | Mumbai | azure-tata-mumbai-lvsb | Tata-Mumbai-LVSB | - bom-zone1-554 - bom-zone2-554 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Washington D.C. | azure-equinix-ashburn-dc2 | Equinix-Ashburn-DC2 | - iad-zone1-1 - iad-zone2-1 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Washington D.C. | azure-equinix-ashburn-dc6 | Equinix-Ashburn-DC6 | - iad-zone1-1 - iad-zone2-1 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Washington D.C. | azure-coresite-reston-va2 | CoreSite-Reston-VA2 | - iad-zone1-5467 - iad-zone2-5467 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Washington D.C. | azure-coresite-reston-va3 | CoreSite-Reston-VA3 | - iad-zone1-5467 - iad-zone2-5467 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Chicago | azure-equinix-chicago-ch1 | Equinix-Chicago-CH1 | - ord-zone1-7 - ord-zone2-7 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Dallas | azure-equinix-dallas-da3 | Equinix-Dallas-DA3 | - dfw-zone1-4 - dfw-zone2-4 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Las Vegas | azure-switch-las-vegas | Switch-Las-Vegas | - las-zone1-770 - las-zone2-770 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Montréal | azure-cologix-montreal-mtl3 | Cologix-Montreal-MTL3 | - yul-zone1-1944 - yul-zone2-1944 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Portland | azure-edgeconnex-portland-por01 | EdgeConneX-Portland-POR01 | - pdx-zone1-1922 - pdx-zone2-1922 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | San Antonio, Texas | azure-cyrusone-san-antonio-1 | CyrusOne-San-Antonio-1 | - sat-zone1-1484 - sat-zone2-1484 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | San Francisco | azure-coresite-santa-clara-sv7 | CoreSite-Santa-Clara-SV7 | - sfo-zone1-1619 - sfo-zone2-1619 |
| - northamerica-northeast1 - northamerica-northeast2 - northamerica-south1 - us-central1 - us-east1 - us-east4 - us-east5 - us-south1 - us-west1 - us-west2 - us-west3 - us-west4 | - East US - West US - East US 2 - West US 2 - West US 3 - Central US - South Central US - North Central US - West Central US - Canada Central - Canada East | Seattle | azure-equinix-seattle-se2 | Equinix-Seattle-SE2 | - sea-zone1-86 - sea-zone2-86 |

## Verify availability

After you've identified a location that you want to use, double-check that it has an available
ExpressRoute Direct port with your intended capacity. This step is helpful because the availability
of ports can change without notice.

If you're working in the Azure portal, you can verify availability while ordering your
connections. To verify availability in advance, use Azure PowerShell.

### Azure PowerShell

Use the [`Get-AzExpressRoutePortsLocation` command](https://learn.microsoft.com/powershell/module/az.network/get-azexpressrouteportslocation?view=azps-8.1.0):

```
Get-AzExpressRoutePortsLocation -LocationName LOCATION
```

Replace `LOCATION` with the name of the location as it's
represented in Azure---for example, `Interxion-Frankfurt-FRA11`.

In the command output, look for the `AvailableBandwidths` block. Make sure
that it lists the port speed that you need.

For example, the following output shows that the `Interxion-Frankfurt-FRA11`
has available `10 Gbps` and `100 Gbps` ports:

```
    Name                : Interxion-Frankfurt-FRA11
    Id                  : [ID information]
    ProvisioningState   : Succeeded
    Address             : Interxion Deutschland GmbHHanauer LandstraÃŸe 298 60314 Frankfurt am Main
                         Deutschland
    Contact             : de.info@interxion.com
    AvailableBandwidths : [
                           {
                             "OfferName": "100 Gbps",
                             "ValueInGbps": 100
                           },
                           {
                             "OfferName": "10 Gbps",
                             "ValueInGbps": 10
                           }
                         ]
     
```

## Note locations and regions

After you've reviewed the previous sections, make a note of the following values:

- The remote location, as it's known in Google Cloud, and the Google Cloud location. You need these values when you [order your Cross-Cloud Interconnect connections](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/cci/azure/order-google-connections).
- The remote location, as it's known in Azure, and the region where you want to place the ExpressRoute Direct resources and ExpressRoute circuits. You need these values when you [order your Azure ports](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/cci/azure/order-azure-ports) and [create the ExpressRoute circuits](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/cci/azure/configure-azure#create-circuit).
- The Google Cloud region where you want to place your VLAN attachments. You need this value when you create the attachment, as described in [Configure your Google Cloud resources](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/cci/azure/configure-google-resources).