When transitioning to Azure, had thought that this pattern would work as a replacement for the Cisco ASA to support our partners requiring limited access to our environment. Having an issue with gateway transit, however, between the partner VPN gateways and our primary VNet. Client can connect okay to partner VNet and access resources (e.g., VM) in the partner VNet (VPN connect) Routing to primary VNet (10.190.0.0/16) using partner VPN interface appears correctly in client routing table VM in the partner VNet can access resources in primary VNet okay (peering) The client, however, is unable reach any resources in the primary VNet which suggests a gateway transit issue in the peering. Hoping that you might have some insight or suggestions.

Azure VPN Vnet

Atharv Gupta 1

When transitioning to Azure, had thought that this pattern would work as a replacement for the Cisco ASA to support our partners requiring limited access to our environment. Having an issue with gateway transit, however, between the partner VPN gateways and our primary VNet.

Client can connect okay to partner VNet and access resources (e.g., VM) in the partner VNet (VPN connect)
Routing to primary VNet (10.190.0.0/16) using partner VPN interface appears correctly in client routing table
VM in the partner VNet can access resources in primary VNet okay (peering)
The client, however, is unable reach any resources in the primary VNet which suggests a gateway transit issue in the peering.

Hoping that you might have some insight or suggestions.

GitaraniSharma-MSFT 47,316 Reputation points Microsoft Employee

2021-10-12T10:39:19.407+00:00

Hello @Atharv Gupta ,

Could you please share a network diagram of your setup?
If I understand correctly, client (on-premises) <----VPN----> Partner Vnet <----Vnet peering----> Primary Vnet is the connection setup. Please correct me if I am wrong.

When you say client, is it from on-premises network?
Please confirm if it is S2S VPN or P2S VPN?

So, on-premise can connect to Partner Vnet via Azure VPN and the Partner Vnet VMs can connect to Primary Vnet via Vnet peering. The Vnet peering has gateway transit enabled but on-premise client is unable to access the primary Vnet, is that correct?

Regards,
Gita Sharma
GitaraniSharma-MSFT 47,316 Reputation points Microsoft Employee

2021-10-14T14:23:52.89+00:00

Hello @Atharv Gupta , any updates on this post?
GitaraniSharma-MSFT 47,316 Reputation points Microsoft Employee

2021-10-19T10:57:35.71+00:00

Hello @Atharv Gupta , any updates on this post from your end?