Skip to content

Commit a9f082b

Browse files
authored
Merge pull request #104753 from vhorne/fw-faq
Forced tunneling statement
2 parents b96b7ec + e58c4e6 commit a9f082b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/firewall/firewall-faq.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,9 @@ Azure Firewall doesn’t SNAT when the destination IP address is a private IP ra
124124

125125
## Is forced tunneling/chaining to a Network Virtual Appliance supported?
126126

127-
Forced tunneling isn't currently supported. Azure Firewall must have direct Internet connectivity. If your AzureFirewallSubnet learns a default route to your on-premises network via BGP, you must override this with a 0.0.0.0/0 UDR with the **NextHopType** value set as **Internet** to maintain direct Internet connectivity.
127+
Forced tunneling is supported. For more information, see [Azure Firewall forced tunneling (preview)](forced-tunneling.md).
128+
129+
Azure Firewall must have direct Internet connectivity. If your AzureFirewallSubnet learns a default route to your on-premises network via BGP, you must override this with a 0.0.0.0/0 UDR with the **NextHopType** value set as **Internet** to maintain direct Internet connectivity.
128130

129131
If your configuration requires forced tunneling to an on-premises network and you can determine the target IP prefixes for your Internet destinations, you can configure these ranges with the on-premises network as the next hop via a user defined route on the AzureFirewallSubnet. Or, you can use BGP to define these routes.
130132

0 commit comments

Comments
 (0)