Azure DevOps Integration (via Microsoft Power Automate)
- Overview of the integration
- Azure DevOps - definitions
- Microsoft Power Automate flows
- Prerequisites
- Best Practice
- Caution
- Integration process
- Step-by-Step Integration Process
- Add fields specific to Azure DevOps and GitHub to the SD_REQUEST table
- Create the Bug work item type
- Import the workflow to Microsoft Power Automate
- Create MS Power Automate flow 1
- Create MS Power Automate flow 2
- Create MS Power Automate flow 3
- Service Manager: Create a resource called Bug Work Item used in a REST step of a process
- Links to other integrations
- List of files to download
IntegrationIntroduction
You can integrate third-party systems with Service Manager in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.
This document describes an integration process that has already been implemented in a customer context.
To find out more about this integration (e.g. scripts to be used), please do not hesitate to contact your EasyVista contact, or your service provider and integrator.
Overview of the integration
Azure DevOps is a Microsoft solution. It is a management tool for DevOps projects that ensures monitoring for tasks, deadlines, problems and calendars relating to applications.
This integration enables you to create a Bug work item in Azure DevOps when a ticket is created in Service Manager, via Microsoft Power Automate.
- The number of the work item is saved in the Service Manager ticket.
- A notification can be added to the comments and available_field_6 field of the Service Manager ticket to indicate changes to the status, scheduled end date and/or group/user assigned in the Azure DevOps work item.
- The work item can be associated with a parent item in Azure DevOps.
Preview of the tools used in this integration
- Microsoft Power Automate (formerly known as Microsoft Flow) enables you to automate recurrent tasks by building workflows using Web applications. These applications use MS Power Automate connectors (based on Microsoft Azure Logic Apps) or the MS Graph gateway for interfacing with any endpoint via HTTP/HTTPS.
| Integration Data Feed (direction) | Authentication Type | Integration Connector Options | ||
|---|---|---|---|---|
|
|
|
|
Connector: When a HTTP request is received| Available versions | ||
|---|---|---|
| SaaS-based | On-premises | |
| Service Manager |  |
|
| Third-Party Product | |
N/A |
Azure DevOps - definitions
Definitions_AzureDevOps
- Azure DevOps is a Microsoft solution. It is a management tool for DevOps projects that ensures monitoring for tasks, deadlines, problems and calendars relating to applications.
- Work items are used to monitor functionalities and specifications, code errors, bugs, etc.
- Each work item is based on a work item type and has a unique ID.
- The work item types available are based on the processes used when creating projects, e.g. agile, scrum, etc. They can be configured differently by each team.
- The Bug work item type is used for tracking bugs.
- The Task work item type is used for monitoring activity and tasks.
- Work items can be assigned to other work items according to a hierarchy based on parent-child relationships.
Microsoft Power Automate flows
The integration between Service Manager and Azure DevOps will trigger three separate flows in Microsoft Power Automate when a ticket is created in Service Manager.
| Flow 1: Create a work item in Azure DevOps and store the Service Manager ticket references | Flow 2: Create a work item associated with a specific parent item | Flow 3: Notify work item changes in the Service Manager ticket | ||
|---|---|---|---|---|
 |
 |
 |
