Merge pull request #215815 from itechedit/four-network-watcher-articles

edit pass: four network-watcher articles

Author: ShawnJackson

articles/network-watcher/azure-monitor-agent-with-connection-monitor.md

@@ -1,58 +1,73 @@
 ---
-title: Monitor Network Connectivity using Azure Monitor Agent
-description: This article describes how to monitor network connectivity in Connection Monitor using the Azure monitor agent.
+title: Monitor network connectivity by using Azure Monitor Agent
+description: This article describes how to monitor network connectivity in Connection Monitor by using Azure Monitor Agent.
 services: network-watcher
 author: v-ksreedevan
 ms.service: network-watcher
 ms.custom: ignite-2022
 ms.topic: how-to
 ms.date: 09/11/2022
 ms.author: v-ksreedevan
-#Customer intent: I need to monitor a connection using Azure Monitor agent.
+#Customer intent: I need to monitor a connection by using Azure Monitor Agent.
 ---
 
-# Monitor Network Connectivity using Azure Monitor Agent with Connection Monitor
+# Monitor network connectivity by using Azure Monitor Agent with Connection Monitor
 
-Connection Monitor supports the Azure Monitor Agent extension, thereby eliminating the dependency on the legacy Log Analytics agent. 
+Connection Monitor supports the Azure Monitor Agent extension, which eliminates any dependency on the legacy Log Analytics agent. 
 
-With Azure Monitor Agent, a single agent consolidates all the features necessary to address all connectivity logs and metrics data collection needs across Azure and On-premises machines compared to running various monitoring agents. 
+With Azure Monitor Agent, a single agent consolidates all the features necessary to address all connectivity logs and metrics data collection needs across Azure and on-premises machines compared to running various monitoring agents. 
 
-The Azure Monitor Agent provides enhanced security and performance capabilities, effective cost savings with efficient data collection and ease of troubleshooting with simpler data collection management for Log Analytics agent. 
+Azure Monitor Agent provides the following benefits:
+* Enhanced security and performance capabilities
+* Effective cost savings with efficient data collection
+* Ease of troubleshooting, with simpler data collection management for the Log Analytics agent 
 
-[Learn more](../azure-monitor/agents/agents-overview.md) about Azure Monitor Agent.
+[Learn more about Azure Monitor Agent](../azure-monitor/agents/agents-overview.md).
 
 To start using Connection Monitor for monitoring, do the following:
 * Install monitoring agents
 * Create a connection monitor
 * Analyze monitoring data and set alerts
 * Diagnose issues in your network
 
-The following sections provide details on the installation of Monitor Agents. For more information, see [Connection Monitor](connection-monitor-overview.md).
+The following sections provide details on the installation of monitoring agents. For more information, see [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md).
 
-## Installing monitoring agents for Azure and Non-Azure resources
+## Install monitoring agents for Azure and non-Azure resources
 
-The Connection Monitor relies on lightweight executable files to run connectivity checks. It supports connectivity checks from both Azure environments and on-premises environments. The executable file that you use depends on whether your VM is hosted on Azure or on-premises.
+Connection Monitor relies on lightweight executable files to run connectivity checks. It supports connectivity checks from both Azure and on-premises environments. The executable file that you use depends on whether your virtual machine (VM) is hosted on Azure or on-premises.
 
 ### Agents for Azure virtual machines and scale sets
 
-Refer [here](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets) to install agents for Azure virtual machines and scale sets.
+To install agents for Azure virtual machines and virtual machine scale sets, see the "Agents for Azure virtual machines and virtual machine scale sets" section of [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets).
 
 ### Agents for on-premises machines
 
 To make Connection Monitor recognize your on-premises machines as sources for monitoring, do the following: 
-* Enable your hybrid endpoints to [ARC Enabled Servers](../azure-arc/overview.md).
+
+* Enable your hybrid endpoints to [Azure Arc-enabled servers](../azure-arc/overview.md).
+
 * Connect hybrid machines by installing the [Azure Connected Machine agent](../azure-arc/servers/overview.md) on each machine.
