You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/network-watcher/traffic-analytics-rule-impact-analyzer.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,8 @@ Use rule impact analyzer in the Azure portal to analyze your security rules and
59
59
60
60
1. Select **Next**.
61
61
62
+
:::image type="content" source="media/traffic-analytics-rule-impact-analyzer/rule-configuration.png" alt-text="Screenshot that shows the Rule Configuration page of the Rule Impact Analyzer in the Azure portal.":::
63
+
62
64
### Select virtual networks
63
65
64
66
After selecting the rules to analyze, define the scope of the evaluation by choosing the target virtual networks whose traffic data will be used. Only eligible virtual networks are included to ensure the analysis provides an accurate view of end-to-end traffic behavior:
@@ -69,6 +71,8 @@ After selecting the rules to analyze, define the scope of the evaluation by choo
69
71
70
72
1. Select **Run Simulation**
71
73
74
+
:::image type="content" source="media/traffic-analytics-rule-impact-analyzer/run-simulation.png" alt-text="Screenshot that shows the simulation scope of the Rule Impact Analyzer in the Azure portal.":::
75
+
72
76
> [!IMPORTANT]
73
77
> Rule impact analysis is performed only on Virtual Networks with Traffic Analytics fully enabled. This ensures the simulation is based on complete and accurate traffic data. The following Virtual Networks are automatically excluded because they can result in incomplete or inaccurate simulation results:
74
78
> - Virtual networks with subnet or NIC‑level flow logs.
@@ -79,6 +83,7 @@ After selecting the rules to analyze, define the scope of the evaluation by choo
79
83
80
84
After running the simulation, you'll see a detailed report that lists all traffic paths and how your rules impact them.
81
85
86
+
:::image type="content" source="media/traffic-analytics-rule-impact-analyzer/simulation-results.png" alt-text="Screenshot that shows the simulation results of the Rule Impact Analyzer in the Azure portal." lightbox="media/traffic-analytics-rule-impact-analyzer/simulation-results.png":::
82
87
83
88
In the **Impact** column of the simulation results, you can find one of these states:
84
89
@@ -94,7 +99,8 @@ For impacted virtual networks, the report identifies the **impacting rule**, its
94
99
95
100
## Related content
96
101
97
-
-[Create a security admin rule using network groups](/azure/virtual-network-manager/how-to-create-security-admin-rule-network-group)
0 commit comments