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
title: List of built-in policy definitions for Azure App Service
3
+
description: Lists Azure Policy built-in policy definitions for Azure App Service. These built-ins provide common approaches to managing your Azure resources.
4
+
ms.date: 05/01/2020
5
+
ms.topic: sample
6
+
ms.custom: subject-policy-samples
7
+
---
8
+
# Azure Policy built-in policy definitions for Azure App Service
9
+
10
+
This page is an index of [Azure Policy](../governance/policy/overview.md) built-in policy
11
+
definitions for Azure App Service. For additional Azure Policy built-ins for other services, see
Copy file name to clipboardExpand all lines: articles/automation/automation-create-account-template.md
+37-33Lines changed: 37 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Use Azure Resource Manager templates to create Automation account | Microsoft Docs
2
+
title: Use Azure Resource Manager templates to create an Automation account | Microsoft Docs
3
3
description: You can use an Azure Resource Manager template to create an Azure Automation account.
4
4
ms.service: automation
5
5
ms.subservice: update-management
@@ -10,18 +10,18 @@ ms.date: 04/24/2020
10
10
11
11
---
12
12
13
-
# Create Automation account using Azure Resource Manager template
13
+
# Create an Automation account by using an Azure Resource Manager template
14
14
15
-
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:
15
+
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:
16
16
17
-
*Creation of a Azure Monitor Log Analytics workspace.
18
-
*Creation of an Azure Automation account.
17
+
*Automates the creation of an Azure Monitor Log Analytics workspace.
18
+
*Automates the creation of an Azure Automation account.
19
19
* Links the Automation account to the Log Analytics workspace.
20
20
21
-
The template does not automate the onboarding of one or more Azure or non-Azure VMs, or solutions.
21
+
The template doesn't automate the onboarding of Azure or non-Azure virtual machines or solutions.
22
22
23
23
>[!NOTE]
24
-
>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).
24
+
>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).
25
25
26
26
## API versions
27
27
@@ -32,40 +32,40 @@ The following table lists the API version for the resources used in this example
32
32
| Workspace | workspaces | 2017-03-15-preview |
33
33
| Automation account | automation | 2015-10-31 |
34
34
35
-
## Before using the template
35
+
## Before you use the template
36
36
37
-
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).
37
+
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).
38
38
39
-
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).
39
+
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).
40
40
41
41
The JSON template is configured to prompt you for:
42
42
43
-
* The name of the workspace
44
-
* The region to create the workspace in
45
-
* The name of the Automation account
46
-
* The region to create the account in
43
+
* The name of the workspace.
44
+
* The region to create the workspace in.
45
+
* The name of the Automation account.
46
+
* The region to create the account in.
47
47
48
48
The following parameters in the template are set with a default value for the Log Analytics workspace:
49
49
50
-
* sku - defaults to the new Per-GB pricing tier released in the April 2018 pricing model
51
-
*data retention - defaults to thirty days
52
-
*capacity reservation - defaults to 100 GB
50
+
**sku*defaults to the per GB pricing tier released in the April 2018 pricing model.
51
+
**dataRetention*defaults to 30 days.
52
+
**capacityReservationLevel*defaults to 100 GB.
53
53
54
54
>[!WARNING]
55
-
>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**.
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 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
-
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.
60
+
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.
61
61
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.
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
-
*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.
64
+
*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.
65
65
66
-
* 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.
66
+
* 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.
67
67
68
-
## Deploy template
68
+
## Deploy the template
69
69
70
70
1. Copy and paste the following JSON syntax into your file:
71
71
@@ -92,7 +92,7 @@ It is important to understand the following configuration details if you are new
92
92
],
93
93
"defaultValue": "pergb2018",
94
94
"metadata": {
95
-
"description": "Pricing tier: perGB2018 or legacy tiers (Free, Standalone, PerNode, Standard or Premium) which are not available to all customers."
95
+
"description": "Pricing tier: perGB2018 or legacy tiers (Free, Standalone, PerNode, Standard or Premium), which are not available to all customers."
96
96
}
97
97
},
98
98
"dataRetention": {
@@ -101,14 +101,14 @@ It is important to understand the following configuration details if you are new
101
101
"minValue": 7,
102
102
"maxValue": 730,
103
103
"metadata": {
104
-
"description": "Number of days of retention. Workspaces in the legacy Free pricing tier can only have 7 days."
104
+
"description": "Number of days of retention. Workspaces in the legacy Free pricing tier can have only 7 days."
105
105
}
106
106
},
107
107
"immediatePurgeDataOn30Days": {
108
108
"type": "bool",
109
109
"defaultValue": "[bool('false')]",
110
110
"metadata": {
111
-
"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."
111
+
"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."
112
112
}
113
113
},
114
114
"location": {
@@ -135,7 +135,7 @@ It is important to understand the following configuration details if you are new
135
135
},
136
136
"sampleGraphicalRunbookDescription": {
137
137
"type": "String",
138
-
"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
138
+
"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
139
139
},
140
140
"sampleGraphicalRunbookContentUri": {
141
141
"type": "String",
@@ -147,7 +147,7 @@ It is important to understand the following configuration details if you are new
147
147
},
148
148
"samplePowerShellRunbookDescription": {
149
149
"type": "String",
150
-
"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
150
+
"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
151
151
},
152
152
"samplePowerShellRunbookContentUri": {
153
153
"type": "String",
@@ -159,7 +159,7 @@ It is important to understand the following configuration details if you are new
159
159
},
160
160
"samplePython2RunbookDescription": {
161
161
"type": "String",
162
-
"defaultValue": " An example runbook which gets all the ARM resources using the Run As Account (Service Principal)."
162
+
"defaultValue": " An example runbook that gets all the Resource Manager resources by using the Run As account (service principal)."
163
163
},
164
164
"samplePython2RunbookContentUri": {
165
165
"type": "String",
@@ -282,11 +282,11 @@ It is important to understand the following configuration details if you are new
282
282
}
283
283
```
284
284
285
-
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.
285
+
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.
286
286
287
287
3. Save this file as deployAzAutomationAccttemplate.json to a local folder.
288
288
289
-
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.
289
+
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.
290
290
291
291
**PowerShell**
292
292
@@ -300,10 +300,14 @@ It is important to understand the following configuration details if you are new
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 complete. When it finishes, you see a message similar to 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 following that includes the result.
304
304
305
305
306
306
307
307
## Next steps
308
308
309
309
Now that you have an Automation account, you can create runbooks and automate manual processes.
310
+
311
+
* To get started with PowerShell runbooks, see [Create a PowerShell runbook](automation-first-runbook-textual-powershell.md).
312
+
* To get started with PowerShell workflow runbooks, see [Create a PowerShell Workflow runbook](automation-first-runbook-textual.md).
313
+
* To get started with Python 2 runbooks, see [Create a Python runbook](automation-first-runbook-textual-python2.md).
title: List of built-in policy definitions for Azure Automation
3
+
description: Lists Azure Policy built-in policy definitions for Azure Automation. These built-ins provide common approaches to managing your Azure resources.
4
+
ms.date: 04/30/2020
5
+
ms.topic: sample
6
+
ms.custom: subject-policy-samples
7
+
---
8
+
# Azure Policy built-in policy definitions for Azure Automation
9
+
10
+
This page is an index of [Azure Policy](../governance/policy/overview.md) built-in policy
11
+
definitions for Azure Automation. For additional Azure Policy built-ins for other services,
12
+
see [Azure Policy built-in definitions](../governance/policy/samples/built-in-policies.md).
13
+
14
+
The name of each built-in links to the policy definition in Azure portal. Use the link in the
title: List of built-in policy definitions for Azure App Configuration
3
+
description: Lists Azure Policy built-in policy definitions for Azure App Configuration. These built-ins provide common approaches to managing your Azure resources.
4
+
ms.date: 05/01/2020
5
+
ms.topic: sample
6
+
author: lisaguthrie
7
+
ms.author: lcozzens
8
+
ms.service: azure-app-configuration
9
+
ms.custom: subject-policy-samples
10
+
---
11
+
# Azure Policy built-in policy definitions for Azure App Configuration
12
+
13
+
This page is an index of [Azure Policy](../governance/policy/overview.md) built-in policy
14
+
definitions for Azure App Configuration. For additional Azure Policy built-ins for other services, see
0 commit comments