-  This agent doesn't deliver any other functionality, and it doesn't replace the Azure Monitor Agent. The Azure Connected Machine agent simply enables you to manage your Windows and Linux machines hosted outside of Azure on your corporate network or other cloud providers. 
-* Install the [Azure Monitor Agent](../azure-monitor/agents/agents-overview.md) to enable the Network Watcher extension.
-* The agent collects monitoring logs and data from the hybrid sources and delivers it to Azure Monitor.
+
+  This agent doesn't deliver any other functionality, and it doesn't replace Azure Monitor Agent. The Azure Connected Machine agent simply enables you to manage the Windows and Linux machines that are hosted outside of Azure on your corporate network or other cloud providers. 
+
+* [Install Azure Monitor Agent](../azure-monitor/agents/agents-overview.md) to enable the Network Watcher extension.
+
+  The agent collects monitoring logs and data from the hybrid sources and delivers it to Azure Monitor.
 
 ## Coexistence with other agents
 
-The Azure Monitor agent can coexist (run side by side on the same machine) with the legacy Log Analytics agents so that you can continue to use their existing functionality during evaluation or migration. While this allows you to begin the transition, given the limitations, you must review the following:
-* Ensure that you do not collect duplicate data because it could alter query results and affect downstream features like alerts, dashboards, or workbooks. For example, VM insights uses the Log Analytics agent to send performance data to a Log Analytics workspace. You might also have configured the workspace to collect Windows events and Syslog events from agents. If you install the Azure Monitor agent and create a data collection rule for these same events and performance data, it will result in duplicate data. So, ensure you're not collecting the same data from both agents. If you are, ensure they're collecting from different machines or going to separate destinations.
-* Besides data duplication, this would also generate more charges for data ingestion and retention.
-* Running two telemetry agents on the same machine would result in double the resource consumption, including but not limited to CPU, memory, storage space and network bandwidth.
+Azure Monitor Agent can coexist with, or run side by side on the same machine as, the legacy Log Analytics agents. You can continue to use their existing functionality during evaluation or migration. 
+
+Although this coexistence allows you to begin the transition, there are certain limitations. Keep in mind the following considerations:
+
+* Do not collect duplicate data, because it could alter query results and affect downstream features such as alerts, dashboards, or workbooks. 
+
+   For example, the VM insights feature uses the Log Analytics agent to send performance data to a Log Analytics workspace. You might also have configured the workspace to collect Windows events and Syslog events from agents. If you install Azure Monitor Agent and create a data collection rule for the same events and performance data, it will result in duplicate data. Ensure that you're not collecting the same data from both agents. If you are collecting duplicate data, make sure that it's coming from different machines or going to separate destinations.
+
+* Data duplication would also generate more charges for data ingestion and retention.
+
+* Running two telemetry agents on the same machine would result in double the resource consumption, including but not limited to CPU, memory, storage space, and network bandwidth.
 
 ## Next steps 
 
-- Install [Azure Connected machine agent](connection-monitor-connected-machine-agent.md).
+- [Install the Azure Connected Machine agent](connection-monitor-connected-machine-agent.md)

articles/network-watcher/connection-monitor-connected-machine-agent.md

@@ -1,58 +1,60 @@
 ---
-title: Install agents for connection monitor
-description: This article describes how to install Azure Connected machine agent
+title: Install the Azure Connected Machine agent for Connection Monitor
+description: This article describes how to install Azure Connected Machine agent
 services: network-watcher
 author: v-ksreedevan
 ms.service: network-watcher
 ms.custom: ignite-2022
 ms.topic: how-to
 ms.date: 09/11/2022
 ms.author: v-ksreedevan
-#Customer intent: I need to monitor a connection using Azure Monitor agent.
+#Customer intent: I need to monitor a connection by using Azure Monitor Agent.
 ---
 
-# Install Azure Connected Machine agent to enable Arc 
+# Install the Azure Connected Machine agent to enable Azure Arc 
 
-This article describes the procedure to install the Azure Connected Machine agent.
+This article describes how to install the Azure Connected Machine agent.
 
 ## Prerequisites
 
