- 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
- 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
- About the Microsoft Outlook 365 connector
- Microsoft Outlook 365 authentication
- Microsoft Outlook 365 events
- 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 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 Service - 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
Microsoft Outlook 365 authentication
In Integration Service, when you create a connection to one of our Microsoft Graph-based connectors, 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, your shared mailbox.
- OAuth 2.0 Client credentials – uses a service account.
- Bring your own OAuth 2.0 app – connects to a private application you create.
In case you encounter any errors during the sign-in process, it is recommended to contact your Microsoft Outlook 365 administrator. For more information, refer to the Office 365 Outlook connector documentation.
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, chek Overview of admin consent workflow and User and admin consent in Microsoft Entra ID in the Microsoft documentation.
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.
Make sure to follow best practices from Microsoft when creating your OAuth applications. For full details on how to create a Microsoft OAuth app, see the Microsoft documentation.
This issue affects not only the OneDrive & SharePoint connector, but all Microsoft Graph-based connectors, such as Outlook or Teams.
Mail.Read
, Mail.Read.Shared
,
Mail.ReadWrite
, Mail.ReadWrite.Shared
,
Mail.Send
, Mail.Send.Shared
,
MailboxSettings.ReadWrite
, Calendars.Read
,
Calendars.Read.Shared
, Calendars.ReadWrite
,
Calendars.ReadWrite.Shared
, profile
,
openid
, email
,
offline_access
, User.Read
.
To create a connection to your Microsoft Outlook 365 instance, perform the following steps:
-
Select Integration Service from Automation CloudTM.
- From the Connectors list, select Microsoft Outlook 365, or use the search bar to find the connector.
- Select Connect to Microsoft Outlook 365.
- You are now redirected to the connection page.
- From the gear icon, select the OAuth 2.0 Authorization code authentication type.
- Select an environment from the
drop-down list: Office 365 (default), US Government L4 - Public Sector
domain, US Government L5 - Public Sector domain, or
China.
Note: For more details on environments, check Microsoft Graph and Graph Explorer service root endpoints.
- Optionally, enter your shared
mailbox in the Shared mailbox field.
Note: All Outlook activities inherit the shared mailbox once you connect.
- Select Connect.
- Authenticate with your Microsoft email address and password.
Mail.Read
, User.Read
.
To create a connection to your Microsoft Outlook 365 instance, perform the following steps:
-
Select Integration Service from Automation CloudTM.
- From the Connectors list, select Microsoft Outlook 365, or use the search bar to find the connector.
- Select Connect to Microsoft Outlook 365.
- You are now redirected to the connection page.
- From the gear icon, select the OAuth 2.0 Client credentials authentication type.
- Fill in the required fields Client ID, Client secret, and,
optionally, the fields Tenant ID, Environment, Shared
mailbox, and Account.
Note:
- This authentication type is only for application permissions and does not require to impersonate a user. If you do not enter any Account, the connection acts similar to a service account, which does not impersonate any user. When you enter an account, it represents the account that impersonates a user.
- The account is mandatory for Outlook and Calendar triggers and activities.
- Select Connect.
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.
The connector uses Microsoft Graph API. Refer to the Microsoft Graph permissions reference page for details on all permissions.
After you create your application, use the Client ID and Client Secret to create a connection with the Microsoft connectors.
- Minimal scopes required for creating a connection:
openid
,offline_access
,Mail.Read
. - Minimal list of scopes required for Outlook triggers:
openid
,offline_access
,Mail.Read
,Mail.Read.Shared
– for shared mailbox triggers.Calendars.Read
– for events on calendars.Calendars.Read.Shared
– for events on shared calendars.
To create a connection to your Microsoft Outlook 365 instance, perform the following steps:
-
Select Integration Service from Automation CloudTM.
- From the Connectors list, select Microsoft Outlook 365, or use the search bar to find the connector.
- Select Connect to Microsoft Outlook 365.
- You are now redirected to the connection page.
- From the gear icon, select the Bring your own OAuth 2.0 app authentication type.
- Fill in the required fields: Client ID and Client secret, and, optionally, the Scope, required to interact with different activities, Tenant ID, Environment, and Shared mailbox.
Note:
- For more details check the documentation for activities to learn what scopes they require.
- If you use a multi-tenant application, keep the default value for the Tenant ID (
common
). - If you use a single tenant application, retrieve the Tenant ID from Azure. For more details, check How to find your Microsoft Entra tenant ID.