Skip to content

Commit 14e85e9

Browse files
committed
faqs acrolinx
1 parent 95ca227 commit 14e85e9

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/network-watcher/frequently-asked-questions.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ sections:
2525
- question: |
2626
What is Network Watcher?
2727
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.
2929
3030
- question: |
3131
What tools does Network Watcher provide?
@@ -77,7 +77,7 @@ sections:
7777
- question: |
7878
What is the NetworkWatcherRG?
7979
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.
8181
8282
- question: |
8383
Why do I need to install the Network Watcher extension?
@@ -97,12 +97,12 @@ sections:
9797
- question: |
9898
Why is only one instance of Network Watcher allowed per region?
9999
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.
101101
102102
- question: |
103103
How can I manage the Network Watcher Resource?
104104
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).
106106
107107
- name: Service availability and redundancy
108108
questions:
@@ -131,15 +131,15 @@ sections:
131131
* 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)
132132
* Under the **SETTINGS** section, select **Firewalls and virtual networks**
133133
* 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.
135135
* 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.
136136
137137
You can check the storage logs after a few minutes, you should see an updated TimeStamp or a new JSON file created.
138138
139139
- question: |
140140
How do I use NSG Flow Logs with a Storage account behind a Service Endpoint?
141141
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.
143143
144144
145145
- question: |

0 commit comments

Comments
 (0)