- Welcome to the EasyVista Wiki
- Integrations
- Microsoft Azure Logic Apps Integration
Microsoft Azure Logic Apps Integration
IntegrationIntroduction
You can integrate third-party systems with 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 contact the Consulting & Professional Services team, the
Support team, or your service provider and integrator.
Overview of the integration
Microsoft Azure Logic Apps enables you to create logic apps that run workflows and provide access to cloud data and services. The tool relies on a large ever growing ecosystem of standard connectors available for interfacing with any endpoint via HTTP/HTTPS.
example Azure Active Directory, Office 365, Skype For Business, Teams, Jira Software, SAP, etc.
This integration enables you to perform actions in both Service Manager and a third-party service using a logic app. You can do this in two ways.
- Perform actions in a third-party service from a Service Manager workflow/business rule.
See Integration Process 1.
example
- In Service Manager, approval of an onboarding request for a new employee via a HR workflow ==> Creation of a user in Microsoft Azure Active Directory with the relevant information, e.g. name, first name, title, department, etc. The user will be added to an AD group and a manager will be assigned.
- In Service Manager, creation of an incident via a standard ticket management workflow or business rule ==> Creation of a new incident in Jira Software.
- In Service Manager, approval of an SAP-related change request via a change management workflow ==> Creation of a new card in Trello, with the change request number as its name.
- Perform actions in Service Manager from a third-party service.
See Integration Process 2.
example In Trello, creation of a new card for a new training course in the HR catalog ==> Creation of a new New Training Analysis change request in Service Manager, with the description of the Trello card.
Integration Data Feed (direction) | Authentication Type | Integration Connector Options | ||
---|---|---|---|---|
|
|
|
Available versions | ||
---|---|---|
SaaS-based | On-premises | |
Service Manager | ![]() |
![]() |
Third-Party Product | ![]() |
N/A |
Notes
- Microsoft Azure Logic Apps is similar to Zapier and IFTTT, also supported by Service Manager thanks to standard connectors (services) that can be used in business processes via REST actions.
PowerAutomatevsLogicApp
What is the difference between Logic Apps and Microsoft Power Automate?
- Microsoft Power Automate is a tool integrated with certain Microsoft 365 programs. It is based on Logic Apps, with same workflow designer and connectors. It enables any user to perform simple integrations without requiring developers or the IT Department.
example Receive SMS notifications for important emails
- Logic apps are used for advanced or strategic integrations that require corporate development and security practices. For this reason, Microsoft Azure Logic Apps includes more functionalities intended for IT teams and developers.
EndPowerAutomatevsLogicApp
Microsoft Azure Logic Apps - Definitions
- A logic app is a series of steps that run actions by accessing data via a connector. The first step requires a trigger.
- A trigger is run when an event meets the specified conditions. It will start the logic app workflow.
example A Service Manager workflow uses a logic app REST action as the trigger.
- An action is a task carried out by the workflow of your logic app.
example When the logic app REST action is triggered in a Service Manager workflow, a Send Email action is performed.
Useful links to documentation
On the wiki Microsoft Logic Apps documentation- What are logic apps?
- List of connectors
- Components and Using Connectors
- Create your first logic app for automating workflows and processes through the Azure portal (sending of an email from an Outlook account when new content is posted in an RSS feed)
- Triggers and actions for logic app workflows
- Configure a workflow using a pre-built template or pattern to get started quickly
- Get started with the request and response components
- Use the HTTP Request trigger
- Secure access to your logic apps
- Common scenarios, examples, tutorials, and walkthroughs for Azure Logic Apps
- Deploy and call custom APIs from logic app workflows (Call your custom API from logic app workflows section)
- Choose between Flow, Logic Apps, Functions, and WebJobs
- Microsoft Azure documentation
- JSON schema (JSON online editor)
- jsoneditoronline.org (JSON online editor)
- Postman (API development and testing environment)
- SoapUI (API and protocol testing environment)
Step-by-Step Integration Process
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.
See the procedure.
- You must have the relevant accounts and access rights to the services interfacing with Logic Apps.
- You must have an account authorizing access to the Service Manager platform with a profile and access rights to create and modify workflows, access the Administration menu and other required menus, such as Service Operation and Service Transition.
Integration process 1: From Service Manager to a third-party service
example
- Main trigger event in Service Manager: Creation of a service request by a VIP (high priority)
- Action carried out in the Outlook third-party service: Sending of an email to a mailing list of members in charge of processing VIP requests
Step 1: Access the Azure portal.
1. Log in to the Azure portal using your Azure account login.
Step 2: In Azure Logic Apps, create a logic app.
1. Move the cursor over the logic app service and click + Create.
2. Create the new logic app.
- Enter the information on the new app.
- Subscription: Name of your Azure subscription.
- Resource group: Azure resource group, used to organize and manage Azure resources (
See the description.). Select an existing group or create a new one.
- Logic App Name: Name of the app.
Note: Letters and numbers as well as the following characters are authorized:- ( ) . There must be no spaces.
example EVSM_New_Request_WKFW_(High-VIP)_SendE-mail - Location: Location of the data center hosting your logic app.
- Click Review + create, then click Create.
- The logic app is created on the Azure portal.
- It is deployed for the selected group.
3. Open the Logic Apps Designer via Go to resource.
4. Select the app trigger.
example When a HTTP request is received trigger
5. Generate the URL of the app via Save in the Designer toolbar.
6. Click to copy the URL displayed in the HTTP POST URL field and paste it in your text editor in order to store it temporarily. It will be required when defining the configuration in Service Manager (steps 2 and 4).
Step 3: In Azure Logic Apps, create the logic app workflow.
1. Click + New step below the trigger step.
The window for selecting the action will appear.
2. Select the connector and the action to be performed.
- Use the search field to filter the list of connectors.
- Select the connector you want.
The list of all actions available for the selected connector will appear. - Select the action you want.
example
- Filter the outlook connectors.
- Select the Office 365 Outlook connector.
- Select the Send email action.
3. Enter the login information required by the connector or click Change connection.
example For the Outlook connector: User name and password for the Outlook account
4. Specify the information for the action based on your requirements.
example Information for sending an email to a mailing list via Outlook
5. Click Save in the Designer toolbar to save the workflow.
Step 4: In Service Manager, create a logic app REST action.
Note: The logic app REST action uses the app you previously created in Azure Logic Apps.
See How to define a new resource and associate it with a REST action.
1. Create a new logic app service by selecting Administration > REST > Services in the menu.
- Service Name: Microsoft Azure Logic Apps.
- Authentication Method: None.
- Service URL: URL for accessing the new Microsoft Azure Logic Apps service.
- Copy and paste the URL you stored in your text editor when creating the logic app (step 2.3). The URL was provided by Azure Logic Apps.
- You should keep only the text displayed in yellow below.
https://prod-29.eastus.logic.azure.com:443/workflows/1f5f40b60154432abcb0b8084892440f/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=5-nNWgR2Hho6s5YN2BYzqBFpzrLmf7UBqhrl6328rIB
- Replace prod-29.eastus with {subdomain}.
2. Create a new connection to the logic app service by selecting Administration > REST > Connections in the menu.
- Enter the name of the connection.
- Authentication Method: None.
- Service Name: Select the Microsoft Azure Logic Apps service you previously created.
The service URL will automatically appear.
- {subdomain} parameter: Copy and paste the prod-29.eastus value of the URL you stored in your text editor.
3. Create a resource associated with the logic app service by selecting Administration > REST > Resources in the menu.
- Label: Name of the resource.
- Service Name: Select the Microsoft Azure Logic Apps service.
- Connection Name: Select the connection you previously created.
- Resource URI: ID of the new resource.
- Copy and paste the URL you stored in your text editor when creating the logic app (step 2.3). The URL was provided by Azure Logic Apps.
- You should keep only the text displayed in yellow below.
https://prod-29.eastus.logic.azure.com:443/workflows/1f5f40b60154432abcb0b8084892440f/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=5-nNWgR2Hho6s5YN2BYzqBFpzrLmf7UBqhrl6328rIB
- Content: Specify the parameters to be used in the third-party service.
example Pass the incident number and description in the email sent to a mailing list
4. Add the new resource associated with the logic app service to a REST step in a process.
- 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
- Click and drag the new resource from the REST Actions category to the graphic editor of the process.
A new step will be added to the process.
- Double-click to define the properties of the new step.
Step 4: Pass Service Manager parameters to the logic app.
See Use the HTTP Request trigger.
Note:
- The parameters must be passed to the logic app trigger in a JSON schema. To do this, you can use jsonschema.net.
- You can then use them in actions via dynamic variables.
Pass Service Manager resource parameters to the logic app trigger.
1. In Service Manager, go to the resource you previously associated with the logic app service (step 3.3).
- Copy the text added to the Content field.
2. Open a text editor, e.g. Notepad++.
- Paste the text.
- Ensure that all invisible characters and line breaks are deleted.
- Copy the clean text.
3. Go to jsonschema.net.
- Paste the clean text in the JSON field.
- Click Submit.
- Switch to Plain mode.
- (optional) Rename the Service Manager parameters so you can identify them easily in the logic app.
example
- comment > title: Description of the incident in Service Manager
==> previous value The comment schema
==> new value EVSM_Request_Description - rfc_number > title: Number of the incident in Service Manager
==> previous value The rfc_number schema
==> new value EVSM_Request_Number
- Click
to copy the JSON schema.
4. Go to the Azure Logic Apps trigger.
- Click the title bar to display the trigger's properties.
- Paste the JSON schema in the Request Body JSON Schema field.
Pass Service Manager resource parameters to the logic app action.
- Click the title bar to display the action's properties.
- Add the parameters retrieved from the Service Manager resource using the app's dynamic variables.
Note: The list of variables available is automatically displayed when you click the Body or Subject field.
Step 5: Verification and test.
1. Create an incident in Service Manager.
2. Check that the action configured in the logic app is correctly performed in the third-party service.
example Creation of a service request in Service Manager ==> An email is automatically sent to a mailing list of members in charge of processing VIP requests, using the Outlook account.
Integration process 2: From a third-party service to Service Manager
example
- Main trigger event in the Outlook third-party service: Reception of an email for a service request
- Action performed in Service Manager: Creation of a service request by sending a HTTP POST request to the Service Manager REST API
Step 1: Access the Azure portal.
1. Log in to the Azure portal using your Azure account login.
Step 2: In Azure Logic Apps, create a logic app.
1. Move the cursor over the logic app service and click + Create.
2. Create the new logic app.
- Enter the information on the new app.
- Subscription: Name of your Azure subscription.
- Resource group: Azure resource group, used to organize and manage Azure resources (
See the description.). Select an existing group or create a new one.
- Logic App Name: Name of the app.
Note: Letters and numbers as well as the following characters are authorized:- ( ) . There must be no spaces.
example EVSM_New_Request_WKFW_(High-VIP)_SendE-mail - Location: Location of the data center hosting your logic app.
- Click Review + create, then click Create.
- The logic app is created on the Azure portal.
- It is deployed for the selected group.
3. Open the Logic Apps Designer via Go to resource.
4. Select the Blank Logic App template.
Note: You can use a predefined template.
5. Select the app trigger.
- Use the search field to filter the list of connectors.
The list of all triggers available for the selected connector will appear. - Select the trigger you want.
example
- Filter the outlook connectors.
- Select the Office 365 Outlook connector.
- Select the When a new email arrives trigger.
6. Enter the login information required by the connector or click Change connection.
example For the Office 365 Outlook connector: User name and password for the Outlook account
7. Specify the information for the trigger based on your requirements.
example Information for the When a new email arrives trigger
The logic app workflow trigger is created.
8. Click Save in the Designer toolbar to save the app.
Step 3: In Azure Logic Apps, create the steps in the logic app workflow.
1. Click + New step below the trigger step.
The window for selecting the action will appear.
2. Select the connector and the action to be performed.
The window for selecting the action will appear.
3. Select the connector and the action to be performed.
- Use the search field to filter the list of connectors.
- Select the connector you want.
The list of all actions available for the selected connector will appear. - Select the action you want.
example
- Filter the HTTP connectors.
- Select the HTTP connector.
- Select the HTTP - HTTP action.
4. Specify the information for the action based on your requirements.
Note: The list of variables available is automatically displayed when you click one of the fields.
example Define the email to be sent when a service request is created in Service Manager
5. Click Save in the Designer toolbar to save the workflow.
Step 5: Verification and test.
1. In the Designer toolbar, click Run.
2. Check the workability of the workflow. A should appear in the Designer window.
example Send an email with a new service request using a specific email address ==> Creation of the corresponding service request in Service Manager
AccountFreeCreation
How to create a free Azure account
1. Go to the Microsoft Azure website.
2. Click Start free.
3. Log in to your professional Microsoft account.
4. Enter the login information.
5. Click Next.
6. Tick the I agree box.
7. Click Sign up.