- Getting started
- Notifications
- Licensing
- Troubleshooting
- Connector Builder
- Act! 365
- ActiveCampaign
- Active Directory - Preview
- Adobe Acrobat Sign
- Adobe PDF Services
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- CrewAI – Preview
- Customer.io
- Datadog
- DeepSeek
- Deputy
- Discord - Preview
- DocuSign
- Drip
- Dropbox
- Dropbox Business
- Egnyte
- Eventbrite
- Exchangerates
- Exchange Server - Preview
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms - Preview
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Text-to-Speech
- Google Tasks - Preview
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP Webhook - Preview
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure OpenAI
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Power Automate – Preview
- About the Microsoft Power Automate connector
- Microsoft Power Automate authentication
- Microsoft Sentiment
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Okta
- OpenAI
- OpenAI V1 Compliant LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce AgentForce & Flows – Preview
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Data Fabric – Preview
- UiPath GenAI Activities
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo

Integration Service user guide
You can choose between the following authentication options:
-
OAuth 2.0 Authorization code: Connects to the UiPath public application with your Microsoft account credentials, and, optionally, to your shared mailbox.
-
Bring your own OAuth 2.0 app: Connects to a private application you create, and, optionally, to your shared mailbox.
In case you encounter any errors during the sign-in process, we recommend you contact your Microsoft Power Automate administrator.
Many organizations require the consent of an administrator before you create a connection to an external application. The admin consent workflow requires an admin to approve the app registration to specific users or groups before a connection is established. For more details, refer to Overview of admin consent workflow and User and admin consent in Microsoft Entra ID in the Microsoft documentation.
-
Integration Service impersonates the user that creates the connection. The credentials of the user offer access to all of the same resources that they have in the given application. If you share the connection, every change made to Microsoft Power Automate with that connection is made on behalf of that user.
-
The Microsoft Power Automate connector uses OAuth 2.0 to authenticate and access Microsoft Dataverse APIs behind the scenes. Scopes are automatically managed through Azure AD app, requiring no manual configuration by the user.
The connector requests the following permissions/scopes:
-
OAuth 2.0 Authorization code:
offline_access
,.default
-
Bring your own OAuth 2.0 app:
-
Minimal scopes for creating a connection:
openid
,offline_access
-
Adding the Microsoft Power Automate connection
To create a connection to your Microsoft Power Automate instance, perform the following steps:
-
Select Integration Service from Automation CloudTM.
-
From the Connectors list, select Microsoft Power Automate, or use the search bar to find the connector.
-
Select Connect to Microsoft Power Automate.
-
You are now redirected to the connection page.
-
Select the OAuth 2.0 Authorization code authentication type.
-
Enter the environment ID.
-
Add the necessary scopes.
-
Enter the Tenant ID.
-
Select Connect.
-
Authenticate with your Microsoft email address and password.
Refresh tokens for OAuth applications
Refresh tokens for OAuth applications can be invalidated or revoked at any time by Microsoft. This can happen for different reasons, such as timeouts and revocations. For details, see Microsoft's official documentation.
Token invalidation results in failed connections and automations are unable to run without fixing connections.
Make sure to follow best practices from Microsoft when creating your OAuth applications. For full details on how to create a Microsoft OAuth app, refer to the Microsoft documentation: Register an application with the Microsoft identity platform.
To learn how to create an application, go to Microsoft's official documentation and follow the described steps: Register an application with the Microsoft identity platform.
Requirements
When creating your own application to use with Integration Service, you must consider the following requirements:
-
You must configure the application as a Multitenant or Single tenant application.
-
You must configure a Web application.
-
You must configure a Web Redirect URI. The Redirect URI (or callback URL) for your OAuth 2.0 application is provided in the authentication screen when creating a connection: https://cloud.uipath.com/provisioning_/callback.
-
You must set up delegated permissions. For more information, refer to Permissions in the Microsoft official documentation.
-
Generate a client secret for your application.
Adding the Microsoft Power Automate connection
To create a connection to your Microsoft Power Automate instance, perform the following steps:
-
Select Integration Service from Automation CloudTM.
-
From the Connectors list, select Microsoft Power Automate, or use the search bar to find the connector.
-
Select Connect to Microsoft Power Automate.
-
You are now redirected to the connection page.
-
Select the Bring your own OAuth 2.0 app authentication type.
-
Fill in the required fields: Client ID, Client secret, Environment ID, and Tenant ID.
- Add the necessary scopes.