Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.
3.3.1. Connectivity Models
Connectivity Models (how you connect to Microsoft's network):
| Model | Description | Best For |
|---|---|---|
| CloudExchange Co-location | Your equipment in a colocation facility with direct cross-connect | Enterprises with existing colo presence |
| Point-to-Point Ethernet | Dedicated fiber from your datacenter to provider | Large enterprises needing dedicated links |
| Any-to-Any (IPVPN) | Add Azure as another location in your MPLS WAN | Organizations with existing MPLS networks |
| ExpressRoute Direct | Direct 10G/100G ports at Microsoft peering locations | Massive bandwidth, lowest latency |
Circuit SKUs:
| SKU | Features | Use Case |
|---|---|---|
| Local | Access to Azure regions near peering location only, unlimited egress | Single-region deployments, cost-sensitive |
| Standard | Access to all Azure regions in same geopolitical area | Multi-region within continent |
| Premium | Global reach (all Azure regions worldwide), more routes | Global enterprises, multi-geo deployments |
⚠️ Exam Trap: Local SKU circuits have unlimited egress (no data transfer charges out of Azure), but only connect to nearby regions. If the scenario mentions "cost optimization" and "single region," Local is likely the answer.
Written byAlvin Varughese
Founder•15 professional certifications