HaloCRM Guides

Guides > Azure Monitor Integration

Azure Monitor Integration

In this guide we will cover:

- What is the Azure Monitor Integration?

- Connecting to Azure Monitor

- Defaults and Mappings

- Creating the Webhook

What is the Azure Monitor Integration?

The Azure Monitor integration allows webhooks to be sent from Azure Monitor to Halo and subsequently turned into tickets. Furthermore, field mappings can be configured and if the alert is resolved, it will automatically close the ticket in Halo.

Connecting to Azure Monitor

First, you must enable this integration in Configuration > Integrations > Asset Management and Alerting. Hover over the icon and click the plus - it is enabled when the colour is not greyed out.

The first tab is for "Azure Monitor Setup". Here you will see the URL required for the webhook, as well as the option for authentication. If "Secure Webhook" is selected as the "Action Type", additional fields for the tenant and application ID will show to provide that webhook authentication.

Note: The tenant used to authenticate must be a single-tenanted application.

Fig 1. Azure Monitor Setup tab.

Defaults and Mappings

The configuration page contains some basic setup for you to decide what happens to tickets create from an Alert.

Fig 2. Default ticket type/users/status.

You can then choose any field mappings you would like. These will map information from the alert to custom fields in Halo.

Fig 3. Field mappings.

Creating the Webhook

The last thing you will have to do, is use the URL found at the top of the config page as the webhook URL when you configure your Azure Monitor Alert Action.

Fig 4. Adding a webhook.

Note: You must enable the common alert schema otherwise the webhook will not be processed by Halo.

If you would like more information on how to create and configure alerts in Azure Monitor, please see this guide from Microsoft: Overview of Azure Monitor Alerts.

Secure Webhooks

If using secure webhooks, please note that we only support version 2 access tokens. This means you need to ensure the Azure Entra ID app registration has this reflected in the Microsoft Graph App Manifest file.

Within the manifest file of the app registration, ensure 'api.requestedAccessTokenVersion' is set to 2, as below:

Once you've done that, it will take a while to update, as this is heavily cached by Microsoft. You should be able to speed it along by adding a scope and then removing it straight after: