liveBook · Manning

Forced tunneling

As explained in Azure Security

Forced tunneling is a routing configuration that sends outbound traffic through a specified network destination instead of directly to the internet.

Forced tunneling configures Azure Firewall to send outbound traffic to a specified network destination instead of directly to the internet. This supports designs where a network virtual appliance, such as a third-party firewall, performs additional inspection. section 3.2.7

Implement forced tunneling with these constraints:

  • Enable forced tunneling when creating Azure Firewall; it cannot be enabled afterward. section 3.2.7
  • Add routes to AzureFirewallSubnet to direct traffic to the alternate network destination. section 3.2.7
  • Create AzureFirewallManagementSubnet with its own public IP address to support the configuration. section 3.2.7

Inspection through a network virtual appliance

After outbound traffic passes through Azure Firewall, route it to a network virtual appliance or third-party firewall for further inspection rather than forwarding it to the internet. section 3.2.7

How Azure Security covers it

How deep it goes
Explains the routing design and required subnets, but stops short of portal, CLI, or route-entry procedures.
Examples
Uses a third-party firewall or network virtual appliance as the alternate destination for outbound traffic inspection.
What it assumes
Assumes an Azure Firewall design and requires AzureFirewallSubnet routes plus a management subnet with its own public IP.
What you can do after
Configure Azure Firewall forced tunneling during creation with supporting routes, subnet, and public IP requirements.
How it connects
Connects Azure Firewall with AzureFirewallSubnet, AzureFirewallManagementSubnet, network virtual appliances, and Azure Firewall Premium.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.