Skip to content

Commit 9dc4c4e

Browse files
committed
tweak to the answer of classic VMs
1 parent 9cf8264 commit 9dc4c4e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ sections:
141141
- question: |
142142
Does connection monitor support classic VMs?
143143
answer: |
144-
No, connection monitor doesn't support classic VMs. We recommended that you migrate infrastructure as a service (IaaS) resources from classic to Azure Resource Manager because classic resources [will be deprecated](../virtual-machines/classic-vm-deprecation.md). For more information, see [Migrate IaaS resources from classic to Azure Resource Manager](../virtual-machines/migration-classic-resource-manager-overview.md).
144+
No, connection monitor doesn't support classic VMs. For more information, see [Migrate IaaS resources from classic to Azure Resource Manager](../virtual-machines/migration-classic-resource-manager-overview.md).
145145
146146
- question: |
147147
What if my topology isn't decorated or my hops have missing information?
@@ -166,7 +166,7 @@ sections:
166166
- question: |
167167
Are there any limitations to using Azure Monitor and Arc Agents with connection monitor?
168168
answer: |
169-
There is currently a regional boundary when an endpoint uses Azure Monitor and Arc agents with the associated Log Analytics workspace. As a result to this limitation, the associated Log Analytics workspace must be in the same region as the Arc endpoint. Data ingested into individual workspaces can be unionized for a single view, see [Query data across Log Analytics workspaces, applications, and resources in Azure Monitor](../azure-monitor/logs/cross-workspace-query.md).
169+
There's currently a regional boundary when an endpoint uses Azure Monitor and Arc agents with the associated Log Analytics workspace. As a result to this limitation, the associated Log Analytics workspace must be in the same region as the Arc endpoint. Data ingested into individual workspaces can be unionized for a single view, see [Query data across Log Analytics workspaces, applications, and resources in Azure Monitor](../azure-monitor/logs/cross-workspace-query.md).
170170
171171
- name: Flow logs
172172
questions:
@@ -183,7 +183,7 @@ sections:
183183
- question: |
184184
What is the difference between NSG flow logs and NSG diagnostics?
185185
answer: |
186-
NSG flow logs log traffic flowing through a network security group, while NSG diagnostics returns all network security groups that your traffic is traversing and the rules of each network security group that are applied to this traffic. Use NSG diagnostics to verify that your network security group rules are being applied as expected.
186+
NSG flow logs log traffic flowing through a network security group. On the other hand, NSG diagnostics returns all network security groups that your traffic is traversing and the rules of each network security group that are applied to this traffic. Use NSG diagnostics to verify that your network security group rules are being applied as expected.
187187
188188
- question: |
189189
Can I log ESP and AH traffic using NSG flow logs?

0 commit comments

Comments
 (0)