Delete the Azure Log Analytics Log Analytics Workspace.


Azure > Log Analytics > Log Analytics Workspace

Azure > Log Analytics > Log Analytics Workspace > Delete

Process events for Azure Log Analytics service Log Analytics Workspace resources.

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


Azure > Resource Group

Azure > Log Analytics > Log Analytics Workspace > Router

Update the tags for Azure Log Analytics log analytics workspace.


Azure > Log Analytics > Log Analytics Workspace > Set Tags

Configure the Azure Log Analytics Workspace data retention. The retention days varies from 30 to 730 days where 30 is the default value.


Azure > Log Analytics > Log Analytics Workspace > Update Data Retention

Take an action when an Azure Log Analytics log analytics workspace is not active based on the&#92;n`Azure &gt; Log Analytics &gt; Log Analytics Workspace &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; Log Analytics &gt; Log Analytics Workspace &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 > Log Analytics > Log Analytics Workspace > Active > Age

Azure > Log Analytics > Log Analytics Workspace > Active > Last Modified

Azure > Log Analytics > Log Analytics Workspace > Active

Take an action when an Azure Log Analytics log analytics workspace is not approved based on `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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 > Log Analytics > Log Analytics Workspace > Approved > Custom

Azure > Log Analytics > Log Analytics Workspace > Approved > Usage

Azure > Log Analytics > Enabled

Azure > Log Analytics > Log Analytics Workspace > Approved > Regions

Azure > Log Analytics > Log Analytics Workspace > Approved

Record and synchronize details for the Azure Log Analytics log analytics workspace 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; Log Analytics &gt; Log Analytics Workspace &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > Log Analytics > Log Analytics Workspace > Regions

Azure > Log Analytics > Log Analytics Workspace > CMDB

Configure the Azure Log Analytics Workspace data retention. The retention days varies from 30 to 730 days where 30 is the default value.&#92;n

Azure > Log Analytics > Log Analytics Workspace > Data Retention > Days

Azure > Log Analytics > Log Analytics Workspace > Data Retention

Discover all Azure Log Analytics log analytics workspace 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; Log Analytics &gt; Log Analytics Workspace &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > Log Analytics > Log Analytics Workspace > Discovery

This control checks the resource&#39;s pricing tier based on `Azure &gt; Log Analytics &gt; Log Analytics Workspace &gt; Pricing Tier` policy and raises an alarm if the pricing tier is not set according to this policy.&#92;n

Azure > Log Analytics > Log Analytics Workspace > Pricing Tier

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

Azure > Log Analytics > Log Analytics Workspace > Tags

logAnalytics

logAnalyticsAka

DefaultWorkspace-0a55cd76-e849-43b4-a2c2-23318da500e4-CIN

pergb2018

invalid - workspacename property is missing

invalid - turbot metadata property is missing

logAnalyticsWorkspace

logAnalyticsWorkspaceServiceNow

workspaceAka

workspaceId

workspaceName

azure-loganalytics

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

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

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

Azure > Log Analytics

Azure > Log Analytics > Approved Regions [Default]

Azure > Log Analytics > Permissions > Levels

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

Azure > Log Analytics > Permissions

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

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

Azure > Log Analytics > Regions

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

Azure > Log Analytics > Tags Template [Default]

Determine the action to take when an Azure Log Analytics log analytics workspace, based on the `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace&#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; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace 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; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace is not approved based on `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an Azure Log Analytics log analytics workspace is not approved, it will be subject to the action specified in the `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspaces 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 Log Analytics log analytics workspace is created in a region that is not in the approved list, it will be subject to the action specified in the `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace is allowed to exist.&#92;n&#92;nThis policy will be evaluated by the Approved control. If an Azure Log Analytics log analytics workspace is not approved, it will be subject to the action specified in the `Azure &gt; Log Analytics &gt; Log Analytics Workspace &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 Log Analytics log analytics workspace 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; Log Analytics &gt; Log Analytics Workspace &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

The Pricing Tier control checks the resource&#39;s pricing tier based on `Azure &gt; Log Analytics &gt; Log Analytics Workspace &gt; Pricing Tier` policy and raises an alarm if the pricing tier is not set according to this policy.&#92;n

A list of Azure regions in which Azure Log Analytics log analytics workspaces are supported for use.&#92;n&#92;nAny log analytics workspaces 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 Log Analytics log analytics workspace tags are not updated based on the `Azure &gt; Log Analytics &gt; Log Analytics Workspace &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure Log Analytics log analytics workspace tags include tags defined in `Azure &gt; Log Analytics &gt; Log Analytics Workspace &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Log Analytics Workspace 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 Log Analytics log analytics workspace.&#92;n&#92;nTags not defined in Log Analytics Workspace 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 Log Analytics service offers comprehensive log management and analytics capability in the Azure cloud. It enables users to collect, store, and analyze log data from various sources, known as workspaces, to monitor, troubleshoot and gain insights from their operational data and applications.&#92;n

Azure

Azure > Log Analytics > Log Analytics Workspace > ServiceNow

The Log Analytics Workspace resource type is a unique environment for Azure Monitor log data that can be used to collect, store, and analyze log data from Azure resources.&#92;n

Mod: azure-loganalytics

Recommended Version

Resource Types

Controls

IAM Roles

Policies