Merge pull request #113517 from ttorble/automation-create-account-template

ShawnJackson · web-flow · commit f2930ab316ab · 2020-05-07T13:42:58.000-05:00
edit pass: automation-create-account-template
diff --git a/articles/automation/automation-create-account-template.md b/articles/automation/automation-create-account-template.md
@@ -1,5 +1,5 @@
 ---
-title: Use Azure Resource Manager templates to create Automation account | Microsoft Docs
+title: Use Azure Resource Manager templates to create an Automation account | Microsoft Docs
 description: You can use an Azure Resource Manager template to create an Azure Automation account.
 ms.service:  automation
 ms.subservice: update-management
@@ -10,18 +10,18 @@ ms.date: 04/24/2020
 
 ---
 
-# Create Automation account using Azure Resource Manager template
+# Create an Automation account by using an Azure Resource Manager template
 
-You can use [Azure Resource Manager templates](../azure-resource-manager/templates/template-syntax.md) to create an Azure Automation account in your resource group. This article provides a sample template that automates the following:
+You can use [Azure Resource Manager templates](../azure-resource-manager/templates/template-syntax.md) to create an Azure Automation account in your resource group. This article provides a sample template that:
 
-* Creation of a Azure Monitor Log Analytics workspace.
-* Creation of an Azure Automation account.
+* Automates the creation of an Azure Monitor Log Analytics workspace.
+* Automates the creation of an Azure Automation account.
 * Links the Automation account to the Log Analytics workspace.
 
-The template does not automate the onboarding of one or more Azure or non-Azure VMs, or solutions. 
+The template doesn't automate the onboarding of Azure or non-Azure virtual machines or solutions. 
 
 >[!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).
+>Creation of the Automation Run As account is not supported when you're using an Azure Resource Manager template. To create a Run As account manually from the portal or with PowerShell, see [Manage Run As accounts](manage-runas-account.md).
 
 ## API versions
 
@@ -32,40 +32,40 @@ The following table lists the API version for the resources used in this example
 | Workspace | workspaces | 2017-03-15-preview |
 | Automation account | automation | 2015-10-31 | 
 
-## Before using the template
+## Before you use 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're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure. With PowerShell, the 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). 
+If you choose to install and use the Azure CLI locally, this article requires that you're running version 2.1.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install the Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest). With the 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 name of the Automation account
-* The region to create the account in
+* The name of the workspace.
+* The region to create the workspace in.
+* The name of the Automation account.
+* The region to create the account in.
 
 The following parameters in the template are set with a default value for the Log Analytics workspace:
 
-* sku - defaults to the new Per-GB pricing tier released in the April 2018 pricing model
-* data retention - defaults to thirty days
-* capacity reservation - defaults to 100 GB
+* *sku* defaults to the per GB pricing tier released in the April 2018 pricing model.
+* *dataRetention* defaults to 30 days.
+* *capacityReservationLevel* 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 you want to create or configure 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*.
 >
 
-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 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 more information about working with templates, see [Deploy resources with Resource Manager templates and the Azure CLI](../azure-resource-manager/templates/deploy-cli.md).
 
-It is important to understand the following configuration details if you are new to Azure Automation and Azure Monitor, in order to avoid errors when attempting to create, configure, and use a Log Analytics workspace linked to your new Automation account.
+If you're new to Azure Automation and Azure Monitor, it's important that you understand the following configuration details. They can help you avoid errors when you try to create, configure, and use a Log Analytics workspace linked to your new Automation account. 
 
-* 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.
+* 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.
 
-* Because only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription, review [Workspace mappings](how-to/region-mappings.md) to specify the supported regions inline or in a parameters file.
+* Review [workspace mappings](how-to/region-mappings.md) to specify the supported regions inline or in a parameter file. Only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription.
 
