Merge pull request #268812 from halkazwini/nw-faq

Update NW FAQ

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ metadata:
   ms.author: halkazwini
   ms.service: network-watcher
   ms.topic: faq
-  ms.date: 02/15/2024
+  ms.date: 03/12/2024
 title: "Network Watcher frequently asked questions (FAQ)"
 summary: |
   This article provides answers to some of the frequently asked questions asked about Azure Network Watcher.
@@ -141,7 +141,7 @@ sections:
       - question: |
           Does connection monitor support classic VMs?
         answer: |
-          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).
+          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).
 
       - question: |
           What if my topology isn't decorated or my hops have missing information?
@@ -163,6 +163,11 @@ sections:
         answer: |
           There's no protocol selection option in connection monitor (classic). Tests in connection monitor (classic) only use the TCP protocol, and that's why, during the migration, we create a TCP configuration in tests in the new connection monitor.
 
+      - question: |
+          Are there any limitations to using Azure Monitor and Arc Agents with connection monitor?
+        answer: |
+          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).
+
   - name: Flow logs
     questions:
       - question: |
@@ -175,6 +180,11 @@ sections:
         answer: |
           Flow log data is collected outside the path of your network traffic, so it doesn't affect network throughput or latency. You can create or delete flow logs without any risk of impact to network performance.
 
+      - question: |
+          What is the difference between NSG flow logs and NSG diagnostics?
+        answer: |
+          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.
+
       - question: |
           Can I log ESP and AH traffic using NSG flow logs?
         answer: |