Delete the Azure Automation Automation Account.


Azure > Automation > Automation Account

automationAccount

Azure > Automation > Automation Account > Delete

Process events for Azure Automation service Automation Account resources.

The router receives events from the event handler and creates, updates, or deletes Automation Account resources in the CMDB.


resourceGroup

Azure > Automation > Automation Account > Router

Update the tags for Azure Automation automation account.


Azure > Automation > Automation Account > Set Tags

Azure > Automation > Runbook

runbook

Azure > Automation > Runbook > Delete

Process events for Azure Automation service Runbook resources.

The router receives events from the event handler and creates, updates, or deletes Runbook resources in the CMDB.


Azure > Automation > Runbook > Router

Update the tags for Azure Automation runbook.


Azure > Automation > Runbook > Set Tags

Sets the Public Network Access setting for Azure Automation Account to enabled or disabled.


Azure > Automation > Automation Account > Set Public Network Access

Take an action when an Azure Automation automation account is not active based on the&#92;n`Azure &gt; Automation &gt; Automation Account &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Automation Account &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Automation > Automation Account > Active

Take an action when an Azure Automation automation account is not approved based on `Azure &gt; Automation &gt; Automation Account &gt; Approved &gt; * policies`.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Automation Account > Approved

Record and synchronize details for the Azure Automation automation account into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If&#92;nregion is not in `Azure &gt; Automation &gt; Automation Account &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > Automation > Automation Account > CMDB

Discover all Azure Automation automation account resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/discovery) control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n&#92;n**Note:** Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in `Azure &gt; Automation &gt; Automation Account &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > Resource Group

Azure > Automation > Automation Account > Discovery

Define the Public Network Access settings required for `Azure &gt; Automation &gt; Automation Account`.&#92;n&#92;nThe Public Network Access control determines whether the public network access for Azure Automation Account should be Enabled or Disabled.&#92;n&#92;nWhen public network access is disabled, the Automation Account can only be accessed through private endpoints. This provides enhanced security by preventing public internet access to the automation account.&#92;n

Azure > Automation > Automation Account > Public Network Access

Take an action when an Azure Automation automation account tags is not updated based on the `Azure &gt; Automation &gt; Automation Account &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; Automation &gt; Automation Account &gt; Tags &gt; Template`, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Automation > Automation Account > Tags

Take an action when an Azure Automation runbook is not active based on the&#92;n`Azure &gt; Automation &gt; Runbook &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Runbook &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Automation > Runbook > Active

Take an action when an Azure Automation runbook is not approved based on `Azure &gt; Automation &gt; Runbook &gt; Approved &gt; * policies`.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Runbook > Approved

Record and synchronize details for the Azure Automation runbook into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If&#92;nregion is not in `Azure &gt; Automation &gt; Runbook &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > Automation > Runbook > CMDB

Discover all Azure Automation runbook resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/discovery) control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n&#92;n**Note:** Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in `Azure &gt; Automation &gt; Runbook &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > Automation > Runbook > Discovery

Take an action when an Azure Automation runbook tags is not updated based on the `Azure &gt; Automation &gt; Runbook &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; Automation &gt; Runbook &gt; Tags &gt; Template`, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Automation > Runbook > Tags

automation

automationAccountAka

invalid - Hyphen can not be at last position

automationAccountName

automationAccountServiceNow

automationAka

runbookAka

runbookName

runbookServiceNow

azure-automation

Determine the action to take when an Azure Automation automation account, based on the `Azure &gt; Automation &gt; Automation Account &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Automation Account &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Automation automation account&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Automation Account &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Automation > Automation Account > Active > Age

The number of days since the Azure Automation automation account was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Automation Account &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

Azure > Automation > Automation Account > Active > Last Modified

Determine the action to take when an Azure Automation automation account is not approved based on `Azure &gt; Automation &gt; Automation Account &gt; Approved &gt; *` policies.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Automation automation account is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation automation account is not approved, it will be subject to the action specified in the `Azure &gt; Automation &gt; Automation Account &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

string

Azure > Automation > Automation Account > Approved > Custom

A list of Azure regions in which Azure Automation automation accounts are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and &#39;?&#39; wildcard characters.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation automation account is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; Automation &gt; Automation Account &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Automation Account > Approved > Regions

Determine whether the Azure Automation automation account is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation automation account is not approved, it will be subject to the action specified in the `Azure &gt; Automation &gt; Automation Account &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Automation Account > Approved > Usage

Configure whether to record and synchronize details for the Azure Automation automation account into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If region is not in `Azure &gt; Automation &gt; Automation Account &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n&#92;n(**Note**: Setting CMDB to **&quot;Skip&quot;** will also pause these changes.)&#92;n

Define the Public Network Access settings required for `Azure &gt; Automation &gt; Automation Account`.&#92;n&#92;nThe Public Network Access policy determines whether the public network access for Azure Automation Account should be Enabled or Disabled.&#92;n&#92;nWhen public network access is disabled, the Automation Account can only be accessed through private endpoints. This provides enhanced security by preventing public internet access to the automation account.&#92;n

