Microsoft Azure Logic Apps Integration


About This Integration
IntegrationIntroduction

You can integrate third-party systems with Product name - ev itsm.png 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 Logo - EasyVista.png Consulting & Professional Services team, the Logo - EasyVista.png 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.

    Example documentation icon EN.png  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
       Open url.png See List of connectors

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. Open url.png 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 Product name - ev itsm.png and supported third-party services:

  • Carry out actions in third-party services from an Product name - ev itsm.png workflow or business rule.  Open url.png See Integration Process no. 1.

        Example documentation icon EN.png  

    • The approval of the onboarding request for a new employee (HR Onboarding process managed in an Product name - ev itsm.png 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 Product name - ev itsm.png 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 Product name - ev itsm.png 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.
  • Carry out actions in Product name - ev itsm.png using third-party services.  Open url.png See Integration Process no. 2.

    Example documentation icon EN.png 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 Product name - ev itsm.png with the description of the Trello card.

     
Integration Data Feed (direction) Authentication Type Integration Connector Options

Product name - ev itsm - big.png

Up and Down arrow.png

Logo - Microsoft Azure Logic Apps.png

  • Based on the external service used (authentication performed by Microsoft Azure Logic Apps)
  • Basic Authentication for the REST API Product name - ev itsm.png

Product name - ev itsm.png SaaS

Product name - ev itsm.png On-premise

Check icon.png

Check icon.png

SaaS Version of Third-Party Product

On-Premise Version of Third-Party Product

Check icon.png

N/A

Step-by-Step Integration Process

Documentation

Open url.png See the wiki
Open url.png See the Microsoft Logic Apps documentation
Open url.png See the documentation on tools
Open url.png See Pricing

Prerequisites

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 Product name - ev itsm - big.png workflow or business rule to carry out actions in a third-party service

Open url.png 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).

Example documentation icon EN.png This process is based on a simple use case. A service request created in Product name - ev itsm.png 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 Product name - ev itsm.png)

         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 Product name - ev itsm.png 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.
         Process 1 & 2 - Menu new Logic app.png

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 ].
         Process 1 - Step 1 - Window Create Logic App.png

  • Name: Name of your logic app.

    Note: Letters and numbers as well as the following characters are authorized:-  (  )  . . There must be no spaces.

    Example documentation icon EN.png  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.
             Process 1 - Step 1 - Select trigger.png
  • In the Designer toolbar, click [ SAVE ] to generate the URL of the trigger.
             Process 1 - Step 1 - Generate url.png

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 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 action of a connector.

Example documentation icon EN.png An action for sending an email when a Logic Apps Rest action is triggered in an Product name - ev itsm.png 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.
         Process 1 & 2 - Menu new action.png

2.2. Select the action to perform.
         Process 1 - Step 2 - Action.png

  • Use the search field to filter the list of connectors and select the one you want in the Connectors section.
             Example documentation icon EN.png  Enter Outlook and select Office 365 Outlook.
  • The Actions section will display all actions predefined for the selected connector. Select the one you want.
             Example documentation icon EN.png  Office 365 Outlook - Send an email action

2.3. Specify the authentication information required for logging in to the service or click Change connection.
         Example documentation icon EN.png  User name and password for the Office 365 Outlook account

2.4. Specify the information for the action based on your requirements.
         Example documentation icon EN.png  Send an email to a mailing list using the Office 365 Outlook connector
         Process 1 - Step 2 - Example Action details.png

2.5. In the Designer toolbar, click [ SAVE ].
         Process 1 & 2 - Save action.png
 

Step 3: In Product name - ev itsm.png, create a Logic Apps REST action in a workflow or business rule.

         Open url.png See the procedure called How to configure a REST action type for a new service.

3.1. Create a new Logic Apps service.
         Process 1 - Step 3 - New service.png

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.

         Process 1 - Step 3 - New connection.png

Value of the {subdomain} parameter of the Logic Apps service URL = code before .logic in the URL provided by Logic Apps in step 1.  

Example documentation icon EN.png  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.
    Example documentation icon EN.png  #[DB_FIELDS.RFC_NUMBER]# parameter

Example documentation icon EN.png New resource passing the incident number and description in the email sent to a mailing list.
         Process 1 - Step 3 - New resource.png

Best Practice icon.png 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.
         Process 1 - Step 3 - New action REST.png
 

Step 4: In Logic Apps, configure the trigger and action to manage Product name - ev itsm.png parameters.

         Open url.png See Use the HTTP Request trigger.

         Notes:

  • To pass Product name - ev itsm.png 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 Product name - ev itsm.png parameters.

