Microsoft Azure Monitor Actions

Actions for Microsoft Azure Monitor #

• Send Data to Microsoft Azure Monitor. Sends a custom set of Lucidum data to Microsoft Azure Monitor.

Use Cases #

Below are the possible use cases for these actions:

• If you want to run Lucidum “headless”, you can send relevant data to Microsoft Azure Monitor on a regular schedule.

• You can send normalized, enriched Lucidum data to Microsoft Azure Monitor to be indexed, searched, and analyzed.

Prerequisites #

To execute Microsoft Azure Monitor actions, you must configure a Microsoft Azure Monitor API connection beforehand.

Workflows #

• Creating a new Configuration and a new Action
• Cloning an Existing Action
• Creating a new Action from the Location Results page
• Editing a Configuration
• Editing an Action
• Viewing Information about an Action

Microsoft Azure Monitor Configuration #

To create a configuration for Microsoft Azure Monitor actions:

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• Tenant. The GUID or domain name of the directory tenant.

• Client ID. Enter the Client ID for the Lucidum application in Azure AD. Client ID is the unique identifier for the Lucidum application in Azure Active Directory. For details, see https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/register-app-for-token?tabs=portal.

• Client Secret. Enter the Client Secret ID for the Lucidum application in Azure AD. You captured this value in step #11 in the section above. For details, see https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/register-app-for-token?tabs=portal.

• Scope. Specify the scope of the API requests. For example, a specific resource, subscription, or log data.

• Max # of Records per Payload. The maximum number of records to send to Microsoft Azure Monitor in each action. The default value is “50”.

Create a New Action #

To create an action for Microsoft Azure Monitor, contact Lucidum customer care.