Express Route Peering Location not appearing on the list

For High Resiliency with Port type = Provider, first verify that your contracted provider is currently supported at an ExpressRoute Metro location; the peering-location list can only offer supported Metro/provider combinations.

For the Indonesia Central configuration shown

The current ExpressRoute Metro table lists Jakarta Metro, with Indonesia Central as its local Azure region:

• DCI Indonesia is listed without a future-availability marker.
• Telin and XL Axiata are marked as future providers; Microsoft states that circuit creation is expected to fail until those providers become active. ^1^

Proceed as follows:

1. Confirm with your contracted connectivity provider that it can provision ExpressRoute Metro at Jakarta Metro.
2. In Azure portal, select:
   • Resiliency: High Resiliency
   • Region: Indonesia Central
   • Port type: Provider
   • Peering location: Jakarta Metro
   • Provider: your contracted, currently active provider
3. Do not select DCI Indonesia unless that is the provider from which you are purchasing the circuit.
4. Complete the remaining circuit settings and create the circuit only when the provider is ready. Billing begins when the service key is issued. ^2^

If your provider is Telin, XL Axiata, or another provider not currently active at Jakarta Metro, High Resiliency through that provider is not presently a supported combination. Contact the provider about Metro availability or use another supported provider/location. Microsoft also advises contacting a desired provider when it does not support the required peering location. ^3^

If you intend to connect through Singapore

Singapore Metro is another documented High Resiliency location. Its listed active providers include Colt, DE-CIX, Equinix, IX Reach, MegaPOP (Singtel), Megaport, and Singtel International. ^1^

Use Singapore Metro only after confirming that your provider can provision there. Selecting Southeast Asia as the Azure resource region does not itself guarantee that a provider will appear.

Azure Region and ExpressRoute peering location are separate concepts:

• Region controls where the Azure circuit resource is stored.
• Peering location is the physical facility where your network connects to Microsoft.
• They do not generally have to match. ^3^

If the dropdown remains empty

If Jakarta Metro is absent before provider selection despite using the configuration above—or Singapore Metro is absent when testing that supported option:

1. Reopen the circuit creation form and confirm High Resiliency and Provider are selected.
2. Confirm that you are using the public Azure environment and an active subscription.
3. Capture the subscription, selected region, resiliency type, port type, intended provider, timestamp, and screenshot.
4. Open an Azure support request under ExpressRoute → Circuit creation/configuration, because the documented Metro location is not being returned by the portal.

Do not work around the empty list by creating a circuit with an unrelated provider. The provider named in Azure must be the provider that will receive the service key and provision the circuit.

References

1. About ExpressRoute Metro
2. Quickstart: Create and modify ExpressRoute circuits
3. ExpressRoute peering locations and connectivity partners