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
This article provides answers to some of the frequently asked questions asked about Azure Network Watcher.
@@ -29,15 +28,15 @@ sections:
29
28
* Monitoring
30
29
* [Topology view](./view-network-topology.md) shows you the resources in your virtual network and the relationships between them.
31
30
* [Connection monitor](./connection-monitor-overview.md) allows you to monitor connectivity and latency between endpoints inside and outside Azure.
32
-
* Diagnostics
31
+
* Network diagnostic tools
33
32
* [IP flow verify](./network-watcher-ip-flow-verify-overview.md) allows you to detect traffic filtering issues at a virtual machine level.
34
33
* [NSG diagnostics](./network-watcher-network-configuration-diagnostics-overview.md) allows you to detect traffic filtering issues at a virtual machine, virtual machine scale set, or application gateway level.
35
34
* [Next hop](./network-watcher-next-hop-overview.md) helps you verify traffic routes and detect routing issues.
36
35
* [Connection troubleshoot](./network-watcher-connectivity-portal.md) enables a one-time connectivity and latency check between a virtual machine and Bastion host, application gateway, or another virtual machine.
37
36
* [Packet capture](./network-watcher-packet-capture-overview.md) enables you to capture your virtual machine traffic.
38
37
* [VPN troubleshoot](./network-watcher-troubleshoot-overview.md) runs multiple diagnostics checks on your VPN gateways and connections to help debug issues.
39
-
* Logging
40
-
* [NSG flow logs](./network-watcher-nsg-flow-logging-overview.md) allows you to log network traffic passing through your [network security groups (NSGs)](../virtual-network/network-security-groups-overview.md).
38
+
* Traffic
39
+
* [NSG flow logs](./network-watcher-nsg-flow-logging-overview.md) and [VNet flow logs (preview)](vnet-flow-logs-overview.md) allow you to log network traffic passing through your network security groups (NSGs) and virtual networks respectively.
41
40
* [Traffic analytics](./traffic-analytics.md) processes your NSG flow log data enabling you to visualize, query, analyze, and understand your network traffic.
42
41
43
42
For more detailed information, see [Network Watcher overview](./network-watcher-monitoring-overview.md).
@@ -77,11 +76,21 @@ sections:
77
76
answer: |
78
77
The Network Watcher resource represents the backend service for Network Watcher, which is fully managed by Azure. You don't need to manage it. Operations like move aren't supported on the resource. However, Network Watcher instance can be deleted to disable Network Watcher in a particular region. For more information, see [Disable Network Watcher for your region](network-watcher-create.md#disable-network-watcher-for-your-region).
79
78
79
+
- question: |
80
+
Can I move Network Watcher instance from one region to another?
81
+
answer: |
82
+
No. Moving Network Watcher resource or any of its child resources across regions isn't supported.
83
+
80
84
- question: |
81
85
What is the NetworkWatcherRG?
82
86
answer: |
83
87
NetworkWatcherRG is a resource group that's automatically created for Network Watcher resources. For example, Network Watcher regional instances and the NSG flow log resources are created in **NetworkWatcherRG** resource group. You can customize the name of Network Watcher resource group using [PowerShell](network-watcher-create.md?tabs=powershell#enable-network-watcher-for-your-region), [Azure CLI](network-watcher-create.md?tabs=cli#enable-network-watcher-for-your-region), or [REST API](/rest/api/network-watcher/network-watchers/create-or-update).
84
88
89
+
- question: |
90
+
What ?
91
+
answer: |
92
+
Azure Network Watcher doesn't store customer data, except for the Connection monitor. Connection monitor stores customer data, which is automatically stored by Network Watcher in a single region to satisfy in-region data residency requirements.
0 commit comments