Azure FAQs
Quick answers to the questions most often asked about connecting to Microsoft Azure with IZO™+ Multi Cloud Connect. For step-by-step detail, follow the linked pages.
Getting connected
How do I start an Azure connection? You create an ExpressRoute circuit in the Azure portal, choose Tata Communications as your connectivity provider, and share the resulting service key with Tata Communications via the TCx Portal. See Azure Connection Setup.
What is the service key and why does Tata Communications need it? The service key is generated by Azure when you create the circuit. It links the Azure-side circuit to Tata Communications’ provisioning so the interconnect can be associated with your circuit.
Which peering types are supported? Two: Private Peering (for your VNets) and Microsoft Peering (for Microsoft public services). Both can run on the same circuit.
Bandwidth
What bandwidths are available? ExpressRoute circuits provisioned through Tata Communications support tiers from 50 Mbps to 10 Gbps, subject to availability at the chosen peering location. For higher dedicated capacity, see ExpressRoute Direct.
Can I change bandwidth later? A bandwidth upgrade within the same SKU is initiated by you in the Azure portal and is non-disruptive, subject to capacity. A downgrade requires deprovisioning and recreating the circuit.
Routing and addressing
What ASNs are used? Microsoft uses ASN 12076 for both peering types. Tata Communications uses ASN 4755 (fixed).
How many BGP sessions will I have? A pair (primary and secondary) per peering type, for redundancy. If you take both Private and Microsoft Peering, you’ll have two pairs.
Is multicast supported? No. Microsoft does not support multicast over ExpressRoute.
Resilience and performance
Is the connection resilient by default? Yes. Tata Communications establishes dual interconnects with Microsoft and creates your circuit over both, with dual BGP sessions. See High Availability for Azure.
What MTU does the connection support? The effective WAN-side MTU on the Azure ExpressRoute path is 1500 bytes, including Ethernet and IP overheads. Jumbo frames are not supported on ExpressRoute.
Security
Is MACsec available on the connection? Not on the provider-provisioned ExpressRoute circuit — MACsec is a property of ExpressRoute Direct ports. For Layer 3 encryption, use an IPsec overlay over the connection. See ExpressRoute Direct.
Who manages the CPE? The Azure cloud connection is delivered as an unmanaged service, so CPE configuration and management sit with you, using the parameter handoff Tata Communications provides.
Still stuck?
If your question isn’t answered here, see Azure Troubleshooting for symptom-based diagnostics, or raise a ticket from the Support area of the TCx Portal.