- Getting started
- Notifications
- Troubleshooting
- Connector Builder
- 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 ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- Customer.io
- Datadog
- Deputy
- Discord
- DocuSign
- Drip
- Dropbox
- 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 - Preview
- Google Workspace
- GoToWebinar
- Greenhouse
- HTTP Webhook - Preview
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail - Preview
- 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
- Okta
- OpenAI
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Data Service
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- ZoomInfo
![](https://docs.uipath.com/_next/static/media/grid.05ebd128.png?w=3840&%3Bq=100)
Integration Service user guide
Microsoft Outlook 365 authentication
In Integration Service, when creating a connection to one of our Microsoft Graph-based connectors, you can choose between three authentication options:
- OAuth 2.0 Authorization code – connects to the UiPath public application.
- OAuth 2.0 Client credentials - uses a service account.
- Bring your own OAuth 2.0 app – connects to a private application you create.
- OAuth 2.0 Authorization code: your Microsoft account credentials, and, optionally, your shared mailbox.
For more details regarding the different authentication types, refer to the How to connect to Microsoft 365 activities guide.
Environment
When you first access the Authentication screen, you can select an Environment. The available options are:
- Office 365 (default)
- US Government L4 - Public Sector domain
- US Government L5 - Public Sector domain
- China
For details, refer to Microsoft Graph and Graph Explorer service root endpoints.
Many organizations require an administrator's consent before creating 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 information, 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 user’s credentials 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 SharePoint or OneDrive with that connection is made on behalf of that user.
The connector requests the following permissions/scopes:
- OAuth 2.0 Authorization code:
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
. - OAuth 2.0 Client credentials:
- Minimal scopes required for creating a connection:
Mail.Read
,User.Read
.
- Minimal scopes required for creating a connection:
- Bring your own OAuth 2.0 app:
- 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.
- Minimal scopes required for creating a connection:
common
scope. This means you use only the permissions configured for that application in Azure. You can also declare additional
scopes at connection creation, using the Scopes field. You will then be asked to grant the additional consent during sign-in.
To create a connection to your Microsoft Outlook 365 instance, you need to perform the following steps:
-
Select Integration Service from Automation CloudTM Public Sector.
- From the Connectors list, select Microsoft Outlook 365. You can also use the search bar to find the connector.
- Select the Connect to Microsoft Outlook 365 button.
- You are now redirected to the connection page.
You can choose between three authentication types: OAuth 2.0 Authorization code, OAuth Client credentials, or Bring your own OAuth 2.0 app.
- If you select OAuth 2.0 Authorization code, select Connect, then authenticate using your Microsoft email address and password.
Note:
- You can provide your shared mailbox in the Shared mailbox field, which is inherited by all Outlook activities once you connect.
- If you select OAuth 2.0 Client credentials, you must provide an Account. This represents the account used to impersonate a user.
- If you select Bring your own OAuth 2.0 app, you must provide a Client ID and Client secret, the Tenant ID, and the Scopes you may need to interact with different activities.
Check out the activities' documentation to learn what scopes they require.
Note: If you are using a multitenant application, keep the default value for the Tenant ID (
common
). If you are using a single tenant application, retrieve the Tenant ID from Azure. Refer to How to find your Microsoft Entra tenant ID.
- If you select OAuth 2.0 Authorization code, select Connect, then authenticate using your Microsoft email address and password.
- Your connection has been added.
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.
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://govcloud.uipath.us/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 its Client ID and Client Secret to create a connection with the Microsoft connectors.
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.