Merge pull request #111783 from BethWilke/branch122

Fixing task 1707219

Author: Kellylorenebaker

articles/automation/automation-update-azure-modules.md

@@ -11,28 +11,28 @@ ms.topic: conceptual
 
 To update the Azure modules in your Automation account you need to use the [Update Azure modules runbook](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update), which is available as open source. To start using the **Update-AutomationAzureModulesForAccount** runbook to update your Azure modules, download it from the [Update Azure modules runbook repository](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) on GitHub. You can then import it into your Automation account or run it as a script. To learn how to import a runbook in your Automation account, see [Import a runbook](manage-runbooks.md#importing-a-runbook).
 
-The most common AzureRM PowerShell modules are provided by default in each Automation account. The Azure team updates the Azure modules regularly, therefore to keep up to date you will want to use the [Update-AutomationAzureModulesForAccount](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) runbook to update the modules in your Automation accounts.
+The most common PowerShell modules are provided by default in each Automation account. The Azure team updates the Azure modules regularly. Therefore, to keep the modules in your Automation accounts up to date, you should use the [Update-AutomationAzureModulesForAccount](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) runbook.
 
-Because modules are updated regularly by the product group, changes can occur with the included cmdlets. This action may negatively impact your runbooks depending on the type of change, such as renaming a parameter or deprecating a cmdlet entirely.
+Because modules are updated regularly by the product group, changes can occur with the included cmdlets. These changes, for example, renaming a parameter or deprecating a cmdlet entirely, can negatively affect your runbooks.
 
-To avoid impacting your runbooks and the processes they automate, test and validate before proceeding. If you don't have a dedicated Automation account intended for this purpose, consider creating one so that you can test many different scenarios during the development of your runbooks. This testing should include iterative changes such as updating the PowerShell modules.
+To avoid impacting your runbooks and the processes they automate, test and validate before proceeding. If you don't have a dedicated Automation account intended for this purpose, consider creating one so that you can test many different scenarios during the development of your runbooks. This testing should include iterative changes, such as updating the PowerShell modules.
 
 If you develop your scripts locally, it's recommended to have the same module versions locally that you have in your Automation account when testing to ensure you'll receive the same results. After the results are validated and you've applied any changes required, you can move the changes to production.
 
 > [!NOTE]
 > A new Automation account might not contain the latest modules.
 
 > [!NOTE]
-> You will not be able to delete global modules - modules that Automation provides out of the box.
+> You will not be able to delete global modules, which are modules that Automation provides out of the box.
 
 >[!NOTE]
 >This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). 
 
 ## Considerations
 
-The following are some considerations to take into account when using this process to update your Azure Modules:
+The following are some considerations to take into account when using this article to update your Azure Modules:
 
