Policy types for @turbot/azure-provider
- Azure > Provider > API Management > CMDB
- Azure > Provider > API Management > Registered
- Azure > Provider > Automation > CMDB
- Azure > Provider > Automation > Registered
- Azure > Provider > Billing > CMDB
- Azure > Provider > Billing > Registered
- Azure > Provider > Compute > CMDB
- Azure > Provider > Compute > Registered
- Azure > Provider > Container Service > CMDB
- Azure > Provider > Container Service > Registered
- Azure > Provider > Cost Management > CMDB
- Azure > Provider > Cost Management > Registered
- Azure > Provider > DB for MySQL > CMDB
- Azure > Provider > DB for MySQL > Registered
- Azure > Provider > DB for PostgreSQL > CMDB
- Azure > Provider > DB for PostgreSQL > Registered
- Azure > Provider > Data Factory > CMDB
- Azure > Provider > Data Factory > Registered
- Azure > Provider > Data Lake Analytics > CMDB
- Azure > Provider > Data Lake Analytics > Registered
- Azure > Provider > Databricks > CMDB
- Azure > Provider > Databricks > Registered
- Azure > Provider > Document DB > CMDB
- Azure > Provider > Document DB > Registered
- Azure > Provider > Domain Registration > CMDB
- Azure > Provider > Domain Registration > Registered
- Azure > Provider > HDInsight > CMDB
- Azure > Provider > HDInsight > Registered
- Azure > Provider > Insights > CMDB
- Azure > Provider > Insights > Registered
- Azure > Provider > Key Vault > CMDB
- Azure > Provider > Key Vault > Registered
- Azure > Provider > Network > CMDB
- Azure > Provider > Network > Registered
- Azure > Provider > Operational Insights > CMDB
- Azure > Provider > Operational Insights > Registered
- Azure > Provider > Recovery Services > CMDB
- Azure > Provider > Recovery Services > Registered
- Azure > Provider > Relay > CMDB
- Azure > Provider > Relay > Registered
- Azure > Provider > Resources > CMDB
- Azure > Provider > Resources > Registered
- Azure > Provider > SQL > CMDB
- Azure > Provider > SQL > Registered
- Azure > Provider > SQL Virtual Machine > CMDB
- Azure > Provider > SQL Virtual Machine > Registered
- Azure > Provider > Search > CMDB
- Azure > Provider > Search > Registered
- Azure > Provider > Security > CMDB
- Azure > Provider > Security > Registered
- Azure > Provider > Service Bus > CMDB
- Azure > Provider > Service Bus > Registered
- Azure > Provider > SignalR Service > CMDB
- Azure > Provider > SignalR Service > Registered
- Azure > Provider > Storage > CMDB
- Azure > Provider > Storage > Registered
- Azure > Provider > Synapse > CMDB
- Azure > Provider > Synapse > Registered
- Azure > Provider > Web > CMDB
- Azure > Provider > Web > Registered
Azure > Provider > API Management > CMDB
Configure whether to record and synchronize details for the Azure Provider api management into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/apiManagementCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > API Management > Registered
Check whether Azure > Provider > API Management
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > API Management > Registered
control compares
the registration state against the registration policies for the provider API Management,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/apiManagementRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Automation > CMDB
Configure whether to record and synchronize details for the Azure Provider automation into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in Azure > Provider > Automation > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-provider#/policy/types/automationCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Automation > Registered
Check whether Azure > Provider > Automation
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Automation > Registered
control compares
the registration state against the registration policies for the provider Automation,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/automationRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Billing > CMDB
Configure whether to record and synchronize details for the Azure Provider billing into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/billingCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Billing > Registered
Check whether Azure > Provider > Billing
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Billing > Registered
control compares
the registration state against the registration policies for the provider Billing,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/billingRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Compute > CMDB
Configure whether to record and synchronize details for the Azure Provider compute into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/computeCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Compute > Registered
Check whether Azure > Provider > Compute
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Compute > Registered
control compares
the registration state against the registration policies for the provider Compute,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/computeRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Container Service > CMDB
Configure whether to record and synchronize details for the Azure Provider container service into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/containerServiceCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Container Service > Registered
Check whether Azure > Provider > Container Service
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Container Service > Registered
control compares
the registration state against the registration policies for the provider Container Service,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/containerServiceRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Cost Management > CMDB
Configure whether to record and synchronize details for the Azure Provider cost management into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/costManagementCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Cost Management > Registered
Check whether Azure > Provider > Cost Management
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Cost Management > Registered
control compares
the registration state against the registration policies for the provider Cost Management,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/costManagementRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > DB for MySQL > CMDB
Configure whether to record and synchronize details for the Azure Provider db for mysql into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/dbforMySqlCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > DB for MySQL > Registered
Check whether Azure > Provider > DB for MySQL
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > DB for MySQL > Registered
control compares
the registration state against the registration policies for the provider DB for MySQL,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/dbforMySqlRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > DB for PostgreSQL > CMDB
Configure whether to record and synchronize details for the Azure Provider db for postgresql into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/dbForPostgreSqlCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > DB for PostgreSQL > Registered
Check whether Azure > Provider > DB for PostgreSQL
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > DB for PostgreSQL > Registered
control compares
the registration state against the registration policies for the provider DB for PostgreSQL,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/dbForPostgreSqlRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Data Factory > CMDB
Configure whether to record and synchronize details for the Azure Provider data factory into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/dataFactoryCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Data Factory > Registered
Check whether Azure > Provider > Data Factory
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Data Factory > Registered
control compares
the registration state against the registration policies for the provider Data Factory,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/dataFactoryRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Data Lake Analytics > CMDB
Configure whether to record and synchronize details for the Azure Provider data lake analytics into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in Azure > Provider > Data Lake Analytics > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-provider#/policy/types/dataLakeAnalyticsCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Data Lake Analytics > Registered
Check whether Azure > Provider > Data Lake Analytics
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Data Lake Analytics > Registered
control compares
the registration state against the registration policies for the provider Data Lake Analytics,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/dataLakeAnalyticsRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Databricks > CMDB
Configure whether to record and synchronize details for the Azure Provider databricks into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/databricksCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Databricks > Registered
Check whether Azure > Provider > Databricks
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Databricks > Registered
control compares
the registration state against the registration policies for the provider Databricks,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/databricksRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Document DB > CMDB
Configure whether to record and synchronize details for the Azure Provider document db into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/documentDbCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Document DB > Registered
Check whether Azure > Provider > Document DB
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Document DB > Registered
control compares
the registration state against the registration policies for the provider Document DB,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/documentDbRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Domain Registration > CMDB
Configure whether to record and synchronize details for the Azure Provider domain registration into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/domainRegistrationCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Domain Registration > Registered
Check whether Azure > Provider > Domain Registration
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Domain Registration > Registered
control compares
the registration state against the registration policies for the provider Domain Registration,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/domainRegistrationRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > HDInsight > CMDB
Configure whether to record and synchronize details for the Azure Provider hdinsight into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in Azure > Provider > HDInsight > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-provider#/policy/types/hdInsightCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > HDInsight > Registered
Check whether Azure > Provider > HDInsight
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > HDInsight > Registered
control compares
the registration state against the registration policies for the provider HDInsight,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/hdInsightRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Insights > CMDB
Configure whether to record and synchronize details for the Azure Provider insights into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/insightsCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Insights > Registered
Check whether Azure > Provider > Insights
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Insights > Registered
control compares
the registration state against the registration policies for the provider Insights,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/insightsRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Key Vault > CMDB
Configure whether to record and synchronize details for the Azure Provider key vault into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/keyVaultCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Key Vault > Registered
Check whether Azure > Provider > Key Vault
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Key Vault > Registered
control compares
the registration state against the registration policies for the provider Key Vault,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/keyVaultRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Network > CMDB
Configure whether to record and synchronize details for the Azure Provider network into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/networkCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Network > Registered
Check whether Azure > Provider > Network
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Network > Registered
control compares
the registration state against the registration policies for the provider Network,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/networkRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Operational Insights > CMDB
Configure whether to record and synchronize details for the Azure Provider operational insights into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/operationalInsightsCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Operational Insights > Registered
Check whether Azure > Provider > Operational Insights
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Operational Insights > Registered
control compares
the registration state against the registration policies for the provider Operational Insights,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/operationalInsightsRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Recovery Services > CMDB
Configure whether to record and synchronize details for the Azure Provider recovery services into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/recoveryServicesCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Recovery Services > Registered
Check whether Azure > Provider > Recovery Services
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Recovery Services > Registered
control compares
the registration state against the registration policies for the provider Recovery Services,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/recoveryServicesRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Relay > CMDB
Configure whether to record and synchronize details for the Azure Provider relay into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/relayCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Relay > Registered
Check whether Azure > Provider > Relay
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Relay > Registered
control compares
the registration state against the registration policies for the provider Relay,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/relayRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Resources > CMDB
Configure whether to record and synchronize details for the Azure Provider resources into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/providerResourcesCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Resources > Registered
Check whether Azure > Provider > Resources
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Resources > Registered
control compares
the registration state against the registration policies for the provider Resources,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/resourcesRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > SQL > CMDB
Configure whether to record and synchronize details for the Azure Provider sql into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/sqlCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > SQL > Registered
Check whether Azure > Provider > SQL
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > SQL > Registered
control compares
the registration state against the registration policies for the provider SQL,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/sqlRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > SQL Virtual Machine > CMDB
Configure whether to record and synchronize details for the Azure Provider sql virtual machine into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/sqlVirtualMachineCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > SQL Virtual Machine > Registered
Check whether Azure > Provider > SQL Virtual Machine
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > SQL Virtual Machine > Registered
control compares
the registration state against the registration policies for the provider SQL Virtual Machine,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/sqlVirtualMachineRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Search > CMDB
Configure whether to record and synchronize details for the Azure Provider search into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/searchCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Search > Registered
Check whether Azure > Provider > Search
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Search > Registered
control compares
the registration state against the registration policies for the provider Search,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/searchRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Security > CMDB
Configure whether to record and synchronize details for the Azure Provider security into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/securityCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Security > Registered
Check whether Azure > Provider > Security
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Security > Registered
control compares
the registration state against the registration policies for the provider Security,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/securityRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Service Bus > CMDB
Configure whether to record and synchronize details for the Azure Provider service bus into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/serviceBusCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Service Bus > Registered
Check whether Azure > Provider > Service Bus
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Service Bus > Registered
control compares
the registration state against the registration policies for the provider Service Bus,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/serviceBusRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > SignalR Service > CMDB
Configure whether to record and synchronize details for the Azure Provider into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/signalRServiceCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > SignalR Service > Registered
Check whether Azure > Provider > SignalR Service
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > SignalR Service > Registered
control compares
the registration state against the registration policies for the provider SignalR Service,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/signalRServiceRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Storage > CMDB
Configure whether to record and synchronize details for the Azure Provider storage into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/storageCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Storage > Registered
Check whether Azure > Provider > Storage
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Storage > Registered
control compares
the registration state against the registration policies for the provider Storage,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/storageRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Synapse > CMDB
Configure whether to record and synchronize details for the Azure Provider synapse into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/synapseCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Synapse > Registered
Check whether Azure > Provider > Synapse
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Synapse > Registered
control compares
the registration state against the registration policies for the provider Synapse,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/synapseRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}
Azure > Provider > Web > CMDB
Configure whether to record and synchronize details for the Azure Provider web into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If 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.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
tmod:@turbot/azure-provider#/policy/types/webCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
Azure > Provider > Web > Registered
Check whether Azure > Provider > Web
is registered.
Provider registration refers specifically to the registration state of a provider.
This control determines whether the provider registration state is set as per desired level.
The Azure > Provider > Web > Registered
control compares
the registration state against the registration policies for the provider Web,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/azure-provider#/policy/types/webRegistered
[ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered"]
{ "type": "string", "enum": [ "Skip", "Check: Not Registered", "Check: Registered", "Enforce: Not Registered", "Enforce: Registered" ], "example": [ "Skip" ], "default": "Skip"}