Creating incidents from Azure Monitor alerts via BMC Helix iPaaS, powered by Jitterbit

As an administrator, you can integrate BMC Helix ITSM with Azure Monitor to create a BMC Helix ITSM incident from an Azure alert. You can also update the status of an alert from the corresponding BMC Helix ITSM incident.

BMC Helix Multi-Cloud Broker, along with BMC Helix iPaaS, powered by Jitterbit provides an out-of-the-box integration template that you use to integrate BMC Helix ITSM and Azure Monitor. You configure the integration in BMC Helix Multi-Cloud Broker and deploy the template to your BMC Helix iPaaS environment.

This integration provides the following capabilities:

Use case	Notification feature capabilities
Create a ticket	Create an incident in BMC Helix ITSM when an alert is created in Azure Monitor.
Update ticket status	Update the status of an Azure alert when the status of the corresponding BMC Helix ITSM incident is changed to In Progress, Resolved, or Closed

The following image gives an overview of the capabilities that this integration supports:

Before you begin

Make sure you have the following items:

A valid BMC Helix iPaaS, powered by Jitterbit subscription.
Administrator access to the Azure Monitor service.
Administrator access for BMC Helix Multi-Cloud Broker and BMC Helix ITSM users to run this integration.
Webhooks configured for Azure alerts.
The Create BMC Helix ITSM incident from Microsoft Azure alert Update 2022-03-01 project file downloaded to your system from the BMC Helix Multi-Cloud Broker page on the Electronic Product Distribution site.

Azure Monitor to BMC Helix ITSM data flow

BMC Helix ITSM to Azure Monitor status change flow

Task 1: To configure the integration

To integrate BMC Helix ITSM incidents with Azure alerts, you must first select the integration feature in Quick Configuration Guide, add vendor metadata, and configure a webhook for Azure alert.

Task 1.1: To perform the basic configurations

Log in to BMC Helix Innovation Studio.
On Workspace, click Multi-Cloud Broker.
To launch BMC Helix Multi-Cloud Broker, click Visit Deployed Application.
Tip

You can access BMC Helix Multi-Cloud Broker directly by entering the URL https://hostName:portNumber/helix/index.html#/com.bmc.dsm.mcsm/login and logging in as a tenant administrator.
Click Settings .
Select Start Here > Quick Configuration Guide.
The Quick Configuration Guide page is displayed.
In the Step 1: Choose configuration tab, perform the following steps:
Important

In Choose Configuration, Helix iPaaS (powered by Jitterbit) is selected by default. Do not change this value.
1. Under Notification, select Azure Alerts to ITSM Incident.
2. Click Next.

In the Step 2: Perform configurations tab, perform the following steps:

Add an operating organization, if you have not already done so.
Add Microsoft as the vendor organization, if you have not already done so.

To add vendor metadata, click Map vendors and perform the following steps:

On the Map Vendors page, click Map Vendor.

Complete the fields as described in the following table:

Field	Action
Description	Enter a description for the vendor metadata configuration.
Ticketing Technology Provider	From the list, select Azure Alerts.
(Optional) Instance Name	You do not need to enter any value in this variable.
Add Mapping	After you select the ticketing technology provider, click Add Mapping. BMC Helix Multi-Cloud Broker displays the default values in the Instance URL field and the Display Field Mapping section.
Instance URL	If you have clicked Add Mapping, this field is auto-populated. You do not need to change the URL.
Display Field Mapping	By default, the basic Azure Monitor fields are mapped in this section. If you want to map additional fields to display in the BMC Helix ITSM UI, add the relevant mappings by clicking .
Enable Local ITSM Communication	By default, this toggle key is enabled. If you want to use BMC Helix Integration Service as the underlying integration platform, disable this toggle key.
Integration Platform	Select Jitterbit.

Click Save.
The following image shows the fields displayed in the Map New Vendor pane for Azure Monitor:

Task 1.2: To configure a webhook for an Azure alert

Log in to Microsoft Azure.
Select Home > Alerts > Rules.

Based on the type of webhook that you want to configure, perform the following steps:

Type of webhook

Steps

Basic webhook

In the Webhook panel, set Secure webhook to No.
In URL, enter the URL to the BMC Helix iPaaS API that you are using.
Set Common Alert Schema to Yes.

The following image shows a sample basic webhook action:

Secure webhook

If you have not already done, register the app .
After you have registered your app, you can find the Object ID in the Overview tab. You will also need Application ID and Tenant ID for configuration in the Azure Alerts connector.
In the Overview tab, copy Object ID of your registered app.
In the Webhook panel, set Secure webhook to Yes.
Paste the Object ID that you copied from the registered app.
In URL, enter the URL to the BMC Helix iPaaS API that you are using.
Set Common Alert Schema to Yes.

The following image shows a sample secure webhook action:

To know more, see the Azure Monitor Open link documentation.

Task 1.3: To assign a role to an application

You must assign a role with the required permissions to your application. To do this, perform the following steps:

Log in to Microsoft Azure.
On the Home page, search for and select Subscriptions.
From the list of your subscriptions, select the required subscription.
Select Access control (IAM).
Select Add > Add role assignment.
On the Add Role Assignment page, select the role that you want to assign to your application.

For more information about the roles, see Assign a role to the application Open link .

Task 2: To import the integration template project file

