Skip to main content
Zhuo
Explorer
September 1, 2025
Question

Azure Virtual WAN

  • September 1, 2025
  • 3 replies
  • 548 views

If the FGT in the Azure V-hub isn't directly connected to the local network, the local network won't be able to access it and won't be managed by our local FortiManager.

Azure V-hub doesn't pass its routes to indirect connections.

 

What are your thoughts on this issue?

3 replies

Anthony_E
Staff
Staff
September 4, 2025

Hello,


Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.


Thanks,

Best Regards
Anthony_E
Staff
Staff
September 8, 2025

Hello,

We are still looking for someone to help you.

We will come back to you ASAP.


Thanks,

Best Regards
Jean-Philippe_P
Staff & Editor
Staff & Editor
September 10, 2025

Hello Zhuo,

 

I found this solution. Can you tell me if it helps, please?

 

If the FortiGate in the Azure Virtual Hub isn't directly connected to the local network, the local network won't be able to access it, and it won't be managed by your local FortiManager. Azure Virtual Hub does not propagate routes to indirect connections. To resolve this, ensure that:

 

  1. Direct Connection: Establish a direct connection between the FortiGate in the Azure Virtual Hub and the local network. This can be done using VPN or ExpressRoute.

  2. Route Configuration: Ensure that the necessary routes are configured in the Azure Virtual Hub to allow traffic between the FortiGate and the local network.

  3. FortiManager Access: Verify that FortiManager has network access to the FortiGate for management purposes. This may require additional routing or firewall rules.

  4. VNet Peering: If applicable, use VNet peering to facilitate communication between VNets in Azure.

 

By ensuring these configurations, you can enable management of the FortiGate by the local FortiManager and allow access from the local network.

Jean-Philippe - Fortinet Community Team