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/frequently-asked-questions.yml
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ sections:
25
25
- question: |
26
26
What is Network Watcher?
27
27
answer: |
28
-
Network Watcher is designed to monitor and repair the network health of IaaS (Infrastructure-as-a-Service) components, which includes Virtual Machines, Virtual Networks, Application Gateways, Load balancers, and other resources in an Azure virtual network. It is not a solution for monitoring PaaS (Platform-as-a-Service) infrastructure or getting web/mobile analytics.
28
+
Network Watcher is designed to monitor and repair the network health of IaaS (Infrastructure-as-a-Service) components, which includes Virtual Machines, Virtual Networks, Application Gateways, Load balancers, and other resources in an Azure virtual network. It isn't a solution for monitoring PaaS (Platform-as-a-Service) infrastructure or getting web/mobile analytics.
29
29
30
30
- question: |
31
31
What tools does Network Watcher provide?
@@ -77,7 +77,7 @@ sections:
77
77
- question: |
78
78
What is the NetworkWatcherRG?
79
79
answer: |
80
-
Network Watcher resources are located in the hidden **NetworkWatcherRG** resource group which is created automatically. For example, the NSG Flow Logs resource is a child resource of Network Watcher and is enabled in the NetworkWatcherRG.
80
+
Network Watcher resources are located in the hidden **NetworkWatcherRG** resource group, which is created automatically. For example, the NSG Flow Logs resource is a child resource of Network Watcher and is enabled in the NetworkWatcherRG.
81
81
82
82
- question: |
83
83
Why do I need to install the Network Watcher extension?
@@ -97,12 +97,12 @@ sections:
97
97
- question: |
98
98
Why is only one instance of Network Watcher allowed per region?
99
99
answer: |
100
-
Network Watcher just needs to be enabled once for a subscription for its features to work, this is not a service limit.
100
+
Network Watcher just needs to be enabled once for a subscription for its features to work, this isn't a service limit.
101
101
102
102
- question: |
103
103
How can I manage the Network Watcher Resource?
104
104
answer: |
105
-
The Network Watcher resource represents the backend service for Network Watcher and is fully managed by Azure. Customers don't need to manage it. Operations like move are not supported on the resource. However, [the resource can be deleted](./network-watcher-create.md#delete-a-network-watcher-using-the-azure-portal).
105
+
The Network Watcher resource represents the backend service for Network Watcher and is fully managed by Azure. Customers don't need to manage it. Operations like move aren't supported on the resource. However, [the resource can be deleted](./network-watcher-create.md#delete-a-network-watcher-using-the-azure-portal).
106
106
107
107
- name: Service availability and redundancy
108
108
questions:
@@ -131,15 +131,15 @@ sections:
131
131
* Navigate to the storage account by typing the storage account's name in the global search on the portal or from the [Storage Accounts page](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Storage%2FStorageAccounts)
132
132
* Under the **SETTINGS** section, select **Firewalls and virtual networks**
133
133
* In "Allow access from", select **Selected networks**. Then under **Exceptions**, tick the box next to **"Allow trusted Microsoft services to access this storage account"**
134
-
* If it is already selected, no change is needed.
134
+
* If it's already selected, no change is needed.
135
135
* Locate your target NSG on the [NSG Flow Logs overview page](https://portal.azure.com/#blade/Microsoft_Azure_Network/NetworkWatcherMenuBlade/flowLogs) and enable NSG Flow Logs with the above storage account selected.
136
136
137
137
You can check the storage logs after a few minutes, you should see an updated TimeStamp or a new JSON file created.
138
138
139
139
- question: |
140
140
How do I use NSG Flow Logs with a Storage account behind a Service Endpoint?
141
141
answer: |
142
-
NSG Flow Logs are compatible with Service Endpoints without requiring any extra configuration. Please see the [tutorial on enabling Service Endpoints](../virtual-network/tutorial-restrict-network-access-to-resources.md#enable-a-service-endpoint) in your virtual network.
142
+
NSG Flow Logs are compatible with Service Endpoints without requiring any extra configuration. See the [tutorial on enabling Service Endpoints](../virtual-network/tutorial-restrict-network-access-to-resources.md#enable-a-service-endpoint) in your virtual network.
0 commit comments