- 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.
Integration Summary
Microsoft Azure Logic Apps enables you to integrate and connect hundreds of Web apps, services (cloud or on-premises), data and devices easily.
- It uses a large ever growing ecosystem of standard connectors.
Standard connectors: Azure (Active Directory, …), Office 365 (Outlook, One Drive, SharePoint, Dynamics…), Skype For Business, Teams, Planner, Jira Software, SAP, Google Suite, Salesforce, Dropbox, Slack, Facebook, Twitter, Plivo, LiveChat, MySQL, SFTP, Service Bus
See List of connectors
- It is used to interface with any endpoint via HTTP/HTTPS, e.g. via REST APIs.
- It is a tool similar to Zapier and IFTTT, both also supported by thanks to standard connectors (services) that can be used in REST actions in a workflow or business rule. See Zapier integration.
Note: Microsoft Flow is a similar tool integrated with certain Microsoft Office 365 solutions, based on Logic Apps, with the same workflow designer and connectors. It enables any users to perform basic integrations, e.g. receiving SMS notifications for important emails without requiring developers or the IT Department. See the Flow Plan FAQ
Unlike Logic Apps applications are used for advanced or strategic integrations, e.g. B2B processes that require corporate development and security practices. For this reason, Logic Apps includes more functionalities intended for IT teams and developers.
Microsoft Azure Logic Apps enables you to perform 2 types of integration between and supported third-party services:
- Carry out actions in third-party services from an workflow or business rule. See Integration Process no. 1.
- The approval of the onboarding request for a new employee (HR Onboarding process managed in an workflow) will result in the creation of a user in Microsoft Azure Active Directory with all available information, e.g. name, first name, title, department, location, phone number, etc. The user will be added to an AD group and a manager will be assigned.
- The creation of a new incident in via a standard workflow for managing incidents or via a business rule will result in the creation of the incident in Jira Software.
- The approval of an SAP-related change request in an change management workflow step will result in the creation of new card in Trello, a Project Portfolio Management software used by the Design and Development Department. The name of the new card is the change request number and is found in the list of Validated SAP Change Requests in the SAP Development Follow-Up table.
- The approval of the onboarding request for a new employee (HR Onboarding process managed in an
- Carry out actions in using third-party services. See Integration Process no. 2. The creation of a new Trello card in the New Training list in the New Training Catalog table used by the Human Resources department will result in the creation of a New Training Analysis service request in with the description of the Trello card.
| Integration Data Feed (direction) | Authentication Type | Integration Connector Options | ||
|---|---|---|---|---|
|
|
|
|
Connector: When a HTTP request is received
Connector: HTTP – HTTP
|
|
|---|---|
|
|
SaaS Version of Third-Party Product |
On-Premise Version of Third-Party Product |
|
N/A |
Step-by-Step Integration Process
Documentation
See the wiki
See the Microsoft Logic Apps documentation- What are Logic Apps?
- Connectors list
- Connectors: Overview and References
- Create your first logic app
- Triggers and actions for logic app workflows
- Logic App Templates
- Get started with the request and response components
- The HTTP Request trigger Connector
- 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
- Choose between Flow, Logic Apps, Functions, and WebJobs
- Microsoft Azure documentation
See the documentation on tools- JSON schema (JSON online editor)
- jsoneditoronline.org (JSON online editor)
- Postman (API development and testing environment)
- SoapUI (API and protocol testing environment)
See PricingPrerequisites
- 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 the relevant accounts and access rights to the services interfacing with Logic Apps.
- You must have an account giving you access to your platform with a profile and access rights sufficient to create or modify a workflow, access to Administration menu and to other menus which you need as for example Operation and Transition.
Process no. 1: ev|Service Manager to third-party services
Process no. 1: Use a logic app workflow with a Logic Apps REST action in an 
workflow or business rule to carry out actions in a third-party service
See 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).
This process is based on a simple use case. A service request created in by a VIP (high priority) triggers the sending of an email to a mailing list of members in charge of processing VIP requests, using a specific Office 365 Outlook account.
Step 1: Workflow initialization with a trigger (from )
Notes:
- A trigger is an event that starts the workflow of your logic app and is the first element required.
- In this process, the trigger is a Logic Apps REST action triggered in an workflow. It sends a HTTP request via a POST method to an endpoint (URL).
- You use the HTTP request trigger.
1.1. Log in to the Microsoft Azure portal.
1.2. In the left pane, select New > Enterprise Integration > Logic App.
1.3. In the Logic App connector window, click [ CREATE ].
1.4. In the Create logic app window, specify the information below and click [ CREATE ].
- Name: Name of your logic app.
Note: Letters and numbers as well as the following characters are authorized:- ( ) . . There must be no spaces.
EVSM_New_Request_WKFW_(High-VIP)_SendE-mail - Subscription: Your Azure subscription.
- Resource group: Azure resource group, used to organize and manage Azure resources. Select an existing one or create a new one.
- Location: Location of the data center hosting your logic app.
- Pin to dashboard: Select this box to display your logic app in the Azure dashboard after deployment and open it automatically.
1.5. Select your trigger in the Logic Apps Designer:
- Select the [ When a HTTP request is received ] trigger or select an existing predefined template.
- In the Designer toolbar, click [ SAVE ] to generate the URL of the trigger.
1.6. Copy the URL (URL HTTP POST) provided by Logic Apps, to be used in step 3.
Step 2: In Logic Apps, workflow finalization (action in the third-party service).
Notes:
An action for sending an email when a Logic Apps Rest action is triggered in an workflow. It sends a REST request via a POST method to the endpoint (URL) provided in step 1.
2.1. In the Designer, select + New step > Add an action below the trigger.
2.2. Select the action to perform.
- Use the search field to filter the list of connectors and select the one you want in the Connectors section.
Enter Outlook and select Office 365 Outlook. - The Actions section will display all actions predefined for the selected connector. Select the one you want.
Office 365 Outlook - Send an email action
2.3. Specify the authentication information required for logging in to the service or click Change connection.
User name and password for the Office 365 Outlook account
2.4. Specify the information for the action based on your requirements.
Send an email to a mailing list using the Office 365 Outlook connector
2.5. In the Designer toolbar, click [ SAVE ].
Step 3: In , create a Logic Apps REST action in a workflow or business rule.
See the procedure called How to configure a REST action type for a new service.
3.1. Create a new Logic Apps service.
3.2. Create a new connection to the service.
Note: The {subdomain} parameter will depend on the location of the data center hosting your logic app. It is identical to the one selected in step 1.
Value of the {subdomain} parameter of the Logic Apps service URL = code before .logic in the URL provided by Logic Apps in step 1.
URL 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 ==> prod-29.eastus
3.3. Create a new resource for the service.
Note: You can pass parameters to Logic Apps to use them in a third-party app.
#[DB_FIELDS.RFC_NUMBER]# parameter
New resource passing the incident number and description in the email sent to a mailing list.
In the Content field, we recommend that you use a JSON schema online editor to ensure that all unnecessary spaces and line breaks are deleted (see above).
If you paste a JSON schema copied from a third-party editor such as Microsoft Word, Notepad++, etc., invisible characters may be inserted. This will create an error in the processing of the REST step using the resource.
3.4. Add and configure a REST action using the connection and resource you previously created.
Step 4: In Logic Apps, configure the trigger and action to manage parameters.
See Use the HTTP Request trigger.
Notes:
- To pass parameters to Logic Apps, you must provide a JSON schema in the body of the HTTP request trigger. To do this, you can use jsonschema.net.
- You can also use tokens generated by the Logic Apps Designer for properties in the HTTP request trigger.
- When you use dynamic content functionalities in an action, you can use the properties corresponding to the parameters.
4.1. Configure the trigger by creating a JSON schema for the body of the HTTP request trigger:
- In , copy the content of the JSON schema from the Content field of the REST resource created in step 3.
- Delete all invisible characters using a text editor such as Notepad++.
- Open the editor in jsonschema.net:
- (1) Paste the content in the JSON field and click [ SUBMIT ].
- (2) Switch to Plain mode and copy the JSON schema using
.
- Return to Logic Apps and paste the JSON schema in the Request Body JSON Schema field.
- Optional: To configure the name of properties for parameters appearing in the dynamic content window in the next step, modify the JSON schema in Logic Apps or in the jsonschema.net editor.
Modify the value of title objects below the Properties object
- comment > title object: Description of the incident in
==> Previous value The comment schema
==> New value EVSM_Request_Description - rfc_number > title object: Incident number in
==> Previous value The rfc_number schema
==> New value EVSM_Request_Number
4.2. Configure the action by inserting the dynamic content using the JSON schema properties you previously added.
 |
 |
