Reference of integration between BMC Helix ITSM and Azure DevOps by using BMC Helix Integration Service
To establish integration with Microsoft Azure DevOps, 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 BMC Helix ITSM to Azure DevOps, sync Azure DevOps ticket details to BMC Helix 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 for integration with Azure DevOps
You must configure the following connectors when setting up integration with Azure DevOps. These connectors are integration points for the respective applications. For instance, to send the data from BMC Helix Multi-Cloud Broker to Azure DevOps, you must configure a flow from Multi-Cloud connector to Azure DevOps connector.
List of flows for integration with Azure DevOps
You can configure the following flows when setting up integration with Azure DevOps. Each flow is self descriptive, for example to create an incident in BMC Helix ITSM from Azure DevOps, you must configure Create Incident from Azure DevOps flow.
List of connector targets for integration with Azure DevOps
When a ticket is brokered from any vendor to BMC Helix ITSM, the ticket data first comes in BMC Helix Multi-Cloud Broker before being sent to BMC Helix ITSM. To send the data from BMC Helix Multi-Cloud Broker to BMC Helix ITSM, you must configure the BMC Helix Multi-Cloud Broker ITSM connector target and set it in the Connector Process ITSM.
Comments
Log in or register to comment.