For Microsoft Azure on Multi Cloud Connect Direct: first create an ExpressRoute circuit in Azure and copy its service key; configure the Virtual Cloud Connection with that key, VLAN 113 and a /30 subnet; complete the order; retrieve the peer IPs with Get Network Config; then configure Azure Private Peering with Peer ASN 4755. On the default L3VPN delivery the BGP session runs between the Tata Communications edge (4755) and Microsoft, so you enter no ASN in the Virtual Cloud Connection.
This page continues the Multi Cloud Connect Direct order for Azure. Complete the prerequisite below first, then configure the Virtual Cloud Connection, complete the order, retrieve the network configuration, and finish on the Azure side.
Prerequisite — create the ExpressRoute circuit and copy the service key
Prerequisite — before you start
Azure requires an ExpressRoute circuit before Tata Communications can provision the connection. Create it in the Azure portal, set Provider = Tata Communications, and copy the service key — you enter that key in the Virtual Cloud Connection.
1. In the Azure portal, search for ExpressRoute Circuits and select it, then click Create.
2. Enter the details below, then click Review + Create and, once validation passes, Create.
|
Field |
Information |
What it is / Demo Value |
Mand. |
|
Subscription |
Select the subscription you want to use to create the ExpressRoute circuit. |
Pay-as-you-go |
Yes |
|
Resource Group |
A resource group is a collection of resources that share the same lifecycle, permissions, and policies. |
your resource group |
Yes |
|
Resiliency |
|
Standard |
Yes |
|
Region |
Region defines the Azure location where your ExpressRoute circuit is created and connected to Microsoft’s network. |
South India |
Yes |
|
Circuit name |
The name must begin with a letter or number, end with a letter, number or underscore, and may contain only letters, numbers, underscores, periods, or hyphens. |
IZOMCCDemoGuide-Azure |
Yes |
|
Port type |
Select Provider if you are connecting to a service provider to access Microsoft's network. Select Direct if you have an ExpressRoute Direct resource and want to use it to connect directly to Microsoft's global network. |
Provider |
Yes |
|
Peering location |
The location where the ISP will provision the connection |
Chennai |
Yes |
|
Provider |
The ISP that will be providing the express route connection |
Tata Communications |
Yes |
|
Bandwidth |
The maximum bandwidth for the provisioned connection. Downgrading the bandwidth of a circuit is not supported. Carefully choose a bandwidth that matches your needs, overutilization causes degradation in performance. |
50 Mbps |
Yes |
|
SKU |
Local (available with bandwidth of 1Gbps or higher) provides free egress data transfer and gives you access to only 1-2 Azure regions in the same metro as your circuit. Standard gives you access to all Azure regions in the same geopolitical region as your circuit. Premium provides support for more than 4K routes, ability to connect to more than 10 virtual networks, and global connectivity. Premium also gives you access to your services deployed worldwide. |
Standard |
Yes |
|
Billing model |
All inbound data transfer is free of charge. Unlimited provides outbound data transfer for a single fixed monthly fee while metered provides outbound data transfer for a pre-determined rate. Downgrade from Unlimited to Metered is not allowed after circuit creation. |
Metered |
Yes |
3. After deployment, open the circuit and copy the Service Key from the overview — you share it with Tata Communications and enter it in the Virtual Cloud Connection.
Virtual Cloud Connection — Azure
Double-click the Virtual Cloud Connection icon, complete the fields, then Save & Validate.
|
Field |
Information |
What it is / Sample Value |
Mandatory |
|
MCC Flavor |
Virtual Cloud Connect supports both MCC Flavors:
|
Direct |
Yes |
|
CSP |
Select the Cloud Service Provider (CSP) with which you intend to establish Direct Connectivity. |
Microsoft Azure |
Yes |
|
Alias Name |
Alias Name acts as a unique identifier to link components, enabling easy reference throughout the solution. |
e.g. Azure_Chennai_VC |
Yes |
|
Location |
Select the desired CSP Direct Connect location based on your deployment requirements. |
Chennai |
Yes |
|
Data Center |
Select the data center corresponding to the CSP Direct Connect location where you want to establish connectivity. |
STT Chennai DC1-TD, VSB, India |
Yes |
|
Link Type |
Specifies the connection setup between the VNF and the CSP:
|
Dual |
Yes |
|
Select or Add Port |
Select the A-End VNF for the Virtual Cloud Connect or create a new VNF if one is not already available. |
your Fabric Port |
Yes |
|
Bandwidth |
Specify the bandwidth for the Virtual Cloud Connect link between the Fabric Port/VNF and the CSP. |
50 Mbps |
Yes |
|
Redundancy Type |
Choose Primary or Secondary in case of Dual Connectivity. |
Primary |
Yes |
|
Peer Type |
Select the desired CSP Peer Type:
|
Private |
Yes |
|
VLAN |
Use VLAN ID 113 for private peering and 115 for public peering.
|
113 |
Yes |
|
Enable BFD |
Enable Bidirectional Forwarding Detection (BFD) to quickly detect link failures in the BGP session. |
Yes / No |
No |
|
BFD Multiplier |
Set the BFD detection multiplier, which defines how many missed messages indicate a failure. |
3 |
No |
|
BFD Transmit Interval |
Specify the time interval (in milliseconds) between sending BFD packets to the peer. |
300 |
No |
|
BFD Receive Interval |
Specify the minimum time (in milliseconds) the system expects between receiving BFD packets from the peer. |
300 |
No |
|
Azure Service Key |
Enter the Azure Service Key from the Azure portal to establish the ExpressRoute connection; this key uniquely identifies your ExpressRoute circuit. |
your service key |
Yes |
|
Subnet |
Specify the subnet mask for the IP address used in the BGP interface configuration.
|
/30 |
Yes |
|
Specific Prefix Required |
This provides you with the option to specify, Prefix Exact in and Prefix Exact Out and others. |
No |
No |
|
Prefix Filter Required |
This provides you with the option to specify Public Prefix Advertisement from MPLS to Cloud and Public Prefix Advertisement from Cloud to MPLS. |
No |
No |
Complete the order
With the Fabric Port and Virtual Cloud Connection validated, set the commercials and place the order.
-
Set the Contract Term. The Total Contract Value (TCV) refreshes automatically; click Price Breakup to see the component-wise charges.
-
On the Price Breakup screen, review the charges. You can download the draft quote and click Get Ask Price for specific pricing.
-
Enter the expected ARC and NRC, then Submit.
-
Click Checkout to place the order.
-
Enter the Customer Contracting Entity details, then click Generate Order Form.
Generate order form — fields
Field
Information
What it is / Sample Value
Mandatory
Select number of legal entities
Whether the service is contracted under a single legal entity or split across multiple.
Single or Multiple
Yes
Name
The contracting legal entity the order is raised under.
your legal entity
Yes
Address
The registered address of the contracting entity.
entity address
Yes
Email ID
Contact email for the order and order-form correspondence.
contact email
Yes
Contact name
The person Tata Communications should contact about the order.
contact name
Yes
Contact number
A phone number for that contact.
contact number
Yes
-
Review the Order Form — Terms and Conditions, Total Charges, Billing and Payments, Contracting Information and Order Summary — and check the agreement box.
-
Click Order as You Click to submit directly or choose DocuSign / Delegate Signature to send the Customer Order Form to another approver.
-
Click Preview eCOF to view or download the draft Customer Order Form. Provisioning begins once the order is signed.
Get Network Config
Once the order is provisioned, open Inventory → IZO™+ Multi Cloud Connect to view the provisioned components — Fabric Port, Fabric Edge, Connections and the full Solution Inventory.
-
Open the Connections inventory, select your Virtual Cloud Connection, click the three-dot menu and choose Get Network Config.
-
Note the Cloud IP and Peer IP (each a /30) for the primary and, on dual links, the secondary connection — the addresses Tata Communications has allocated. You enter these as the primary and secondary subnets in Azure Private Peering.
For example, primary Cloud IP 10.128.177.158/30 and Peer IP 10.128.177.157/30; secondary Cloud IP 10.128.177.150/30 and Peer IP 10.128.177.149/30. The Get Network Config panel also shows the Tata Communications Peer ASN 4755.
Azure side — configure Azure Private Peering
These steps are completed in the Azure portal. Have the primary and secondary /30 subnets from Get Network Config to hand.
1. Open Azure Private Peering
In the Azure portal, open the ExpressRoute circuit you created, go to the Peering and Global Reach tab, then select Azure Private Peering.
2. Enter the peering details
Complete the private peering fields using the addresses from Get Network Config, then click Save.
|
Field |
Information |
What it is / Sample Value |
Mandatory |
|
Peer ASN |
The Tata Communications ASN on the peering — fixed at 4755. |
4755 |
Yes |
|
Subnets |
Select IPv4 (or Both / IPv6 as required). |
IPv4 |
Yes |
|
IPv4 Primary subnet |
The primary /30 subnet from Get Network Config. |
e.g. 10.128.177.148/30 |
Yes |
|
IPv4 Secondary subnet |
The secondary /30 subnet from Get Network Config. |
e.g. 10.128.177.156/30 |
Yes |
|
Enable IPv4 Peering |
Tick to enable IPv4 peering on the circuit. |
Enabled |
Yes |
|
VLAN ID |
The VLAN for the peering — 113 for private peering. |
113 |
Yes |
|
Shared key |
Optional BGP MD5 key. If used, it is a value you choose and must match on both ends. |
optional |
No |
3. Confirm the peering is up
Once saved, Tata Communications runs the onward BGP to Microsoft’s MSEE routers. When the peering is provisioned, the connection is live end to end.
For the full Azure-side reference, including Microsoft peering and resiliency, see Azure Connection Setup.