Skip to content

Commit 38b25d2

Browse files
authored
Update network-watcher-nsg-flow-logging-overview.md
1 parent e529c2f commit 38b25d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/network-watcher/network-watcher-nsg-flow-logging-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: halkazwini
77
ms.service: network-watcher
88
ms.topic: conceptual
99
ms.workload: infrastructure-services
10-
ms.date: 02/27/2023
10+
ms.date: 03/15/2023
1111
ms.author: halkazwini
1212
ms.custom: template-concept, engagement-fy23
1313
---
@@ -391,7 +391,7 @@ If you want to retain data forever and don't want to apply any retention policy,
391391

392392
### User-defined inbound TCP rules
393393

394-
network security groups are implemented as a [stateful firewall](https://en.wikipedia.org/wiki/Stateful_firewall?oldformat=true). But because of current platform limitations, user-defined rules that affect inbound TCP flows are implemented in a stateless way.
394+
Network security groups are implemented as a [stateful firewall](https://en.wikipedia.org/wiki/Stateful_firewall?oldformat=true). But because of current platform limitations, user-defined rules that affect inbound TCP flows are implemented in a stateless way.
395395

396396
Flows that user-defined inbound rules affect become non-terminating. Additionally, byte and packet counts aren't recorded for these flows. Because of those factors, the number of bytes and packets reported in NSG flow logs (and Network Watcher traffic analytics) could be different from actual numbers.
397397

0 commit comments

Comments
 (0)