A list of Azure regions in which Azure Automation automation accounts are supported for use.&#92;n&#92;nAny automation accounts in a region not listed here will not be recorded in CMDB.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n

Azure > Subscription

Azure > Automation > Automation Account > Regions

Determine the action to take when an Azure Automation automation account tags are not updated based on the `Azure &gt; Automation &gt; Automation Account &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure Automation automation account tags include tags defined in `Azure &gt; Automation &gt; Automation Account &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Automation Account Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The template is used to generate the keys and values for Azure Automation automation account.&#92;n&#92;nTags not defined in Automation Account Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Automation > Automation Account > Tags > Template

A list of Azure regions in which Azure Automation resources are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Automation resources&#39; Approved &gt; Regions policies.&#92;n

Azure > Automation

Azure > Automation > Approved Regions [Default]

Azure > Automation > Enabled

Configure whether permissions policies are in effect for Azure Automation&#92;nThis setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)&#92;n

Azure > Automation > Permissions

Define the permissions levels that can be used to grant access to Storage an&#92;nAzure Subscription.  Permissions levels defined will appear in the UI to assign&#92;naccess to Guardrails users.&#92;n

Azure > Automation > Permissions > Levels

A map of Azure API to Guardrails Permission Level used to customize Guardrails&#92;nstandard permissions. You can add, remove or redefine the mapping of&#92;nAzure API operations to Guardrails permissions levels here.&#92;n&#92;n```&#92;nexample:&#92;n  - &quot;Microsoft.Automation/Automation/delete&quot;: operator&#92;n  - &quot;Microsoft.Automation/Automation/write&quot;: admin&#92;n  - &quot;Microsoft.Automation/Automation/read&quot;: readonly&#92;n```&#92;n

Azure > Automation > Permissions > Levels > Modifiers

A list of Azure regions in which Azure Automation resources are supported for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Automation resources&#39; Regions policies.&#92;n

Azure > Automation > Regions

A template used to generate the keys and values for Azure Automation resources.&#92;n&#92;nBy default, all Automation resource Tags &gt; Template policies will use this value.&#92;n

Azure > Automation > Tags Template [Default]

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermissions for Azure Automation that is used as input to the control that manages&#92;nthe IAM stack.&#92;n

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-automation

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure Automation that is used as input to the&#92;nstack that manages the Guardrails IAM permissions objects.&#92;n

Azure > Turbot > Permissions > Compiled > Levels

Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-automation

Determine the action to take when an Azure Automation runbook, based on the `Azure &gt; Automation &gt; Runbook &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Runbook &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Automation runbook&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Runbook &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Automation > Runbook > Active > Age

The number of days since the Azure Automation runbook was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Automation &gt; Runbook &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

Azure > Automation > Runbook > Active > Last Modified

Determine the action to take when an Azure Automation runbook is not approved based on `Azure &gt; Automation &gt; Runbook &gt; Approved &gt; *` policies.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure Automation runbook is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation runbook is not approved, it will be subject to the action specified in the `Azure &gt; Automation &gt; Runbook &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Azure > Automation > Runbook > Approved > Custom

A list of Azure regions in which Azure Automation runbooks are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and &#39;?&#39; wildcard characters.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation runbook is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; Automation &gt; Runbook &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Runbook > Approved > Regions

Determine whether the Azure Automation runbook is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Automation runbook is not approved, it will be subject to the action specified in the `Azure &gt; Automation &gt; Runbook &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Azure > Automation > Runbook > Approved > Usage

Configure whether to record and synchronize details for the Azure Automation runbook into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If region is not in `Azure &gt; Automation &gt; Runbook &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n&#92;n(**Note**: Setting CMDB to **&quot;Skip&quot;** will also pause these changes.)&#92;n

A list of Azure regions in which Azure Automation runbooks are supported for use.&#92;n&#92;nAny runbooks in a region not listed here will not be recorded in CMDB.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n

Azure > Automation > Runbook > Regions

Determine the action to take when an Azure Automation runbook tags are not updated based on the `Azure &gt; Automation &gt; Runbook &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure Automation runbook tags include tags defined in `Azure &gt; Automation &gt; Runbook &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Runbook Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The template is used to generate the keys and values for Azure Automation runbook.&#92;n&#92;nTags not defined in Runbook Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Automation > Runbook > Tags > Template

The Automation service helps streamline management tasks in both Azure and hybrid cloud environments. It enables automation of processes like system updates, configuration management, and the execution of scheduled tasks using runbooks.&#92;n

Azure

The Automation Account resource type is a container for automation resources like runbooks, DSC configurations, and schedules. It enables automation of tasks and centralized management across Azure and hybrid environments.&#92;n

The Runbook resource type defines an automated workflow or task sequence within an automation account. Runbooks are used to automate repetitive tasks, manage resources, and orchestrate processes across Azure or hybrid environments. They can be executed on-demand or scheduled.&#92;n

Mod: azure-automation

Recommended Version

Resource Types

Controls

IAM Roles

Policies