4.1. Configure the trigger by creating a JSON schema for the body of the HTTP request trigger:

  • In Product name - ev itsm.png, 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 JSONSchemanet editor - Copy clipboard icon.png.
               Process 1 - Step 4 - JSONSchemanet editor.png
       
  • Return to Logic Apps and paste the JSON schema in the Request Body JSON Schema field.
             Process 1 - Step 4 - Logic Apps request body.png
     
  • Optional: To configure the name of properties for Product name - ev itsm.png parameters appearing in the dynamic content window in the next step, modify the JSON schema in Logic Apps or in the jsonschema.net editor.

Example documentation icon EN.png Modify the value of title objects below the Properties object

  • comment > title object: Description of the incident in Product name - ev itsm.png
          ==> Previous value The comment schema
          ==> New value EVSM_Request_Description
  • rfc_number > title object: Incident number in Product name - ev itsm.png
          ==> Previous value The rfc_number schema
          ==> New value EVSM_Request_Number
    Process 1 - Step 4 - Modify JSON schema.png

4.2. Configure the action by inserting the dynamic content using the JSON schema properties you previously added.

Process 1 - Step 4 - Dynamic content in Send email step.png Process 1 - Step 4 - Dynamic content selection.png

Step 5: Verification and test.

Example documentation icon EN.png Creation of a service request in Product name - ev itsm.png 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 1 - Step 5 - Verification ev SM Incident form.png
         Process 1 - Step 5 - Verification ev SM email.png

Process no. 2: Third-party software to ev|Service Manager

Process no. 2: Use a logic app workflow to carry out actions in Product name - ev itsm - big.png from a third-party service

Open url.png  See the Microsoft Azure documentation:

Example documentation icon EN.png 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 Product name - ev itsm.png.

Step 1: In Logic Apps, workflow initialization by a trigger (from a third-party service)

         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 an event occurring in a third-party service.
  • You use the trigger of a connector.

Example documentation icon EN.png 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.
         Process 1 & 2 - Menu new Logic app.png

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 ].
         Process 2 - Step 1 - Window Create Logic App.png

  • Name: Name of your logic app.

    Note: Letters and numbers as well as the following characters are authorized:-  (  )  . . There must be no spaces.

    Example documentation icon EN.png  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.
             Process 2 - Step 1 - Select trigger.png
  • Use the search field to filter the list of connectors and select the one you want in the Connectors section.
             Example documentation icon EN.png  Enter Outlook and select Office 365 Outlook.
     Process 2 - Step 1 - Connector selection.png
  • The Triggers section will display all triggers defined for the selected connector. Select the one you want.
             Example documentation icon EN.png  Office 365 Outlook - When a new email arrives trigger
             Process 2 - Step 1 - Trigger selection.png

1.6. Specify the authentication information required for logging in to the service or click Change connection.
         Example documentation icon EN.png  User name and password for the Office 365 Outlook account

1.7. Specify the information for the trigger based on your requirements.
         Process 2 - Step 1 - Example Trigger details.png

1.8. In the Designer toolbar, click [ SAVE ].
         Process 1 & 2 - Save action.png
 

Step 2: In Logic Apps, workflow finalization (action in Product name - ev itsm.png)

         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.

Example documentation icon EN.png A HTTP POST request is sent to the Product name - ev itsm.png 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.
         Process 1 & 2 - Menu new action.png

2.2. In the Connectors section, select the Logic Apps connector - HTTP.png connector.
         Process 2 - Step 2 - Connector selection.png

2.3. In the Actions section, select the HTTP - HTTP action.
         Process 2 - Step 2 - Action selection.png 

2.4. Specify the information for the HTTP action based on your requirements, using the Product name - ev itsm.png REST API and the dynamic content available.
         Example documentation icon EN.png  Action creating a service request in Product name - ev itsm.png:

  • Recipient and requestor: Defined by the address of the email sender. 
  • Description of the incident: Content from the email subject and body.
Process 2 - Step 2 - Dynamic content in Receive email step.png Process 2 - Step 2 - Dynamic content selection.png

2.5. In the Designer toolbar, click [ SAVE ].
         Process 1 & 2 - Save action.png
 

Step 3: Verification and test.

3.1. In the Designer toolbar, click [ RUN ].
         Process 2 - Run action.png

3.2. Check the workability of the workflow. A Check icon.png should appear in the Designer window.
         Process 2 - Step 3 - Verification App logic workflow.png

Example documentation icon EN.png An email with a new service request is sent using a specific address ==> A service request is created in Product name - ev itsm.png.

         Process 2 - Step 3 - Verification App logic  email.png
         Process 2 - Step 5 - Verification ev SM request.png

Tags:
Last modified by Unknown User on 2018/07/04 12:00
Created by Administrator XWiki on 2017/10/18 16:29

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:

-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

How to Automate Integration
Add a Shortcut to an App
History
Quick Dashboard
Full text search - Stop Words

Powered by XWiki ©, EasyVista 2018