Skip to main content

Celonis Product Documentation

Microsoft Power Automate

Note

Microsoft Power Automate Desktop is part of a limited availability release for the time being. If you find that the Power Automate Desktop app is not active in your environment, please open a Support ticket.

Introduction

Microsoft Power Automate Desktop flows broaden the existing robotic process automation (RPA) capabilities in Power Automate.

Desktop flows automate users’ day-to-day tasks on the desktop, such as copying and pasting data, making calculations, and moving files.

By combining Microsoft Desktop flows with EMS Action Flows, you can:

  • leverage your existing bots and take targeted action by intelligently triggering them based on insights from EMS.

  • automate your entire landscape by combining API-led automation and UI-led automation in one Action Flow.

Pre-requisites

To use Power Automate Desktop with you need to:

  • install Power Automate Designer to create and configure Desktop Flows that will be run from EMS.

  • make sure you have Admin rights on Azure if you want to use your own Client Id and Client Secret for authentication and to establish a connection.

Functionality

By using the Power Automate Desktop app in Action Flows, users can trigger a Power Automate Desktop flow. The flows can run in Attended or Unattended mode.

This page explains how to:

  • set up a connection to Power Automate Desktop

  • configure and run a Desktop flow

Connect Microsoft Power Automate to Execution Management System

You can connect to Microsoft Power Automate in two ways:

Connect using OAuth 2.0

To connect to Microsoft Power Automate:

  1. Log in to your Execution Management System , and open the Microsoft Power Automate module Action Flow .

  2. In the Connection name field, enter a name for the connection.

    msedge_mSDCbrU3W9.gif
  3. In the Connection name field, enter a name for the connection.

  4. Optional: In the MS PAD Environment ID field, enter your environment ID from your Power Automate account to which you want to connect.

    Leave this field empty to choose your default environment. If you have multiple environments, go to the Power Automate admin portal to copy the desired environment ID.

    msedge_8HQZQXagD1.png
  5. Click Continue.

  6. In the pop-up window, enter your account details to sign in and authorize access by clicking Accept.

    msedge_XPHSxnctMO.png

You have successfully connected the Microsoft Power Automate app and can now build Action Flows .

Connect using OAuth 2.0 and your own credentials

To connect to Power Automate with your own credentials, you need to create a custom app in your Azure account and obtain the client credentials of the app.

  1. Log in to azure.portal.com.

  2. Click App Registrations.

    msedge_m80f4l7skA.png
  3. Click New Registration.

    msedge_axiNLCZb9j.png
  4. Enter the details as provided in the table below and click Register.

    msedge_l2QiIjb4dM.png

    Name

    Enter the app's name that you want to connect.

    Supported account types

    Select the option, Accounts in any organizational directory (Any Azure AD Directory - Multitenant).

    Redirect URI (Optional)

    Select the following options:

    • Platform: Web

    • Redirect URI: https://auth.redirect.celonis.cloud/oauth/cb/microsoft-power-automate

      msedge_4VtGgbQXKt.png
  5. You can find the Client ID and Tenant ID details on the app screen. To add a client secret, click Add a certificate or secret.

    msedge_JAgFK3D5QZ.png
  6. Click New client secret. Enter a description and select the expiry period for the client secret. Click Add.

    msedge_uQZSoRUNL3.png
  7. Copy the Client Secret to a safe place.

    msedge_Go0YLZK4iN.png
  8. In the Manifest section, change the allowPublicClient value to true, and click Save.

    msedge_sOLK0rHqyS.png
  9. Log in to your Execution Management System account and open the Microsoft Power Automate Action Flow , select the Advanced Settings checkbox.

    msedge_dkCjV4LcNE.png
  10. In the Connection name field, enter a name for the connection.

  11. Leave this field empty to choose your default environment. If you have multiple environments, go to the Power Automate admin portal to copy the desired environment ID.

    Optional: In the MS PAD Environment ID field, enter your environment ID from your Power Automate account to which you want to connect.

    msedge_8HQZQXagD1.png
  12. In the Client ID, Client Secret, and Tenant ID fields, enter the values copied in step 5 and step 7 respectively.

  13. Click Continue.

  14. In the pop-up window, enter your account details to sign in and authorize access by clicking Accept.

    msedge_XPHSxnctMO.png

You have all the details to connect your custom app with Execution Management System , and can now build Action Flows .

Actions

You can run desktop flows using the following module.

Run Desktop Flow

Set up a desktop flow connection if you use the on-premises data gateway to trigger desktop flows.

Connection

Establish a connection to your Microsoft Power Automate account.

Select MS PAD Flow Connection

Enter the connection flow ID of the desktop flow you want to run.

To create a flow connection, see connections.

You can get the Connection ID in your Power Automate account at Data > Connections > Select the connection > URL. In the URL address, find a part which says, ConnectionName and copy the ID that follows it

slack_hjNxewZacN.png

Select MS PAD Desktop Flow

Select or map the flow you want to run. Only the Desktop Flows created in your Microsoft Power Automate account are displayed here.

The map function allows a user to map a value from one of the previous modules instead of selecting a Bot from the dropdown list.

To create a desktop flow, see UI flows.

Flow Input fields

Add the input variables for the flow. These variables are passed to and from desktop flows, allowing you to create sophisticated flows.

To create variables, see input variables.

Select Run Mode

Select the run mode for the desktop flow depending on your settings.

  • Attended: Requires an active Windows user session that matches the name of the user configured for your connection. The session must not be locked. When an attended desktop flow starts on the target machine, it is recommended to avoid interacting with your device until the run completes.

  • Unattended: The target machine needs to be available with all users signed out. You cannot launch flows with elevated privileges.

To learn more about run modes, see desktop flow modes.

For more information on desktop flows, see Microsoft Power Automate documentation.