Merge pull request #208362 from guywi-ms/patch-22

Update agent-manage.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/agent-manage.md

@@ -1,5 +1,5 @@
 ---
-title: Managing the Azure Log Analytics agent 
+title: Manage the Azure Log Analytics agent 
 description: This article describes the different management tasks that you will typically perform during the lifecycle of the Log Analytics Windows or Linux agent deployed on a machine.
 ms.topic: conceptual
 author: guywi-ms
@@ -8,17 +8,17 @@ ms.date: 04/06/2022
 ms.reviewer: luki
 ---
 
-# Managing and maintaining the Log Analytics agent for Windows and Linux
+# Manage and maintain the Log Analytics agent for Windows and Linux
 
 After initial deployment of the Log Analytics Windows or Linux agent in Azure Monitor, you may need to reconfigure the agent, upgrade it, or remove it from the computer if it has reached the retirement stage in its lifecycle. You can easily manage these routine maintenance tasks manually or through automation, which reduces both operational error and expenses.
 
 [!INCLUDE [Log Analytics agent deprecation](../../../includes/log-analytics-agent-deprecation.md)]
 
-## Upgrading agent
+## Upgrade the agent
 
-The Log Analytics agent for Windows and Linux can be upgraded to the latest release manually or automatically depending on the deployment scenario and environment the VM is running in. The following methods can be used to upgrade the agent.
+Upgrade to the latest release of the Log Analytics agent for Windows and Linux manually or automatically based on your deployment scenario and the environment the VM is running in:
 
-| Environment | Installation Method | Upgrade method |
+| Environment | Installation method | Upgrade method |
 |--------|----------|-------------|
 | Azure VM | Log Analytics agent VM extension for Windows/Linux | Agent is automatically upgraded [after the VM model changes](../../virtual-machines/extensions/features-linux.md#how-agents-and-extensions-are-updated), unless you configured your Azure Resource Manager template to opt out by setting the property _autoUpgradeMinorVersion_ to **false**. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. Major version upgrade is always manual. See [VirtualMachineExtensionInner.AutoUpgradeMinorVersion Property](https://docs.azure.cn/dotnet/api/microsoft.azure.management.compute.fluent.models.virtualmachineextensioninner.autoupgrademinorversion?view=azure-dotnet). |
 | Custom Azure VM images | Manual install of Log Analytics agent for Windows/Linux | Updating VMs to the newest version of the agent needs to be performed from the command line running the Windows installer package or Linux self-extracting and installable shell script bundle.|
@@ -41,7 +41,7 @@ You can download the latest version of the Windows agent from your Log Analytics
 5. From the **Windows Servers** page, select the appropriate **Download Windows Agent** version to download depending on the processor architecture of the Windows operating system.
 
 >[!NOTE]
->During the upgrade of the Log Analytics agent for Windows, it does not support configuring or reconfiguring a workspace to report to. To configure the agent, you need to follow one of the supported methods listed under [Adding or removing a workspace](#adding-or-removing-a-workspace).
+>During the upgrade of the Log Analytics agent for Windows, it does not support configuring or reconfiguring a workspace to report to. To configure the agent, you need to follow one of the supported methods listed under [Add or remove a workspace](#add-or-remove-a-workspace).
 >
 
 #### To upgrade using the Setup Wizard
@@ -80,7 +80,7 @@ Run the following command to upgrade the agent.
 
 ### Enable Auto-Update for the Linux Agent
 
-The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade](../../virtual-machines/automatic-extension-upgrade.md) feature, using the following PowerShell commands.
+We recommend enabling [Automatic Extension Upgrade](../../virtual-machines/automatic-extension-upgrade.md) using these commands to update the agent automatically: 
 
 # [Powershell](#tab/PowerShellLinux)
 ```powershell
@@ -109,7 +109,7 @@ az vm extension set \
 ```
 ---
 
-## Adding or removing a workspace
+## Add or remove a workspace
 
 ### Windows agent
 The steps in this section are necessary when you want to not only reconfigure the Windows agent to report to a different workspace or to remove a workspace from its configuration, but also when you want to configure the agent to report to more than one workspace (commonly referred to as multi-homing). Configuring the Windows agent to report to multiple workspaces can only be performed after initial setup of the agent and using the methods described below.    

articles/azure-monitor/agents/agent-windows.md

@@ -3,6 +3,8 @@ title: Install Log Analytics agent on Windows computers
 description: This article describes how to connect Windows computers hosted in other clouds or on-premises to Azure Monitor with the Log Analytics agent for Windows.
 ms.topic: conceptual
 ms.date: 03/31/2022
+author: guywi-ms
+ms.author: guywild
 ms.reviewer: JeffWo
 
 ---
@@ -72,7 +74,7 @@ Regardless of the installation method used, you'll require the workspace ID and
 [![Screenshot that shows workspace details.](media/log-analytics-agent/workspace-details.png)](media/log-analytics-agent/workspace-details.png#lightbox)
 
 > [!NOTE]
-> You can't configure the agent to report to more than one workspace during initial setup. [Add or remove a workspace](agent-manage.md#adding-or-removing-a-workspace) after installation by updating the settings from Control Panel or PowerShell.
+> You can't configure the agent to report to more than one workspace during initial setup. [Add or remove a workspace](agent-manage.md#add-or-remove-a-workspace) after installation by updating the settings from Control Panel or PowerShell.
 
 ## Install the agent 
 

articles/virtual-machines/extensions/oms-windows.md

@@ -105,7 +105,7 @@ The following JSON shows the schema for the Log Analytics agent extension. The e
 Azure VM extensions can be deployed with Azure Resource Manager templates. The JSON schema detailed in the previous section can be used in an Azure Resource Manager template to run the Log Analytics agent extension during an Azure Resource Manager template deployment. A sample template that includes the Log Analytics agent VM extension can be found on the [Azure Quickstart Gallery](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/oms-extension-windows-vm). 
 
 >[!NOTE]
->The template does not support specifying more than one workspace ID and workspace key when you want to configure the agent to report to multiple workspaces. To configure the agent to report to multiple workspaces, see [Adding or removing a workspace](../../azure-monitor/agents/agent-manage.md#adding-or-removing-a-workspace).  
+>The template does not support specifying more than one workspace ID and workspace key when you want to configure the agent to report to multiple workspaces. To configure the agent to report to multiple workspaces, see [Add or remove a workspace](../../azure-monitor/agents/agent-manage.md#add-or-remove-a-workspace).  
 
 The JSON for a virtual machine extension can be nested inside the virtual machine resource, or placed at the root or top level of a Resource Manager JSON template. The placement of the JSON affects the value of the resource name and type. For more information, see [Set name and type for child resources](../../azure-resource-manager/templates/child-resource-name-type.md).