Azure > MySQL > Flexible Server

Azure > MySQL > Flexible Server > Delete

Process events for Azure MySQL service Flexible Server resources.

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


Azure > Resource Group

Azure > MySQL > Flexible Server > Router

Update the tags for Azure MySQL flexible server.


Azure > MySQL > Flexible Server > Set Tags

Sets the Minimum TLS Version for `Azure > MySQL > Flexible Server`.


Azure > MySQL > Flexible Server > Set Minimum TLS Version

Update Encryption in Transit settings required for `Azure > MySQL > Flexible Server`.


Azure > MySQL > Flexible Server > Update Encryption in Transit

Take an action when an Azure MySQL flexible server is not active based on the&#92;n`Azure &gt; MySQL &gt; Flexible Server &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; MySQL &gt; Flexible Server &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 > MySQL > Flexible Server > Active > Age

Azure > MySQL > Flexible Server > Active > Last Modified

Azure > MySQL > Flexible Server > Active

Take an action when an Azure MySQL flexible server is not approved based on `Azure &gt; MySQL &gt; Flexible Server &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 > MySQL > Flexible Server > Approved > Custom

Azure > MySQL > Flexible Server > Approved > Usage

Azure > MySQL > Enabled

Azure > MySQL > Flexible Server > Approved > Regions

Azure > MySQL > Flexible Server > Approved

Record and synchronize details for the Azure MySQL flexible server 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; MySQL &gt; Flexible Server &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > MySQL > Flexible Server > Regions

Azure > MySQL > Flexible Server > CMDB

Discover all Azure MySQL flexible server 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; MySQL &gt; Flexible Server &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > MySQL > Flexible Server > Discovery

Define the Encryption in Transit settings required for `Azure &gt; MySQL &gt; Flexible Server`.&#92;n&#92;nThe Encryption in Transit control compares the Encryption in Transit settings against the Encryption in Transit policies for the resource (Azure &gt; MySQL &gt; Flexible Server &gt; Encryption in Transit), raises an alarm, and takes the defined enforcement action.&#92;n

Azure > MySQL > Flexible Server > Encryption in Transit

Define the Minimum TLS Version setting required for `Azure &gt; MySQL &gt; Flexible Server`.&#92;n

Azure > MySQL > Flexible Server > Minimum TLS Version

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

Azure > MySQL > Flexible Server > Tags

Take an action when an Azure MySQL server is not active based on the&#92;n`Azure &gt; MySQL &gt; Server &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; MySQL &gt; Server &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 > MySQL > Server [Deprecated] > Active > Age

Azure > MySQL > Server [Deprecated] > Active > Last Modified

Azure > MySQL > Server [Deprecated]

Azure > MySQL > Server [Deprecated] > Active

Take an action when an Azure MySQL server is not approved based on `Azure &gt; MySQL &gt; Server &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 > MySQL > Server [Deprecated] > Approved > Custom

Azure > MySQL > Server [Deprecated] > Approved > Usage

Azure > MySQL > Server [Deprecated] > Approved > Regions

Azure > MySQL > Server [Deprecated] > Approved

Record and synchronize details for the Azure MySQL server 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; MySQL &gt; Server &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n&#92;nThis resource type has been deprecated and will be removed in the next major version. Please refer [end of support](https://techcommunity.microsoft.com/blog/adformysql/azure-database-for-mysql---single-server-retirement---key-updates-and-migration-/4055198) for more information.&#92;n

Azure > MySQL > Server [Deprecated] > Regions

Azure > MySQL > Server [Deprecated] > CMDB

Discover all Azure MySQL server 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; MySQL &gt; Server &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n&#92;nThis resource type has been deprecated and will be removed in the next major version. Please refer [end of support](https://techcommunity.microsoft.com/blog/adformysql/azure-database-for-mysql---single-server-retirement---key-updates-and-migration-/4055198) for more information.&#92;n

Azure > MySQL > Server [Deprecated] > Discovery

Define the Encryption in Transit settings required for `Azure &gt; MySQL &gt; Server`.&#92;n&#92;nThe Encryption in Transit control compares the Encryption in Transit settings against the Encryption in Transit policies for the resource&#92;n(Azure &gt; MySQL &gt; Server &gt; Encryption in Transit), raises an alarm, and takes the defined enforcement action&#92;n

Azure > MySQL > Server [Deprecated] > Encryption in Transit

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

Azure > MySQL > Server [Deprecated] > Tags

test01

GP_Gen5_2

test

flexibleServer

flexibleServerAka

invalid - Hyphen can not be at last position

flexibleServerName

flexibleServerServiceNow

mySql

mySqlAka

test-02

server

serverAka

serverName

serverServiceNow

azure-mysql

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermissions for Azure MySQL 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-mysql

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

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

A list of Azure regions in which Azure MySQL flexible servers 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 MySQL flexible server is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; MySQL &gt; Flexible Server &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure MySQL flexible server is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure MySQL flexible server is not approved, it will be subject to the action specified in the `Azure &gt; MySQL &gt; Flexible Server &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 MySQL flexible server 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; MySQL &gt; Flexible Server &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