Step 5: Verification and test.
Creation of a service request in via a specific catalog entry ==> An email is automatically sent to a mailing list of members in charge of processing VIP requests, using a specific Office 365 Outlook account.
Process no. 2: Third-party software to ev|Service Manager
Process no. 2: Use a logic app workflow to carry out actions in from a third-party service
See the Microsoft Azure documentation:
- Create your first logic app (sending of an email using an Outlook account when new content is posted in an RSS feed).
- Deploy and call custom APIs from logic app workflows (Call your custom API from logic app workflows section).
This process is based on a simple use case. An email is received in the Inbox folder of a specific Office 365 Outlook account. The email contains a service request. This triggers the creation of a service request in .
Step 1: In Logic Apps, workflow initialization by a trigger (from a third-party service)
Notes:
An email is received in the Inbox folder of a specific Office 365 Outlook account. The subject of the email contains the text, New Request By Email.
1.1. Log in to the Microsoft Azure portal.
1.2. In the left pane, select New > Enterprise Integration > Logic App.
1.3. In the Logic App connector window, click [ CREATE ].
1.4. In the Create logic app window, specify the information below and click [ CREATE ].
- Name: Name of your logic app.
Note: Letters and numbers as well as the following characters are authorized:- ( ) . . There must be no spaces.
Create_Request_in_EVSM_from_NewE-mail - Subscription: Your Azure subscription.
- Resource group: Azure resource group, used to organize and manage Azure resources. Select an existing one or create a new one.
- Location: Location of the data center hosting your logic app.
- Pin to dashboard: Select this box to display your logic app in the Azure dashboard after deployment and open it automatically.
1.5. Select your trigger in the Logic Apps Designer:
- Select the [ Blank Logic App ] trigger or select an existing predefined template.
- Use the search field to filter the list of connectors and select the one you want in the Connectors section.
Enter Outlook and select Office 365 Outlook.
- The Triggers section will display all triggers defined for the selected connector. Select the one you want.
Office 365 Outlook - When a new email arrives trigger
1.6. Specify the authentication information required for logging in to the service or click Change connection.
User name and password for the Office 365 Outlook account
1.7. Specify the information for the trigger based on your requirements.
1.8. In the Designer toolbar, click [ SAVE ].
Step 2: In Logic Apps, workflow finalization (action in )
Notes:
- An action is a task performed by the workflow of your logic app.
- Once you have added the trigger to your logic app, you can add an action to perform operations with the data generated by the trigger or other actions thanks to dynamic content.
- You use the HTTP – HTTP action connector.
A HTTP POST request is sent to the REST API to create a service request. The email sender will be specified as the recipient/requestor and the content from the email subject and body will be pasted in the description of the service request.
2.1. In the Designer, select + New step > Add an action below the trigger.
2.2. In the Connectors section, select the 
connector.
2.3. In the Actions section, select the HTTP - HTTP action.
2.4. Specify the information for the HTTP action based on your requirements, using the REST API and the dynamic content available.
Action creating a service request in :
- Recipient and requestor: Defined by the address of the email sender.
- Description of the incident: Content from the email subject and body.
 |
 |
2.5. In the Designer toolbar, click [ SAVE ].
Step 3: Verification and test.
3.1. In the Designer toolbar, click [ RUN ].
3.2. Check the workability of the workflow. A 
should appear in the Designer window.
An email with a new service request is sent using a specific address ==> A service request is created in .