Prerequisites
- You must have an Azure subscription. If this is not the case, you can create a free account, or you can buy an Azure Pay-As-You-Go subscription.
- You must have an Azure DevOps account.
- You must create a Bug work item in Azure DevOps for the process template used by your DevOps project.
See the procedure. - You must create two custom fields for the Bug work item to store the Service Manager ticket references. See the procedure.
Best Practice
BestPractice
- The procedure describes all of the steps for creating Microsoft Power Automate flows. To facilitate integration, the ZIP folders shipped with this integration contain pre-configured flows. Once you have downloaded them, you should specify the parameters specific to your environment, i.e. Azure account credentials, EasyVista server address, credentials of your Service Manager platform, etc.
- Use the search field to find the connectors and actions to be created in the MS Power Automate workflow easily.
example Find the actions for the Azure DevOps connector
Caution
Caution_TitleActionInPowerAutomateFlow
- When you create workflow actions in Microsoft Power Automate, you must rename them as indicated in the procedure. This is because certain items of information in the name refer to the title of the action. If you do not respect the naming convention, the workflow will not be triggered correctly.
example The split(body('Analyze_Ticket_Info')'')?['AVAILABLE_FIELD_6'],',') instruction refers to the action called Analyze Ticket Info
Note: Spaces in the title will automatically be replaced by the underscore _.
Integration process
Prerequisite Ask EasyVista to create two fields in the SD_REQUEST table which will be specific to Azure DevOps and GitHub. Add them to the ticket form. See the detailed procedure.
1. Create the Bug work item in Azure DevOps for the process template used by your DevOps project. See the detailed procedure.
2. Create the two custom fields for the Bug work item to store the Service Manager ticket references. See the detailed procedure.
3. Create the MS Power Automate flows.
See the step-by-step integration process.
- Create MS Power Automate flow 1: Create a work item in Azure DevOps
- Create MS Power Automate flow 2: Create an Azure DevOps work item associated with a specific parent item
- Create MS Power Automate flow 3: Notify work item changes in the Service Manager ticket
- Note: This requires a connection to Azure DevOps.
Import the preconfigured flows below containing all of the steps to MS Power Automate. See the procedure for importing flows.
4. In Service Manager, create a Bug Work Item resource used in a REST step of a process. See the detailed procedure.
Step-by-Step Integration Process
AddDevOpsFieldsInTicketForm_Procedure
Add fields specific to Azure DevOps and GitHub to the SD_REQUEST table
Step 1: Ask EasyVista to add fields to the database
1. Ask EasyVista to add the following two fields.
- Field called E_ADO_NUMBER, nvarchar data type, size 20. This will store the ID of the Azure DevOps work item associated with the Service Manager ticket.
- Field called E_PR_NUMBER, nvarchar data type, size 20. This will store the number of the GitHub pull request associated with the Service Manager ticket.
Step 2: Add fields to the Ticket forms, i.e. Incident and Request forms
See the detailed procedure
1. Open each Ticket form, i.e. Incident and Request forms.
2. Click 
in the top banner and select Edit Form.
The main form presentation will appear.
3. Select and place the two fields in the form.
4. Click Save and click Save and Close.
The form will be refreshed.
Create the Bug work item type
Caution: Make sure you create the work item in the process template or in the process used by your DevOps project.
CreateBugWorkItemType_Procedure
Step 1: Log in to Azure DevOps
1. Log in to Azure DevOps using your Azure account credentials.
2. Click the name of your organization.
3. Click Organization settings.
Step 2: Create the Bug work item type
1. Select Boards > Process in the menu pane.
The list of DevOps processes will appear.
2. Select the DevOps project in which you want to monitor tickets created in Service Manager.
The list of work item types defined for the project processes will appear.
3. Click + New work item type.
4. Specify the information on the new work item type and name it Bug.
5. Click Create.
The properties of the new work item type will appear.
EndCreateBugWorkItemType_Procedure
Step 3: Create two custom fields to store the Service Manager ticket references
CreateEZVFieldsForBugWorkItem_Procedure
1. Select the Bug work item type.
2. Click New field.
3. Specify the information on storing the ticket ID in the new field and name it EZV_ID.
4. Click Add field.
The new field will be associated with the Bug work item type in the Custom section.
5. Repeat the procedure to create the second field for storing the ticket URI and name it EZV_URI.
EndCreateEZVFieldsForBugWorkItem_Procedure
Import the workflow to Microsoft Power Automate
Note: This requires a connection to Azure DevOps.
Step 1: Download the flow
1. Download the relevant file below to your workstation.
ImportFlowInMicrosoftPowerAutomate_Procedure
Step 2: Import the flow to Microsoft Power Automate
1. Log in to the Microsoft Power Automate website using your account credentials.
2. Click My flows in the left pane.
A list of your MS Power Automate flows will appear.
3. Click Import in the menu bar and select the file you downloaded.
- Once imported, the package contents will appear.
- The
icon indicates that the connection for the resource was not found.
Step 3: Create the connections required for the flow
1. Click the Select during import link in the Import Setup column for the relevant resource.
The window for configuring the import will appear.
2. Create a new connection for the resource or select an existing connection.
There is an existing connection for the resource
- Select the connection.
- Click Save.
There is no existing connection for the resource
- Click + Create.
- An MS Power Automate instance will appear in a new Web browser tab.
- The list of existing connections will appear.
- Click + New connection.
- Find the connection you want using the search field and select it from the list.
example Find the GitHub connection
A window displaying the list of permissions to be granted to Microsoft Power Platform will appear.
- Click Create to create the new connection.
- Click Accept to accept the conditions and authorize Microsoft Power Platform access.
- You will return to the tab displaying the list of MS Power Automate flows.
- The new connection for the resource will appear in the list.
example New GitHub connection
- Close your Web browser tab.
You will return to the tab displaying the details of the imported package.
- Click Refresh List.
The new connection for the resource will appear in the window for configuring the import.
- Select the connection and click Save.
The
icon indicates that the connection for the resource has been correctly established.
3. Repeat the procedure for each connection required for the flow.
Step 4: Import package resources
1. Click Import.
The 
icon next to each package resource indicates that the flow has been correctly imported.
Step 5: Configure package resources
Note: You should perform this step if a message at the top of the page informs you that package resources must be configured.
1. Click Save as new flow in the message displayed at the top of the page.
- An MS Power Automate instance will appear in a new Web browser tab.
- The workflow of the imported package will appear.
2. Click the action indicating an invalid connection.
The list of all existing connections for the selected type of resource will appear.
2. Click the connection defined for the type of resource.
The properties of the action will appear. The properties displayed depend on the type of resource.
example Unspecified properties for an action using the Azure DevOps resource
3. Specify the connection information for the action.
example Properties for an action using the Azure DevOps resource
- Organization Name: Select the name of your organization.
- Project Name: Select the name of your DevOps project.
4. Repeat the procedure for each action indicating an invalid connection.
5. Click Save.
- The error message for the action will disappear.
example Action for the Azure DevOps resource
- You have configured all of the connections required for the flow.
- The workflow will be created.
Step 6: Configure the workflow
1. Move your cursor over the name of the flow and click 
.
The workflow will appear.
2. See the procedure for configuring the imported flow.
Create MS Power Automate flow 1
Description of the Create a work item in Azure DevOps workflow
 |
