To establish integration with Azure Monitor, configure the following connectors, flows, and connector targets. You need to set up tenant level configurations. BMC Helix Multi-Cloud Broker provides out-of-the-box mappings and application level configurations required for the integration. After you complete the integration, you can broker tickets from Azure Monitor to ITSM, update Azure Monitor ticket details from ITSM and so on. Each flow in the list of flows is essentially a feature that you can use. Depending upon your use case, you might have to configure multiple flows. BMC Helix Multi-Cloud Broker logically chains the flows and connector processes to complete the feature.
List of connectors and configuration values for integration with Azure Monitor
You must configure the following connectors when setting up integration with Azure Monitor. These connectors are integration points for the respective applications. For instance, to send the data from BMC Helix Multi-Cloud Broker to Azure Monitor, you must configure a flow from Multi-Cloud connector to Azure Alerts connector.
ITSM connector
Configuration
If you are integrating BMC Helix Multi-Cloud Broker with an on-premises instance of ITSM, enter the following values:
| |
|---|
| Select the site that you created for Remedy. |
| Enter the name of your on-premises AR System server. |
| Enter the port number for your on-premises AR System server. |
- Account
Add a ITSM user account that has permissions to view business service requests and permissions to update incidents, change, or problem requests.
Multi-Cloud connector
- Configuration
While activating BMC Helix Multi-Cloud Broker, BMC configures the Multi-Cloud connector. Do not modify the default Multi-Cloud connector configuration.
Account
BMC sets up the account for the Multi-Cloud connector.
Click 
to re-authenticate after you have changed the password for your tenant administrator user account in BMC Helix Innovation Studio.
For information about changing the user password, see Creating or modifying People data.
Azure Alerts connector
Configuration
If you are integrating BMC Helix Multi-Cloud Broker with Azure Monitor, enter the following values:
| |
|---|
| Enter a name for your connector configuration. |
| Enter a description for your connector configuration. |
| Select the site required to establish a connection between Azure Monitor and BMC Helix Integration Service. You can either use the default cloud site or create your own site. |
| Retain the default value. |
| Select Basic or Secure. Select the same type when creating actions on Azure alerts in Microsoft Azure. |
| Required only when you use secure webhook method. |
| Required only when you use secure webhook method. |
| Required only when you use secure webhook method. |
SMTP Email connector
Configuration
To send email notifications for errors, specify values for the following fields:
| |
|---|
| Enter a name for the connector configuration. |
| Select the appropriate site for your email server. |
| Select the type of connection for your email server. |
- Account
Add an email account to be used for sending error notifications.
List of flows and configuration values for integration with Azure Monitor
You can configure the following flows when setting up integration with Azure Monitor. Each flow is self descriptive, for example to create an incident in ITSM from Azure Monitor, you must configure Create Incident from Azure Alerts flow.
Create Incident from Azure Alerts
Trigger
| |
|---|
| Metric, Log, or Activity Log |
Field Mapping
Do not change the following default field mappings.
| |
|---|
| Monitoring Service, Monitor Condition and so on |
| Monitoring Service, Monitor Condition and so on |
| |
| |
| |
| |
Note
While configuring Create Incident from Azure Alerts flow, you can extract the Azure asset name for which the alert is generated by mapping the LogAffected Configuration Item fields and Metric Condition Dimensions fields in the flow, and by adding transformations for the properties of these fields.
Send Error Notification flow
Trigger
| |
|---|
| Metric, Log, or Activity Log |
Field Mapping
Do not change the following default field mappings.
| |
|---|
| Monitoring Service, Monitor Condition and so on |
| Monitoring Service, Monitor Condition and so on |
| |
| |
| |
| |
Note
While configuring Create Incident from Azure Alerts flow, you can extract the Azure asset name for which the alert is generated by mapping the LogAffected Configuration Item fields and Metric Condition Dimensions fields in the flow, and by adding transformations for the properties of these fields.
Update Azure Alert State flow
TriggerField | Value |
|---|
Condition is | Retain the webhook condition |
Source ID contains | Azure Alerts |
Field MappingThe following values are mapped out-of-the-box.Field | Value |
|---|
Parent Ticket Id | source ID |
Alert Id | Vendor Ticket Data |
Alert State | Status |
List of connector targets for integration with Azure Monitor
When a ticket is brokered from any vendor to ITSM, the ticket data first comes in BMC Helix Multi-Cloud Broker before being sent to ITSM. To send the data from BMC Helix Multi-Cloud Broker to ITSM, you must configure the MCSM ITSM connector target and set it in the Connector Process ITSM.
MCSM ITSM connector target
For the MCSM ITSM connector target, define the connection configuration and profile required by the connector process.