<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Azure ExpressRoute Connection Setup

IZO™+ Multi Cloud Connect delivers Azure as an ExpressRoute circuit that you create in your own Azure subscription. The ordering journey is the standard IZO™+ Multi Cloud Connect flow, documented in full under  Provisioning & Configuration. This page shows how that flow applies to Azure, and the Azure-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex.

This page sits alongside the ordering journey rather than repeating it. The TCx Portal steps that place and provision the connection are common to every IZO™+ Multi Cloud Connect order and live under Provisioning & Configuration. Here we focus on how the flow applies to Azure: creating the ExpressRoute circuit, retrieving the network configuration, and configuring the peering in your Azure subscription.

[Prerequisites: Azure side] : Before placing this order, complete the following in your Azure portal:

  • Create an ExpressRoute circuit and select the connectivity provider Tata Communications, confirms for your peering location (Tata Communications where a direct interconnect serves it, otherwise the interconnection partner shown in the Azure portal)

  • Choose your peering location, bandwidth tier (50 Mbps to 10 Gbps) and SKU (Standard, Premium or Local)

  • Decide which peering types you’ll use (Private or Microsoft)

  • Note the service key Microsoft generates — this links the Azure-side circuit to Tata Communications’ provisioning.

How Azure setup fits together

The end-to-end flow is the standard IZO™+ Multi Cloud Connect order, with the Azure-side hand-off around it:

  1. Create the ExpressRoute circuit in the Azure portal and note the service key.

  2. Place your IZO™+ Multi Cloud Connect order for Azure in the TCx Portal (Direct or Flex), sharing the service key, the peering type for this circuit, and any VLAN preference.

  3. Tata Communications provisions the circuit against the service key and allocates the addressing and the C-tag.

  4. Retrieve the network configuration (Get Network Config) from the Portal inventory.

  5. Configure the Azure-side peering, and routing comes up.

Steps 2 and 3 are covered end to end under Provisioning & Configuration. See the IZO™+ Multi Cloud Connect Direct and IZO™+ Multi Cloud Connect Flex order pages  for Azure. This page covers the Azure-side steps around them.

In the TCx Portal: retrieve the network configuration

Once the circuit shows Provisioned, open the connection in your Portal inventory and choose Get Network Config. Note the values you will need for the Azure-side peering: the Cloud IP and Peer IP for the primary and secondary connections (each a /30 transit subnet) and the Tata Communications ASN (4755). Track provisioning status in the same inventory view.

On the Azure side

Because Azure is delivered as an ExpressRoute circuit in your own subscription, the Azure-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. In your Azure portal you:

  • Confirm the circuit is provisioned - On the ExpressRoute circuit overview, the Provider status moves from Not provisioned to Provisioned once Tata Communications completes provisioning.

  • Configure the peering - In Peering and Global Reach, select the peering type for this circuit, Azure Private Peering or Azure Microsoft Peering, matching the peering type set on your order.

  • Set the peering parameters and save - Enter Peer ASN 4755 (the Tata Communications edge), select IPv4, provide the primary and secondary /30 subnets from Get Network Config, and set the VLAN ID to match the circuit's C-tag (113 for Private, 115 for Microsoft).

On the default Layer 3 delivery this establishes the peering to the Tata Communications edge, and Tata Communications runs the onward BGP to Microsoft's MSEE routers on your behalf, so there is no CPE-to-MSEE session for you to configure. If your circuit is delivered as Layer 2 (a point-to-point L2VPN), you run BGP from your CPE directly to the MSEE routers using the parameters Tata Communications provides (remote ASN 12076). 

Direct vs Flex: who owns the peering addresses

On IZO™+ Multi Cloud Connect Direct (Layer 3), Tata Communications allocates the peer IPs. You take them from Get Network Config and enter them in the Azure peering blade against Peer ASN 4755.

On IZO™+ Multi Cloud Connect Flex, you define the interface and neighbour IPs and the BGP key at ordering and run BGP to Microsoft (remote ASN 12076). Creating the Azure circuit and sharing the service key are the same for both. 

The click-by-click walkthrough is under Provisioning & Configuration. For the Azure-specific detail on this side, see Azure Private Peering Configuration and Azure Microsoft Peering Configuration for the per-peering parameters.

Bandwidth changes

A bandwidth upgrade within the same SKU is initiated by you in the Azure portal and is non-disruptive, subject to capacity. A downgrade is not supported in place: it requires deprovisioning the existing circuit and creating a new one. See High Availability for Azure for capacity planning.

Related pages