-* 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.
+* If you're new to Azure Monitor logs and have not deployed a workspace already, you should review the [workspace design guidance](../azure-monitor/platform/design-logs-deployment.md). It will help you to learn about access control, and understand the design implementation strategies we recommend for your organization.
 
-## Deploy template
+## Deploy the template
 
 1. Copy and paste the following JSON syntax into your file:
 
@@ -92,7 +92,7 @@ It is important to understand the following configuration details if you are new
             ],
             "defaultValue": "pergb2018",
             "metadata": {
-                "description": "Pricing tier: perGB2018 or legacy tiers (Free, Standalone, PerNode, Standard or Premium) which are not available to all customers."
+                "description": "Pricing tier: perGB2018 or legacy tiers (Free, Standalone, PerNode, Standard or Premium), which are not available to all customers."
             }
         },
         "dataRetention": {
@@ -101,14 +101,14 @@ It is important to understand the following configuration details if you are new
             "minValue": 7,
             "maxValue": 730,
             "metadata": {
-                "description": "Number of days of retention. Workspaces in the legacy Free pricing tier can only have 7 days."
+                "description": "Number of days of retention. Workspaces in the legacy Free pricing tier can have only 7 days."
             }
         },
         "immediatePurgeDataOn30Days": {
             "type": "bool",
             "defaultValue": "[bool('false')]",
             "metadata": {
-                "description": "If set to true when changing retention to 30 days, older data will be immediately deleted. Use this with extreme caution. This only applies when retention is being set to 30 days."
+                "description": "If set to true when changing retention to 30 days, older data will be immediately deleted. Use this with extreme caution. This applies only when retention is being set to 30 days."
             }
         },
         "location": {
@@ -135,7 +135,7 @@ It is important to understand the following configuration details if you are new
             },
             "sampleGraphicalRunbookDescription": {
                 "type": "String",
-    			"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
+    			"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
             },
             "sampleGraphicalRunbookContentUri": {
                 "type": "String",
@@ -147,7 +147,7 @@ It is important to understand the following configuration details if you are new
             },
             "samplePowerShellRunbookDescription": {
                 "type": "String",
-    			"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
+    			"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
             },
             "samplePowerShellRunbookContentUri": {
                 "type": "String",
@@ -159,7 +159,7 @@ It is important to understand the following configuration details if you are new
             },
             "samplePython2RunbookDescription": {
                 "type": "String",
-    			"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
+    			"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
             },
             "samplePython2RunbookContentUri": {
                 "type": "String",
@@ -282,11 +282,11 @@ It is important to understand the following configuration details if you are new
     }
     ```
 
-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.
+2. Edit the template to meet your requirements. Consider creating a [Resource Manager parameter file](../azure-resource-manager/templates/parameter-files.md) instead of passing parameters as inline values.
 
 3. Save this file as deployAzAutomationAccttemplate.json to a local folder.
 
-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.
+4. You're 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's globally unique across all your Azure subscriptions.
 
     **PowerShell**
 
@@ -300,10 +300,14 @@ It is important to understand the following configuration details if you are new
     az group deployment create --resource-group <my-resource-group> --name <my-deployment-name> --template-file deployAzAutomationAccttemplate.json
     ```
 
-    The deployment can take a few minutes to complete. When it finishes, you see a message similar to the following that includes the result:
+    The deployment can take a few minutes to finish. When it does, you'll see a message like the following that includes the result.
 
     ![Example result when deployment is complete](media/automation-create-account-template/template-output.png)
 
 ## Next steps
 
 Now that you have an Automation account, you can create runbooks and automate manual processes.
+
+* To get started with PowerShell runbooks, see [Create a PowerShell runbook](automation-first-runbook-textual-powershell.md).
+* To get started with PowerShell workflow runbooks, see [Create a PowerShell Workflow runbook](automation-first-runbook-textual.md).
+* To get started with Python 2 runbooks, see [Create a Python runbook](automation-first-runbook-textual-python2.md).
