Azure > DNS > Record Set

Azure > DNS > Record Set > Delete

Process events for Azure DNS service Record Set resources.

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


Azure > Resource Group

Azure > DNS > Record Set > Router

Update the tags for Azure DNS record set.


Azure > DNS > Record Set > Set Tags

Azure > DNS > Zone

Azure > DNS > Zone > Delete

Process events for Azure DNS service Zone resources.

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


Azure > DNS > Zone > Router

Azure > DNS > Zone > Set Tags

Take an action when an Azure DNS record set is not active based on the&#92;n`Azure &gt; DNS &gt; Record Set &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; DNS &gt; Record Set &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 > DNS > Record Set > Active > Age

Azure > DNS > Record Set > Active > Last Modified

Azure > DNS > Record Set > Active

This control serves as a hierarchical parent for more specific Allowed controls, such as region-based controls and custom rule-based controls.&#92;n

Azure > DNS > Record Set > Allowed

Take an action when an Azure DNS record set is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the record set is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the record set is not allowed, 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 if not allowed and resource is new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Azure > DNS > Record Set > Allowed > Custom > Rules

Azure > DNS > Record Set > Allowed > Custom

Take an action when an Azure DNS record set is not approved based on `Azure &gt; DNS &gt; Record Set &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 > DNS > Record Set > Approved > Custom

Azure > DNS > Record Set > Approved > Usage

Azure > DNS > Enabled

Azure > DNS > Record Set > Approved

Record and synchronize details for the Azure DNS record set 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

Azure > DNS > Record Set > CMDB

Discover all Azure DNS record set 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

Azure > DNS > Record Set > Discovery

Take an action when an Azure DNS record set tags is not updated based on the `Azure &gt; DNS &gt; Record Set &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; DNS &gt; Record Set &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 > DNS > Record Set > Tags > Template

Azure > DNS > Record Set > Tags

Take an action when an Azure DNS zone is not active based on the&#92;n`Azure &gt; DNS &gt; Zone &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; DNS &gt; Zone &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 > DNS > Zone > Active > Age

Azure > DNS > Zone > Active > Last Modified

Azure > DNS > Zone > Active

Azure > DNS > Zone > Allowed

Take an action when an Azure DNS zone is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the zone is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the zone is not allowed, 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 if not allowed and resource is new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Azure > DNS > Zone > Allowed > Custom > Rules

Azure > DNS > Zone > Allowed > Custom

Take an action when an Azure DNS zone is not approved based on `Azure &gt; DNS &gt; Zone &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 > DNS > Zone > Approved > Custom

Azure > DNS > Zone > Approved > Usage

Azure > DNS > Zone > Approved

Record and synchronize details for the Azure DNS zone 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

Azure > DNS > Zone > CMDB

Discover all Azure DNS zone 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

Azure > DNS > Zone > Discovery

Take an action when an Azure DNS zone tags is not updated based on the `Azure &gt; DNS &gt; Zone &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; DNS &gt; Zone &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 > DNS > Zone > Tags > Template

Azure > DNS > Zone > Tags

dnsAka

abtestrs

recordSet

recordSetAka

recordSetId

recordSetName

recordSetServiceNow

testdz.com

zone

zoneAka

zoneId

invalid -  can not contain number at last

zoneName

zoneServiceNow

azure-dns

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

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Subscription

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

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure DNS 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-dns

The Event Grid event pattern used by the Azure DNS module to specify&#92;nwhich events to forward to the Guardrails Event Handlers [Event Grid].&#92;n&#92;nThis policy automatically generates operation filters based on which&#92;nresource types have CMDB enabled. Only enabled resource types will&#92;nhave their events forwarded to Guardrails.&#92;n

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns > @turbot/azure-dns

Azure > DNS

Azure > DNS > Permissions > Levels

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

Azure > DNS > Permissions

Azure > DNS > Permissions > Levels > Modifiers

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

