Setup guidance
Azure ExpressRoute Setup Guide
Deploy Azure ExpressRoute using the FPT partner model with private Layer‑2 connectivity.
Partner model
FTI connects to cloud providers through partner hubs for SLA assurance and optimal routing.
Implementation overview
Deploy ExpressRoute by creating a circuit in Azure Portal, sharing the service key with FTI, and configuring peering.
Official doc: Create ExpressRoute circuit.
Direct connectivity from FPT infrastructure
- AWS: direct connectivity in Singapore, Thailand, Malaysia.
- OCI: direct connectivity in Singapore.
- GCP: direct connectivity in Singapore.
- Other clouds/regions: via partner hubs (PCCW, Megaport, Equinix, Epsilon).
Prerequisites
- Azure subscription, region, and bandwidth requirements.
- VLAN, ASN/BGP details, routing policies.
- Redundancy or multi‑site requirements.
Implementation steps
- Create the ExpressRoute circuit in Azure Portal.
- Share the service key with FTI for provisioning.
- Configure peering (Private/Microsoft/Public as required).
- Test SLA and complete acceptance.
Acceptance checklist
- Circuit is Provisioned and peering is Up.
- BGP session stable and performance meets SLA.
- Monitoring and alerts configured.
Deliverables
- Peering configuration summary.
- Test and acceptance report.
- 24/7 operational contacts.