Log in to BMC Helix iPaaS and navigate to the Cloud Studio.
Select your organization.
On the projects page, click Import.
Click Browse to navigate to and select the JSON file that you downloaded from the Electronic Product Distribution site.
The Project Name and Organization fields are automatically populated depending on the values defined.
From the Environment list, select the environment to which you want to import this integration template, and click Import.
The project opens after the integration template is imported. The default project name is displayed. You can change the project name.
To open the project file at a later time, select the environment where the integration templates are available, select the project name, and click View/Edit.

Task 3: To update the project variables for the integration template

Click the ellipsis ... next to the project name and select Project Variables.

Update the project variables as described in the following tables:

BMC Helix iPaaS variables

Project variable	Action
BHIP_API_NAME	Enter the name for API that is created in BMC Helix iPaaS to receive BMC Helix Multi-Cloud Broker webhook requests. The default value of this variable is set to BMCHelixAzureAlertsITSMIncident. If required, you can change the name.
BHIP_API_User_Roles	Specify the organization roles that should have access to the new API. You can add multiple comma separated values. Important: If you do not specify any value, all the organization roles get access to the new API.
BHIP_MCB_API_Profile_User_Name	The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the user name that should be used while creating the BMC Helix Multi-Cloud Broker API profile.
BHIP_MCB_API_Profile_User_Password	The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker. Enter the password that should be used while creating the BMC Helix Multi-Cloud Broker API profile.
BHIP_Vendor_API_Profile_Type	The default value of this variable is OAuth. You must not change the value.
BHIP_Vendor_API_Profile_User_Name	You do not need to enter any values in these variables.
BHIP_Vendor_API_Profile_User_Password
BHIP_Vendor_API_Profile_ApiKey_Name
BHIP_Host	Enter the BMC Helix iPaaS instance URL where you want to run this project. Important: Make sure that you do not enter any leading and trailing spaces.
BHIP_User_Name	Enter the user name for the BMC Helix iPaaS instance.
BHIP_User_Password	Enter the password for the BMC Helix iPaaS instance.
Enable_BMC_Helix_To_Vendor_Integration	By default, this variable is enabled. Important: This variable updates the status of an alert when the corresponding incident status is changed to In Progress, Resolved, or Closed.
Enable_Vendor_To_BMC_Helix_Integration	By default, this variable is enabled. Important: This variable enables the creation of a BMC Helix ITSM incident from an Azure alert. It also updates the status of the alert from the incident.
BHIP_Vendor_API_OAUTH_PROVIDER	The default value of this variable is Azure AD. If you use a different authentication provider, refer to the documentation of that provider to configure the variable.
BHIP_Vendor_OAUTH_CLIENT_ID	Enter the client ID for your Azure Monitor instance only if you have provided the following values in the variables: BHIP_Vendor_API_Profile_Type—OAuth BHIP_Vendor_API_OAUTH_PROVIDER—Azure AD
BHIP_Vendor_OAUTH_CLIENT_SECRET	Enter the client secret for your Azure Monitor instance only if you have provided the following values in the variables: BHIP_Vendor_API_Profile_Type—OAuth BHIP_Vendor_API_OAUTH_PROVIDER—Azure AD

Important

To configure the OAuth variables, see Azure AD OAuth 2.0 API Security Profile Open link in the Jitterbit documentation.

BMC Helix Multi-Cloud Broker variables

Project variable	Action
MCB_Host	Enter the BMC Helix Multi-Cloud Broker host URL in the following format: `[http/https]://[hostname]:[port]` Important: Make sure that you do not enter any leading and trailing spaces.
MCB_User_Name	Enter the user name that enables users to interact with BMC Helix Multi-Cloud Broker.
MCB_User_Password	Enter the password for the provided username.
MCB_Vendor_Name	This variable is autopopulated. You must not change the value.

The following variables are inputs from BMC Helix ITSM. Either enter values for these variables or map the appropriate Azure Monitor fields if the data is available:

Project variable	Action
ITSM_Company_Name	Enter the company name for which the integration template needs to be run; for example, Calbro Services
ITSM_Customer_First_name	Enter the first name of the BMC Helix ITSM customer.
ITSM_Customer_Last_Name	Enter the last name of the BMC Helix ITSM customer.
ITSM_Incident_Type	Enter any of the following incident types for which you want to create a corresponding Azure Alert: User Service Restoration User Service Request Infrastructure Restoration Infrastructure Event Security Incident The default value of this variable is set to User Service Restoration.
Reported_Source	Enter one of the following sources from which the BMC Helix ITSM incident is created: Direct Input Email External Escalation Fax System Management Phone Voice Mail Walk In Web BMC Impact Manager Event The default value of this variable is Other.

Task 4: To deploy and enable the project

Deployment is a one-time activity that initializes the integration configurations. The UI displays a message for the deployment status.

The following image shows the steps to deploy the project and enable it by deploying the workflow:

(Optional) Task 5: To set the time for API debug mode

By default, the debug mode is set to 2 hours after you run the integration. Debug logs are updated for the time set for the debug mode. To increase the debug mode for a longer period of time, perform the following steps:

In BMC Helix iPaaS, powered by Jitterbit, select API Manager > My APIs.
Open any of the following APIs:
- BMC_Helix_Azure_Alerts_ITSM_Incident_MCB_To_Vendor—This API is used to synchronize the status updates from a BMC Helix ITSM incident to an Azure alert.
- BMC_Helix_Azure_Alerts_ITSM_Incident_Vendor_To_MCB—This API is used to create a BMC Helix ITSM incident from an Azure alert.
Select Enable Debug Mode Until: and set it for the required date and time.
Save and publish the API.