Skip to content

Commit d4d4ce8

Browse files
committed
edit pass: automation-create-account-template
1 parent afb4cc4 commit d4d4ce8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/automation/automation-create-account-template.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,20 +48,20 @@ The JSON template is configured to prompt you for:
4848
The following parameters in the template are set with a default value for the Log Analytics workspace:
4949

5050
* *sku* - defaults to the per GB pricing tier released in the April 2018 pricing model.
51-
* *dataRetention* - defaults to thirty days.
51+
* *dataRetention* - defaults to 30 days.
5252
* *capacityReservationLevel* - defaults to 100 GB.
5353

5454
>[!WARNING]
5555
>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*.
5656
>
5757
58-
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 the Azure CLI](../azure-resource-manager/templates/deploy-cli.md).
58+
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).
5959

6060
If you're new to Azure Automation and Azure Monitor, it is important that you understand the following configuration details in order to avoid errors when you try to create, configure, and use a Log Analytics workspace linked to your new Automation account. You should:
6161

6262
* 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.
6363

64-
* Review [workspace mappings](how-to/region-mappings.md), to specify the supported regions inline or in a parameter file. This is because only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription.
64+
* Review [workspace mappings](how-to/region-mappings.md), to specify the supported regions inline or in a parameter file, because only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription.
6565

6666
* Review the [workspace design guidance](../azure-monitor/platform/design-logs-deployment.md), 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.
6767

@@ -300,7 +300,7 @@ If you're new to Azure Automation and Azure Monitor, it is important that you un
300300
az group deployment create --resource-group <my-resource-group> --name <my-deployment-name> --template-file deployAzAutomationAccttemplate.json
301301
```
302302

303-
The deployment can take a few minutes to finish. When it does, you'll see a message like the following that includes the result:
303+
The deployment can take a few minutes to finish. When it does, you'll see a message like the one below that includes the result.
304304

305305
![Example result when deployment is complete](media/automation-create-account-template/template-output.png)
306306

0 commit comments

Comments
 (0)