- Transit between ExpressRoute circuits - It includes a lab.
- Deploying Local SKU ExpressRoute Circuits
- LAB: Azure VPN/ER Coexistence using GCP as On-premises
- LAB: Verify BGP information on Azure VPN and ExpressRoute Gateways
There's a mix of Microsoft official Docs and other relevant information outside of the official Docs. You may see notes in some of the links with important points based on my experience interacting with customers.
- ExpressRoute FAQ
- ExpressRoute Partners and Locations
- ExpressRoute Pricing Details
- ExpressRoute SLAs
- ExpressRoute Technical Overview
- ExpressRoute Gateway Overview
- ExpressRoute Circuit vs Peerings
- ExpressRoute Prerequisites
- Workflows for Configuring ExpressRoute
- Prepare your Routing for ExpressRoute Peerings
- Route Optimization
- Create the Azure Private Peering
- Create an ExpressRoute Virtual Gateway
- Link a Virtual Network to an ER Circuit
- Designing for Disaster Recovery with the Private Peering
- Designing for High Availability
- VPN Backup for ExpressRoute using the Azure VPN Gateway
-
[DM comment] There are two options: IPsec (end-to-end) encryption versus MACsec (poin-to-point) encryption. IPSec can be used in any Circuit type (with Provider provisioning Model or Direct) but MACSec can only be used in Direct model. Keep in mind single IPSec tunnel throughput is limited to 1.2 Gbps (workaround is to build multiple IPSec tunnels).
-
Configure a site-to-site VPN over ExpressRoute Microsoft peering
-
Configure a Site-to-Site VPN connection over ExpressRoute private peering
-
Configure IPsec transport mode for ExpressRoute private peering