Skip to content

Commit b44d061

Browse files
committed
implicit return traffic support
1 parent cf6f67c commit b44d061

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

articles/firewall/rule-processing.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,12 @@ Session drops done by IDPS blocks the flow silently. So no RST is sent on the TC
110110

111111
When TLS inspection is enabled both unencrypted and encrypted traffic is inspected. 
112112

113+
### Implicit return traffic support (stateful TCP/UDP)
114+
115+
User may configure firewall rules to allow traffic in one direction only. For example, Azure Firewall may allow connections initiated from an on‑premises network to an Azure virtual network, while requiring that new connections initiated from the Azure virtual network to on‑premises be blocked. To enforce this policy, user may add an explicit Deny rule for traffic from the Azure virtual network to the on‑premises network.
116+
117+
Azure Firewall supports this configuration. Azure Firewall is stateful and return traffic for an established TCP/UDP connection (for example, the SYN‑ACK/ACK packets for a connection initiated from on‑premises) is allowed even when an explicit Deny rule exists in the reverse direction. The explicit Deny rule continues to block new connections initiated from the Azure virtual network to on‑premises.
118+
113119
## Outbound connectivity
114120

115121
### Network rules and applications rules

0 commit comments

Comments
 (0)