You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/automation-create-account-template.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,20 +48,20 @@ The JSON template is configured to prompt you for:
48
48
The following parameters in the template are set with a default value for the Log Analytics workspace:
49
49
50
50
**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.
52
52
**capacityReservationLevel* - defaults to 100 GB.
53
53
54
54
>[!WARNING]
55
55
>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*.
56
56
>
57
57
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).
59
59
60
60
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:
61
61
62
62
* 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.
63
63
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.
65
65
66
66
* 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.
67
67
@@ -300,7 +300,7 @@ If you're new to Azure Automation and Azure Monitor, it is important that you un
300
300
az group deployment create --resource-group <my-resource-group> --name <my-deployment-name> --template-file deployAzAutomationAccttemplate.json
301
301
```
302
302
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.
304
304
305
305

0 commit comments