Step 1: Create the step that will trigger the flow
==> The flow is triggered when a ticket is created in Service Manager.
1. Create a When a HTTP request is received step that will trigger the workflow.
 |
|
Step 2: Create a Bug work item in Azure DevOps to store the Service Manager ticket references
1. Create a Create a work item action (Azure DevOps connector).
 |
|
Step 3: Store the Bug work item ID in the comment field of the Service Manager ticket
1. Create a HTTP action to update the Service Manager ticket.
 |
|
in the title bar.
Step 4: Save the configuration of the workflow
1. Click Save at the bottom of the flow.
Create MS Power Automate flow 2
Description of the Create a work item associated with a specific parent item workflow
|
Step 1: Create the step that will trigger the flow
==> The flow is triggered when a ticket is created in Service Manager.
1. Create a When a HTTP request is received step that will trigger the workflow.
|
|
Step 2: Create a Bug work item in Azure DevOps to store the Service Manager ticket references
1. Create a Create a work item action (Azure DevOps connector).
|
|
Step 3: Associate the Bug work item with a parent work item
1. Create an Update a work item action (Azure DevOps connector).
 |
|
Step 4: Save the configuration of the workflow
1. Click Save at the bottom of the flow.
Create MS Power Automate flow 3
Description of the Notify work item changes in the Service Manager ticket workflow
 |
|
Step 1: Create the step that will trigger the flow
==> The flow is triggered when the Bug work item associated with the Service Manager ticket is changed in Azure DevOps.
1. Create a When a Work Item is Updated step (Azure DevOps connector) that will trigger the workflow.
 |
|
Step 2: Retrieve the ID of the group/user assigned to the Service Manager ticket (Group_ID field)
1. Create a HTTP step to find the group stored in the Service Manager ticket.
 |
|
2. Create a JSON Analysis action to retrieve information on the group.
 |
|
Step 3: Retrieve the status, scheduled end date and group/user assigned from the Service Manager ticket (available_field_6 field)
1. Create a HTTP step to find the Service Manager ticket.
|
|
2. Create a JSON Analysis action to retrieve information on the Service Manager ticket.
|
|
3. Define the following variables by creating Initialize variable actions in the order listed below to retrieve the status, scheduled end date and group/user assigned from the available_field_6 field.
 |
Variable 1: To store the ID of the Azure DevOps work item
|
Variable 2: To store the number of the Service Manager ticket
|
Step 4: Notify any changes made to the Azure DevOps work item in the comment field of the Service Manager ticket
Step 4.a: Store changes to the status in the Service Manager ticket
1. Create a Condition action to check changes to the status.
 |
|
2. Define the actions to be performed when the status is changed in the Azure DevOps work item (conditions for the Condition State action).
- Go to the If Yes branch.
- Select Add an action to add the following actions.
3. Create an Apply to each action.
 |
|
4. Create a HTTP action to store the changed status in the comment field of the Service Manager ticket.
Note: action_type_id = 95: ID of the Internal Note value
 |
|
Step 4.b: Store changes to the scheduled end date in the Service Manager ticket
1. Create a Condition action to check changes to the scheduled end date.
 |
|
2. Define the actions to be performed when the scheduled end date is changed in the Azure DevOps work item (conditions for the Condition Date actions).
- Go to the If Yes branch.
- Select Add an action to add the following actions.
3. Create an Apply to each action.
|
|
4. Create a HTTP action to store the changed date in the comment field of the Service Manager ticket.
Note: action_type_id = 95: ID of the Internal Note value
 |
