Merge pull request #245174 from halkazwini/nw-tut-cm-vms

Update and rename article

Author: v-shils

articles/network-watcher/.openpublishing.redirection.network-watcher.json

@@ -3,7 +3,13 @@
         {
             "source_path_from_root": "/articles/network-watcher/enable-network-watcher-flow-log-settings.md",
             "redirect_url": "/azure/network-watcher/network-watcher-create",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/network-watcher/connection-monitor.md",
+            "redirect_url": "/azure/network-watcher/monitor-vm-communication",
             "redirect_document_id": true
         }
+
     ]
 }

articles/network-watcher/connection-monitor-overview.md

@@ -118,8 +118,6 @@ To enable the Network Performance Monitor solution for on-premises machines, do
 
    After you've enabled the solution, the workspace takes a couple of minutes to be displayed.
 
-   :::image type="content" source="./media/connection-monitor/network-performance-monitor-solution-enable.png" alt-text="Screenshot showing how to add the Network Performance Monitor solution in Connection Monitor." lightbox="./media/connection-monitor/network-performance-monitor-solution-enable.png":::
-
 Unlike Log Analytics agents, the Network Performance Monitor solution can be configured to send data only to a single Log Analytics workspace.
 
 If you wish to escape the installation process for enabling the Network Watcher extension, you can proceed with the creation of Connection Monitor and allow auto enablement of monitoring solution on your on-premises machines. 

articles/network-watcher/connection-monitor-virtual-machine-scale-set.md

@@ -101,9 +101,7 @@ After the scale set has been created, enable the Network Watcher extension in th
 
 1. Under **Settings**, select **Extensions**. 
 
-1. Select **Add extension**, and then select **Network Watcher Agent for Windows**, as shown in the following image:
-
-   :::image type="content" source="./media/connection-monitor/nw-agent-extension.png" alt-text="Screenshot that shows the Network Watcher extension addition.":::
+1. Select **Add extension**, and then select **Network Watcher Agent for Windows**.
 
 1. Under **Network Watcher Agent for Windows**, select **Create**.
 1. Under **Install extension**, select **OK**.
@@ -197,8 +195,6 @@ In the Azure portal, to create a test group in a connection monitor, do the foll
 
    * To choose on-premises agents, select the **Non–Azure endpoints** tab. By default, agents are grouped into workspaces by region. All these workspaces have the Network Performance Monitor configured. 
 
- 1. If you need to add Network Performance Monitor to your workspace, get it from [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/solarwinds.solarwinds-orion-network-performance-monitor?tab=Overview). For information about how to add Network Performance Monitor, see [Monitoring solutions in Azure Monitor](/previous-versions/azure/azure-monitor/insights/solutions). For information about how to configure agents for on-premises machines, see [Agents for on-premises machines](connection-monitor-overview.md#agents-for-on-premises-machines).
- 
  1. Under **Create Connection Monitor**, on the **Basics** pane, the default region is selected. If you change the region, you can choose agents from workspaces in the new region. You can select one or more agents or subnets. In the **Subnet** view, you can select specific IPs for monitoring. If you add multiple subnets, a custom on-premises network named **OnPremises_Network_1** will be created. You can also change the **Group by** selector to group by agents.
 
     :::image type="content" source="./media/connection-monitor-2-preview/add-non-azure-sources.png" alt-text="Screenshot that shows the 'Add Sources' pane and the 'Non-Azure endpoints' pane in Connection monitor.":::

articles/network-watcher/index.yml

@@ -74,7 +74,7 @@ landingContent:
           - text: Troubleshoot connections
             url: network-watcher-connectivity-portal.md
           - text: Monitor communication between VMs
-            url: connection-monitor.md          
+            url: monitor-vm-communication.md          
 
   # Card (optional)
   - title: Log network traffic