-* An Azure account with an active subscription, else [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-* Administrator permissions to install and configure the Connected Machine agent. On Linux, the installation and configuration is done using the root account, and on Windows, with an account that is a member of the Local Administrators group.
-* Register the Microsoft.HybridCompute, Microsoft.GuestConfiguration, and Microsoft.HybridConnectivity resource providers on your subscription. You can [register these resource providers](../azure-arc/servers/prerequisites.md#azure-resource-providers) ahead of time, or while completing the steps in this article.
-* Review the [agent prerequisites](../azure-arc/servers/prerequisites.md) and ensure the following:
+* An Azure account with an active subscription. If you don't already have an account, [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+* Administrator permissions to install and configure the Connected Machine agent. On Linux, you install and configure it by using the root account, and on Windows, you use an account that's a member of the Local Administrators group.
+* Register the Microsoft.HybridCompute, Microsoft.GuestConfiguration, and Microsoft.HybridConnectivity resource providers on your subscription. You can [register these resource providers](../azure-arc/servers/prerequisites.md#azure-resource-providers) either ahead of time or as you're completing the steps in this article.
+* Review the [agent prerequisites](../azure-arc/servers/prerequisites.md), and ensure that:
   * Your target machine is running a supported [operating system](../azure-arc/servers/prerequisites.md#supported-operating-systems).
   * Your account has the [required Azure built-in roles](../azure-arc/servers/prerequisites.md#required-permissions).
   * The machine is in a [supported region](../azure-arc/overview.md).
-  * If the machine connects through a firewall or proxy server to communicate over the Internet, make sure the listed [URLs](../azure-arc/servers/network-requirements.md#urls) aren't blocked.
+  * If the machine connects through a firewall or proxy server to communicate over the internet, the listed URLs in [Connected Machine agent network requirements](../azure-arc/servers/network-requirements.md#urls) aren't blocked.
 
-## Generate installation script
+## Generate an installation script
 
-Use the Azure portal to create a script that automates the download and installation of the agent and establishes the connection with Azure Arc.
+Use the Azure portal to create a script that automates the downloading and installation of the agent and establishes the connection with Azure Arc.
 
-1. In the Azure portal, search for **Servers - Azure Arc** and select it.
+1. In the [Azure portal](https://portal.azure.com), search for **Servers - Azure Arc**, and then select it in the results list.
 
-  1. On the **Servers - Azure Arc** page, select **Add**.
+1. On the **Servers - Azure Arc** page, select **Add**.
 
-1. On the next screen, from the **Add a single server** tile, select **Generate script**.
+1. On the **Add a single server** tile, select **Generate script**.
 
-1. Review the information on the **Prerequisites** page, then select **Next**.
+1. Review the information on the **Prerequisites** page, and then select **Next**.
 
 1. On the **Resource details** page, provide the following:
 
-   1. Select the subscription and resource group where you want the machine to be managed within Azure.
-   1. For **Region**, choose the Azure region in which the server's metadata will be stored.
-   1. For **Operating system**, select the operating system of the server you want to connect.
-   1. For **Connectivity method**, choose how the Azure Connected Machine agent should connect to the internet. If you select **Proxy server**, enter the proxy server IP address, or the name and port number that the machine will use in the format `http://<proxyURL>:<proxyport>`.
-   1. Select **Next**.
+   a. Select the subscription and resource group where you want the machine to be managed within Azure.  
+   b. For **Region**, select the Azure region in which the server's metadata will be stored.  
+   c. For **Operating system**, select the operating system of the server you want to connect.  
+   d. For **Connectivity method**, select how the Azure Connected Machine agent should connect to the internet. If you select **Proxy server**, enter the proxy server IP address, or enter the name and port number that the machine will use, in the format `http://<proxyURL>:<proxyport>`.  
+   e. Select **Next**.
 
-1. On the **Tags** page, review the default **Physical location tags** suggested and enter a value, or specify one or more **Custom tags** to support your standards. Then select **Next**.
+1. On the **Tags** page, review the default **Physical location tags** suggested and either enter a value or specify one or more **Custom tags** to support your standards. 
+
+1. Select **Next**.
 
 1. On the **Download and run script** page, select the **Register** button to register the required resource providers in your subscription, if you haven't already done so.
 
 1. In the **Download or copy the following script** section, review the script. If you want to make any changes, use the **Previous** button to go back and update your selections. Otherwise, select **Download** to save the script file.
 
-## Install the agent using the script
+## Install the agent by using the script
 
 After you've generated the script, the next step is to run it on the server that you want to onboard to Azure Arc. The script will download the Connected Machine agent from the Microsoft Download Center, install the agent on the server, create the Azure Arc-enabled server resource, and associate it with the agent.
 
@@ -62,19 +64,21 @@ Follow the steps corresponding to the operating system of your server.
 
 1. Sign in to the server.
 
-1. Open an elevated 64-bit PowerShell command prompt.
+1. Open an elevated 64-bit PowerShell Command Prompt window.
+
+1. Change to the folder or share that you copied the script to, and then execute it on the server by running the `./OnboardingScript.ps1` script.
 
-1. Change to the folder or share that you copied the script to, then execute it on the server by running the `./OnboardingScript.ps1` script.
+# [Linux agent](#tab/LinuxScript)
 
-### [Linux agent](#tab/LinuxScript)
+To install the Linux agent, run one of the following commands:
 
-1. To install the Linux agent on the target machine that can directly communicate to Azure, run the following command:
+* On the target machine that can directly communicate to Azure, run:
 
     ```bash
     bash ~/Install_linux_azcmagent.sh
     ```
 
-1. Alternately, if the target machine communicates through a proxy server, run the following command:
+* If the target machine communicates through a proxy server, run:
 
     ```bash
     bash ~/Install_linux_azcmagent.sh --proxy "{proxy-url}:{proxy-port}"
@@ -83,17 +87,20 @@ Follow the steps corresponding to the operating system of your server.
 
 ## Verify the connection with Azure Arc
 
-After you install the agent and configure it to connect to Azure Arc-enabled servers, go to the Azure portal to verify that the server has successfully connected. View your machine in the [Azure portal](https://aka.ms/hybridmachineportal).
+After you install the agent and configure it to connect to Azure Arc-enabled servers, go to the Azure portal to verify that the server is successfully connected. View your machine in the [Azure portal](https://aka.ms/hybridmachineportal).
 
 ## Connect hybrid machines to Azure by using PowerShell
 
-For servers enabled with Azure Arc, you can take manual steps mentioned above to enable them for one or more Windows or Linux machines in your environment. Alternatively, you can use the PowerShell cmdlet Connect-AzConnectedMachine to download the Connected Machine agent, install the agent, and register the machine with Azure Arc. The cmdlet downloads the Windows agent package (Windows Installer) from the Microsoft Download Center, and the Linux agent package from the Microsoft package repository.
-Refer to the linked document to discover the required steps to install the [Arc agent via PowerShell](../azure-arc/servers/onboard-powershell.md)
+For servers that are enabled with Azure Arc, you can take the previously mentioned manual steps to enable them for one or more Windows or Linux machines in your environment. 
+
+Alternatively, you can use the PowerShell cmdlet `Connect-AzConnectedMachine` to download the Azure Connected Machine agent, install the agent, and register the machine with Azure Arc. The cmdlet downloads the Windows agent package (Windows Installer) from the Microsoft Download Center, and it downloads the Linux agent package from the Microsoft package repository.
+
+Refer to the linked document to discover the required steps to install the [Azure Arc agent via PowerShell](../azure-arc/servers/onboard-powershell.md).
 
 ## Connect hybrid machines to Azure from Windows Admin Center
 
-You can enable Azure Arc-enabled servers for one or more Windows machines in your environment manually or use the Windows Admin Center to deploy the Connected Machine agent and register your on-premises servers without having to perform any steps outside of this tool. [Learn more](../azure-arc/servers/onboard-windows-admin-center.md) about installing Arc agent via the Windows Admin Center.
+You can enable Azure Arc-enabled servers for one or more Windows machines in your environment manually, or you can use the Windows Admin Center to deploy the Azure Connected Machine agent and register your on-premises servers without having to perform any steps outside of this tool. For more information about installing the Azure Arc agent via Windows Admin Center, see [Connect hybrid machines to Azure from Windows Admin Center](../azure-arc/servers/onboard-windows-admin-center.md).
 
 ## Next steps
 
-- Install [Azure Monitor agent](connection-monitor-install-azure-monitor-agent.md).
+- [Install Azure Monitor Agent](connection-monitor-install-azure-monitor-agent.md)