A map of Azure API to Guardrails Permission Level used to customize Guardrails&#39;&#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.DNS/DNS/delete&quot;: operator&#92;n  - &quot;Microsoft.DNS/DNS/write&quot;: admin&#92;n  - &quot;Microsoft.DNS/DNS/read&quot;: readonly&#92;n```&#92;n

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

Azure > DNS > Tags Template [Default]

Determine the action to take when an Azure DNS record set, based on the `Azure &gt; DNS &gt; Record Set &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; DNS &gt; Record Set &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 DNS record set&#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; DNS &gt; Record Set &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

The number of days since the Azure DNS record set 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; DNS &gt; Record Set &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

This policy serves as a hierarchical parent for more specific Allowed policies, such as region-based policies and custom rule-based policies.&#92;n

Determine the action to take when an Azure DNS record set is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the record set is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the record set is not allowed, the 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 if not allowed and resource is new`, the control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Determine whether the Azure DNS record set is allowed to exist based on custom rules.&#92;n&#92;nThis policy will be evaluated by the `Allowed &gt; Custom` control. If an Azure DNS record set is not allowed, it will be subject to the action specified in the `Allowed &gt; Custom` policy.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Allowed`, `Not allowed` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Allowed` or `Not allowed`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

string

Determine the action to take when an Azure DNS record set is not approved based on `Azure &gt; DNS &gt; Record Set &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 DNS record set is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure DNS record set is not approved, it will be subject to the action specified in the `Azure &gt; DNS &gt; Record Set &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

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

Configure whether to record and synchronize details for the Azure DNS record set 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

Determine the action to take when an Azure DNS record set tags are not updated based on the `Azure &gt; DNS &gt; Record Set &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure DNS record set tags include tags defined in `Azure &gt; DNS &gt; Record Set &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Record Set 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 DNS record set.&#92;n&#92;nTags not defined in Record Set 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

Determine the action to take when an Azure DNS zone, based on the `Azure &gt; DNS &gt; Zone &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; DNS &gt; Zone &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 DNS zone&#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; DNS &gt; Zone &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

The number of days since the Azure DNS zone 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; DNS &gt; Zone &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

Determine the action to take when an Azure DNS zone is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the zone is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the zone is not allowed, the 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 if not allowed and resource is new`, the control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Determine whether the Azure DNS zone is allowed to exist based on custom rules.&#92;n&#92;nThis policy will be evaluated by the `Allowed &gt; Custom` control. If an Azure DNS zone is not allowed, it will be subject to the action specified in the `Allowed &gt; Custom` policy.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Allowed`, `Not allowed` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Allowed` or `Not allowed`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Determine the action to take when an Azure DNS zone is not approved based on `Azure &gt; DNS &gt; Zone &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 DNS zone is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure DNS zone is not approved, it will be subject to the action specified in the `Azure &gt; DNS &gt; Zone &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

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

Configure whether to record and synchronize details for the Azure DNS zone 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

Determine the action to take when an Azure DNS zone tags are not updated based on the `Azure &gt; DNS &gt; Zone &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure DNS zone tags include tags defined in `Azure &gt; DNS &gt; Zone &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Zone 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 DNS zone.&#92;n&#92;nTags not defined in Zone 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 DNS service provides reliable and scalable domain name system services in the Azure cloud. It allows users to host and manage their DNS domain and records, known as zones and record sets, which can be used to direct traffic to the desired endpoints and services.&#92;n

Azure

Azure > DNS > Record Set > ServiceNow

The Record Set resource type represents a collection of DNS records with the same name and type that can be created and managed within an Azure DNS Zone.&#92;n

Azure > DNS > Record Set > ServiceNow > Configuration Item

Azure > DNS > Record Set > ServiceNow > Configuration Item > Record

Azure > DNS > Zone > ServiceNow

The Zone resource type is a domain name system that can be used to host and manage the domain&#39;s DNS records, enabling one to connect domain names to IP addresses within the Azure environment.&#92;n

Mod: azure-dns

Recommended Version

Resource Types

Controls

IAM Roles

Policies