Skip to content

Commit d125a1f

Browse files
Merge pull request #230949 from 143data/patch-9
Update network-security-groups-overview.md
2 parents 09ec8cc + 6365e50 commit d125a1f

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/virtual-network/network-security-groups-overview.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: asudbring
77
ms.service: virtual-network
88
ms.topic: conceptual
99
ms.workload: infrastructure-services
10-
ms.date: 11/10/2022
10+
ms.date: 03/15/2023
1111
ms.author: allensu
1212
ms.reviewer: kumud
1313
ms.custom: FY23 content-maintenance
@@ -36,9 +36,7 @@ A network security group contains zero, or as many rules as desired, within Azur
3636

3737
Security rules are evaluated and applied based on the five-tuple (source, source port, destination, destination port, and protocol) information. You can't create two security rules with the same priority and direction. A flow record is created for existing connections. Communication is allowed or denied based on the connection state of the flow record. The flow record allows a network security group to be stateful. If you specify an outbound security rule to any address over port 80, for example, it's not necessary to specify an inbound security rule for the response to the outbound traffic. You only need to specify an inbound security rule if communication is initiated externally. The opposite is also true. If inbound traffic is allowed over a port, it's not necessary to specify an outbound security rule to respond to traffic over the port.
3838

39-
Existing connections may not be interrupted when you remove a security rule that enabled the flow. Traffic flows are interrupted when connections are stopped and no traffic is flowing in either direction, for at least a few minutes.
40-
41-
Modifying network security group rules will only affect the new connections that are formed. When a new rule is created or an existing rule is updated in a network security group, it will only apply to new flows and new connections. Existing workflow connections aren't updated with the new rules.
39+
Existing connections may not be interrupted when you remove a security rule that allowed the connection. Modifying network security group rules will only affect new connections. When a new rule is created or an existing rule is updated in a network security group, it will only apply to new connections. Existing connections are not reevaluated with the new rules.
4240

4341
There are limits to the number of security rules you can create in a network security group. For details, see [Azure limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#azure-resource-manager-virtual-networking-limits).
4442

0 commit comments

Comments
 (0)