-* The runbook described in this article supports updating the Azure, AzureRM, and Az modules by default. Review the [Update Azure modules runbook README](https://github.com/microsoft/AzureAutomation-Account-Modules-Update/blob/master/README.md) for more information on updating Az.Automation modules with this runbook. There are additional important factors that you need to take into account when using the `Az` modules in your Automation account. To learn more, see [Using Az modules in your Automation account](az-modules.md).
+* The runbook described in this article supports updating the Azure, AzureRM, and Az modules by default. Review the [Update Azure modules runbook README](https://github.com/microsoft/AzureAutomation-Account-Modules-Update/blob/master/README.md) for more information on updating Az.Automation modules with this runbook. There are additional important factors that you need to take into account when using the Az modules in your Automation account. To learn more, see [Using Az modules in your Automation account](az-modules.md).
 
 * Before starting this runbook, make sure your Automation account has an [Azure Run As account credential](manage-runas-account.md) created.
 

articles/automation/automation-update-management-deploy-template.md

@@ -6,8 +6,7 @@ ms.subservice: update-management
 ms.topic: conceptual
 author: mgoedtel
 ms.author: magoedte
-ms.date: 04/15/2020
-
+ms.date: 03/30/2020
 ---
 
 # Onboard Update Management solution using Azure Resource Manager template
@@ -16,19 +15,19 @@ You can use [Azure Resource Manager templates](../azure-resource-manager/templat
 
 * Creation of a Azure Monitor Log Analytics workspace.
 * Creation of an Azure Automation account.
-* Links the Automation account to the Log Analytics workspace if not already linked.
-* Onboard the Azure Automation Update Management solution
+* Linking the Automation account to the Log Analytics workspace, if not already linked.
+* Onboarding the Azure Automation Update Management solution.
 
 The template does not automate the onboarding of one or more Azure or non-Azure VMs.
 
->[!NOTE]
->Creation of the Automation Run As account is not supported when using an Azure Resource Manager template. To create a Run As account manually from the portal or with PowerShell, see [Manage Run As account](manage-runas-account.md).
+If you already have a Log Analytics workspace and Automation account deployed in a supported region in your subscription, they are not linked. The workspace doesn't already have the Update Management solution deployed. Using this template successfully creates the link and deploys the Update Management solution. 
 
-If you already have a Log Analytics workspace and Automation account deployed in a supported region in your subscription, they are not linked, and the workspace doesn't already have the Update Management solution deployed, using this template successfully creates the link and deploys the Update Management solution. 
+>[!NOTE]
+>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).
 
 ## API versions
 
-The following table lists the API version for the resources used in this example.
+The following table lists the API versions for the resources used in this template.
 
 | Resource | Resource type | API version |
 |:---|:---|:---|
@@ -38,18 +37,18 @@ The following table lists the API version for the resources used in this example
 
 ## Before using the template
 
-If you choose to install and use PowerShell locally, this article requires the Azure PowerShell Az module. Run `Get-Module -ListAvailable Az` to find the version. If you need to upgrade, see [Install the Azure PowerShell module](/powershell/azure/install-az-ps). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure. With Azure PowerShell, deployment uses [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment).
+If you choose to install and use PowerShell locally, this article requires the Azure PowerShell Az module. Run `Get-Module -ListAvailable Az` to find the version. If you need to upgrade, see [Install the Azure PowerShell module](/powershell/azure/install-az-ps). If you are running PowerShell locally, you also need to run [Connect-AzAccount](https://docs.microsoft.com/powershell/module/az.accounts/connect-azaccount?view=azps-3.7.0) to create a connection with Azure. With Azure PowerShell, deployment uses [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment).
 
 If you choose to install and use the CLI locally, this article requires that you are running the Azure CLI version 2.1.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest). With Azure CLI, this deployment uses [az group deployment create](https://docs.microsoft.com/cli/azure/group/deployment?view=azure-cli-latest#az-group-deployment-create). 
 
 The JSON template is configured to prompt you for:
 
 * The name of the workspace
-* The region to create the workspace in
+* The region in which to create the workspace
 * The name of the Automation account
-* The region to create the account in
+* The region in which to create the account
 
-The JSON template specifies a default value for the other parameters that would likely be used as a standard configuration in your environment. You can store the template in an Azure storage account for shared access in your organization. For further information about working with templates, see [Deploy resources with Resource Manager templates and Azure CLI](../azure-resource-manager/templates/deploy-cli.md).
+The JSON template specifies a default value for the other parameters that are likely to be used for a standard configuration in your environment. You can store the template in an Azure storage account for shared access in your organization. For further information about working with templates, see [Deploy resources with Resource Manager templates and Azure CLI](../azure-resource-manager/templates/deploy-cli.md).
 
 The following parameters in the template are set with a default value for the Log Analytics workspace:
 
@@ -58,11 +57,11 @@ The following parameters in the template are set with a default value for the Lo
 * capacity reservation - defaults to 100 GB
 
 >[!WARNING]
->If creating or configuring a Log Analytics workspace in a subscription that has opted into the new April 2018 pricing model, the only valid Log Analytics pricing tier is **PerGB2018**.
+>If creating or configuring a Log Analytics workspace in a subscription that has opted into the April 2018 pricing model, the only valid Log Analytics pricing tier is **PerGB2018**.
 >
 
 >[!NOTE]
->Before using this template, review [additional details](../azure-monitor/platform/template-workspace-configuration.md#create-a-log-analytics-workspace) to fully understand workspace configuration options such as access control mode, pricing tier, retention, and capacity reservation level. If you are new to Azure Monitor logs and have not deployed a workspace already, you should review the [workspace design](../azure-monitor/platform/design-logs-deployment.md) guidance to learn about access control, and an understanding of the design implementation strategies we recommend for your organization.
+>Before using this template, review [additional details](../azure-monitor/platform/template-workspace-configuration.md#create-a-log-analytics-workspace) to fully understand workspace configuration options, such as access control mode, pricing tier, retention, and capacity reservation level. If you are new to Azure Monitor logs and have not deployed a workspace already, you should review the [workspace design](../azure-monitor/platform/design-logs-deployment.md) guidance to learn about access control, and understand the design implementation strategies we recommend for your organization.
 
 ## Deploy template
 
@@ -213,7 +212,7 @@ The following parameters in the template are set with a default value for the Lo
                 "sku": {
                     "name": "Basic"
                 }
-            }
+            },
         },
         {
             "apiVersion": "2015-11-01-preview",
@@ -234,7 +233,7 @@ The following parameters in the template are set with a default value for the Lo
 
 2. Edit the template to meet your requirements. Consider creating a [Resource Manager parameters file](../azure-resource-manager/templates/parameter-files.md) instead of passing parameters as inline values.
 
-3. Save this file as deployUMSolutiontemplate.json to a local folder.
+3. Save this file to a local folder as **deployUMSolutiontemplate.json**.
 
 4. You are ready to deploy this template. You can use either PowerShell or the Azure CLI. When you're prompted for a workspace and Automation account name, provide a name that is globally unique across all Azure subscriptions.
 

articles/automation/automation-update-management-groups.md

@@ -1,5 +1,5 @@
 ---
-title: Use dynamic groups with Azure Update Management
+title: Use dynamic groups with Azure Automation Update Management
 description: This article describes how dynamic groups work with Azure Automation Update Management.
 services: automation
 ms.subservice: update-management
@@ -8,11 +8,11 @@ ms.topic: conceptual
 ---
 # Use dynamic groups with Update Management
 
-Update Management provides the ability to target a dynamic group of Azure or non-Azure VMs for update deployments. These groups are evaluated at deployment time so you do not have to edit your deployment to add machines.
+Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. These groups, defined by queries, are evaluated at deployment time so that you don't have to edit your deployment to add machines.
 
 ## Azure machines
 
-These groups are defined by a query, when an update deployment begins, the members of that group are evaluated. Dynamic groups do not work with classic VMs. When defining your query, the following items can be used together to populate the dynamic group:
+Dynamic groups do not work with classic VMs. When defining your query, the following items can be used together to populate a dynamic group:
 
 * Subscription
 * Resource groups
@@ -21,16 +21,16 @@ These groups are defined by a query, when an update deployment begins, the membe
 
 ![Select groups](./media/automation-update-management/select-groups.png)
 
-To preview the results of a dynamic group, click the **Preview** button. This preview shows the group membership at that time, in this example, we are searching for machines with the tag **Role** is equal to **BackendServer**. If more machines have this tag added, they will be added to any future deployments against that group.
+To preview the results of a dynamic group, click **Preview**. The preview shows the group membership at the current time. In the example, we're searching for machines having the tag `Role` for the group **BackendServer**. If more machines have this tag added, they are added to any future deployments against that group.
 
 ![preview groups](./media/automation-update-management/preview-groups.png)
 
 ## Non-Azure machines
 
-For non-Azure machines, saved searches also referred to as computer groups, are used to create the dynamic group. To learn how to create a saved search, see [Creating a computer group](../azure-monitor/platform/computer-groups.md#creating-a-computer-group). Once your group is created you can select it from the list of saved searches. Click **Preview** to preview the computers in the saved search at that time.
+For non-Azure machines, saved searches, also referred to as computer groups, are used to create the dynamic group. To learn how to create a saved search, see [Creating a computer group](../azure-monitor/platform/computer-groups.md#creating-a-computer-group). Once your group is created, you can select it from the list of saved searches. Click **Preview** to preview the computers in the saved search at that time.
 
 ![Select groups](./media/automation-update-management/select-groups-2.png)
 
 ## Next steps
 
-After creating a dynamic group, you can [Create an Update Deployment](automation-tutorial-update-management.md)
+After creating a dynamic group, you can [Create an Update Deployment](automation-tutorial-update-management.md).