|
Step 4.c: Store changes to the group/user assigned in the Service Manager ticket
1. Create a Condition action to check changes to the group/user assigned.
 |
|
2. Define the actions to be performed when the group/user assigned is changed in the Azure DevOps work item (conditions for the Condition Assigned To actions).
- Go to the If Yes branch.
- Select Add an action to add the following actions.
3. Create an Apply to each action.
|
|
4. Create a HTTP action to store the changed group/user assigned in the comment field of the Service Manager ticket.
Note: action_type_id = 95: ID of the Internal Note value
 |
|
Step 5: Notify any changes made to the Azure DevOps work item in the available_field_6 field of the Service Manager ticket
1. Create a Condition action to check changes to the Azure DevOps work item.
 |
|
2. Define the actions to be performed when changes are made to the Azure DevOps work item (conditions for the Condition Update Ticket actions).
- Go to the If Yes branch.
- Select Add an action to add the following action.
3. Create a HTTP action to store changes in the available_field_6 field of the Service Manager ticket.
 |
|
Step 6: Save the configuration of the workflow
1. Click Save at the bottom of the flow.
Service Manager: Create a resource called Bug Work Item used in a REST step of a process
Notes:
- The Bug Work Item resource will enable to create a Bug work item in Azure DevOps when a ticket is created in Service Manager.
- It is associated with a Microsoft Power Automate service.
- It is used in a Service Manager process using a REST action type.
CreateInServiceManagerRestResource_Procedure
Step 1: Manage rights for using the Service Manager REST API
1. Select Administration > Access Management > User Profiles in the menu.
2. Select a user profile authorized to use the Service Manager REST API.
3. Tick the REST API box.
Your changes will automatically be saved.
4. Repeat the procedure for all authorized profiles.
Step 2: Create a resource called Bug Work Item associated with a Microsoft Power Automate service
See the detailed procedure.
Step 2.a: Create a service called Microsoft Power Automate
1. Select Administration > REST > Services in the menu.
2. Create a new service.
3. Specify the information below.
- Service Name: Enter the label Microsoft Power Automate.
- Authentication Method: None.
- Service URL: URL for accessing the new Microsoft Power Automate service.
- Copy and paste the URL you stored in your text editor when creating the MS Power Automate flow (step that will trigger the flow).
- You should keep only the text displayed in yellow below.
https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8
- Replace prod-55.westeurope with {subdomain}.
Step 2.b: Create a connection to the Microsoft Power Automate service.
1. Create a new connection.
2. Specify the information below.
- Connection Name: Enter the label Azure DevOps.
- Authentication Method: None.
- Service Name: Select the Microsoft Power Automate service you created at step 2.a.
The URL of the service will automatically appear.
- subdomain: Copy and paste the prod-55.westeurope value of the URL you stored in your text editor.
Step 2.c: Create a resource associated with the Microsoft Power Automate service
1. Create a new resource.
2. Specify the information below.
- Label: Enter the label Bug Work Item.
- Resource URI: ID of the new resource.
- Copy and paste the URL you stored in your text editor when creating the MS Power Automate flow (step that will trigger the flow).
- You should keep only the text displayed in yellow below.
https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8
- Contents: Body of the query containing the data to be updated. Copy and paste the text below without inserting any spaces or line breaks.
{"Description": "{Description}","id": "{id}","Host": "{sys.EVSM_HOST}","URL": "{sys.EVSM_REST_SERVICE_URL}","Account": "{sys.EVSM_ACCOUNT}","Title": "{Title}"}
Step 3: Use the Bug Work Item resource in a REST step of a process
1. Open the workflow or the business rule-related process you want.
- Workflow: References > Other References > Workflows (Operation/Transition)
- Business rule: Administration > Business Rules > Related Processes
2. Click and drag the new Bug Work Item resource from the REST Actions category of the palette of action types to the graphic editor of the process.
A new step will be added to the process.
3. Double-click to define the properties of the new step.
4. Click Confirm Changes.
Links to other integrations
- Microsoft Power Automate (formerly known as Microsoft Flow)
- GitHub integration (via Microsoft Power Automate)
- GitHub integration (via Microsoft Power Automate) - Approve a review
- GitHub integration (via Microsoft Power Automate) - Merge a pull request
- GitHub integration (via Microsoft Power Automate) - Close a pull request
- GitHub integration (via Microsoft Power Automate) - Close a Service Manager ticket associated with a pull request
List of files to download
Note: To find out more, see the step-by-step integration process.