Skip to content

Commit 37ee4bd

Browse files
committed
formatting
1 parent 0c84727 commit 37ee4bd

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/firewall/rule-processing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ When TLS inspection is enabled both unencrypted and encrypted traffic is inspect
112112

113113
### Implicit return traffic support (stateful TCP/UDP)
114114

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.
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.
116116

117117
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.
118118

0 commit comments

Comments
 (0)