vNet peering -- Allow Gateway Transit

%3CLINGO-SUB%20id%3D%22lingo-sub-2247527%22%20slang%3D%22en-US%22%3EvNet%20peering%20--%20Allow%20Gateway%20Transit%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2247527%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Eif%20we%20have%20S2S%20vpn%20(on%20prem%20to%20Azure)%20having%20with%20multiple%20workloads%20in%20differentregions%2C%20in%20this%20case%2C%20if%20region%201%20VM%20want%20to%20talk%20to%20region%202%20%2F%203.%3C%2FP%3E%3CP%3Ehow%20can%20we%20configure%20the%20network%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Econfiguring%20Site%202%20Site%20VPN%20to%20Region1%20(1st%20-%20vnet%20out%20of%205)%20later%20configuring%20Global%20vNet%20Peering%20(with%20Allow%20Gateway%20Transit)%20in%20between%20the%20region%202%2F3%20--%26gt%3B%20region%201%20will%20full%20fill%20my%20requirements.%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20suggest%20me%20the%20best%20path.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2247726%22%20slang%3D%22en-US%22%3ERe%3A%20vNet%20peering%20--%20Allow%20Gateway%20Transit%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2247726%22%20slang%3D%22en-US%22%3EWithin%20Azure%20cross-region%2C%20the%20best%20way%20to%20use%20Global%20VNET%20Peering%20which%20uses%20Microsoft%20Backbone%3CBR%20%2F%3EPlease%20refer%20to%20the%20following%20article%20to%20prepare%20GNET%20Peering%3CBR%20%2F%3E%3CBR%20%2F%3EBenefits-%3CBR%20%2F%3E1)%20Private%20Peering%20traffic%20stays%20on%20the%20Azure%20network%20backbone.%3CBR%20%2F%3E2)%20Low%20latency%20and%20high%20bandwidth%20VNet%20region%20to%20VNet%20region%20connectivity.%3CBR%20%2F%3E3)%20No%20more%20VNet%20to%20VNet%20VPN%20configuration%20which%20means%20no%20VPN%20encryption%2C%20no%20gateways%2C%20no%20public%20internet%20necessary.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-network%2Fcreate-peering-different-subscriptions%23cli%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-network%2Fcreate-peering-different-subscriptions%23cli%3C%2FA%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

 


if we have S2S vpn (on prem to Azure) having with multiple workloads in differentregions, in this case, if region 1 VM want to talk to region 2 / 3.

how can we configure the network?


configuring Site 2 Site VPN to Region1 (1st - vnet out of 5) later configuring Global vNet Peering (with Allow Gateway Transit) in between the region 2/3 --> region 1 will full fill my requirements. 

Please suggest me the best path.

2 Replies
Within Azure cross-region, the best way to use Global VNET Peering which uses Microsoft Backbone
Please refer to the following article to prepare GNET Peering

Benefits-
1) Private Peering traffic stays on the Azure network backbone.
2) Low latency and high bandwidth VNet region to VNet region connectivity.
3) No more VNet to VNet VPN configuration which means no VPN encryption, no gateways, no public internet necessary.

https://docs.microsoft.com/en-us/azure/virtual-network/create-peering-different-subscriptions#cli
Thank you Sesha,

"No more VNet to VNet VPN configuration which means no VPN encryption, no gateways, no public internet necessary." means with in multiple regions we can configure the GNET peering for handshake with options "Allow forwarded traffic" -- can we say with (allow forwarded traffic) this option, all other vNets (in region) will talk to all vNets in other region. Where to skip multiple configurations of peerings. Please advise.