Skip to content

Commit 4a28278

Browse files
Merge pull request #226696 from vhorne/fw-long-run
update idle timeout
2 parents 3f9418b + a291856 commit 4a28278

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/firewall/long-running-sessions.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,9 @@ The Azure Firewall engineering team updates the firewall on an as-needed basis (
3131

3232
### Idle timeout
3333

34-
An idle timer is in place to recycle idle sessions. The default value is four minutes. Applications that maintain keepalives don't idle out. If the application needs more than 4 minutes (typical of IOT devices), you can contact support to extent the time for inbound connections to 30 minutes in the backend. Idle timeout for outbound or east-west traffic cannot be changed.
34+
An idle timer is in place to recycle idle sessions. The default value is four minutes for east-west connections and can't be changed. Applications that maintain keepalives don't idle out.
35+
36+
For north-south connections that need more than 4 minutes (typical of IOT devices), you can contact support to extent the time for inbound connections to 30 minutes in the backend.
3537

3638
### Auto-recovery
3739

0 commit comments

Comments
 (0)