azure_mysql_flexible_server_encryption_in_transit

Azure CIS v2.0.0 - Section 4 - Database Services

azure_mysql_flexible_server_minimum_tls_version

A list of Azure regions in which Azure MySQL flexible servers are supported for use.&#92;n&#92;nAny flexible servers 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

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

A list of Azure regions in which Azure MySQL 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 MySQL resources&#39; Approved &gt; Regions policies.&#92;n

Azure > MySQL

Azure > MySQL > Approved Regions [Default]

Azure > MySQL > Permissions > Levels

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

Azure > MySQL > Permissions

Azure > MySQL > 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.MySQL/MySQL/delete&quot;: operator&#92;n  - &quot;Microsoft.MySQL/MySQL/write&quot;: admin&#92;n  - &quot;Microsoft.MySQL/MySQL/read&quot;: readonly&#92;n```&#92;n

A list of Azure regions in which Azure MySQL 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 MySQL resources&#39; Regions policies.&#92;n

Azure > MySQL > Regions

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

Azure > MySQL > Tags Template [Default]

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

A list of Azure regions in which Azure MySQL servers 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 MySQL server is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; MySQL &gt; Server &gt; Approved` policy.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

Determine whether the Azure MySQL server is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure MySQL server is not approved, it will be subject to the action specified in the `Azure &gt; MySQL &gt; Server &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 MySQL server 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; MySQL &gt; Server &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&#92;n**Note**: This resource type has been deprecated and will be removed in the next major version. Please refer [end of support](https://techcommunity.microsoft.com/blog/adformysql/azure-database-for-mysql---single-server-retirement---key-updates-and-migration-/4055198) for more information.&#92;n

azure_mysql_server_encryption_in_transit

A list of Azure regions in which Azure MySQL servers are supported for use.&#92;n&#92;nAny servers 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

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

The Flexible Server resource type is a fully managed database service with built-in high availability and security that can be used to create and manage new MySQL databases in Azure.&#92;n

Azure > CIS v2.0 > 04 - Database Services > 4.04 - MySQL Database > 4.04.01 - Ensure &#39;Enforce SSL connection&#39; is set to &#39;Enabled&#39; for Standard MySQL Database Server

Azure > CIS v2.0 > 04 - Database Services > 4.04 - MySQL Database > 4.04.02 - Ensure &#39;TLS Version&#39; is set to &#39;TLSV1.2&#39; for MySQL flexible Database Server

Azure > CIS v2.0 > 04 - Database Services > 4.04 - MySQL Database > 4.04.03 - Ensure server parameter &#39;audit_log_enabled&#39; is set to &#39;ON&#39; for MySQL Database Server

Azure > CIS v2.0 > 04 - Database Services > 4.04 - MySQL Database > 4.04.04 - Ensure server parameter &#39;audit_log_events&#39; has &#39;CONNECTION&#39; set for MySQL Database Server

Azure > MySQL > Flexible Server > ServiceNow > Configuration Item

Azure > MySQL > Flexible Server > ServiceNow > Configuration Item > Record

The MySQL service provides scalable database capacity in the Azure cloud. It allows users to launch and manage MySQL databases, known as instances, that can support applications and services.&#92;n

Azure

Azure > MySQL > Server > ServiceNow

The Server resource type is a fully managed database service that can be used to deploy and manage MySQL databases in the cloud.&#92;n

Mod: azure-mysql

Recommended Version

Resource Types

Controls

IAM Roles

Policies

Policy Packs