- 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
- Database Hub - Preview
- Databricks Agent
- 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
- 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 AI Foundry
- Microsoft Azure OpenAI
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- About the Microsoft OneDrive & SharePoint connector
- Microsoft OneDrive and SharePoint authentication
- Microsoft OneDrive & SharePoint events
- Microsoft Outlook 365
- Microsoft Power Automate – Preview
- 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
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath Apps - Preview
- UiPath Data Fabric – Preview
- UiPath GenAI Activities
- UiPath Orchestrator
- 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 OneDrive and SharePoint authentication
Overview
In Integration Service, when you create a connection to one of our Microsoft Graph-based connectors, you can choose between the following authentication options:
- Client Certificate Authentication – connects using a client certificate instead of a client secret.
- OAuth 2.0 Authorization code – connects to the UiPath public application.
- OAuth 2.0 Client credentials - connects using a service account.
- Bring your own OAuth 2.0 app – connects to a private application you create.
For more details regarding the different authentication types, refer to the How to connect to Microsoft 365 activities guide.
Admin consent
This section applies only to the OAuth 2.0 Authorization code and Bring your own OAuth 2.0 app authentication options.
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, check 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 SharePoint or OneDrive with that connection is made on behalf of that user.
Client Certificate Authentication
Scopes
The connector requires the following minimum scopes to create a connection: Files.Read.
The connector requires the following full set of scopes for all activities to function: offline_access, Files.Read, Files.Read.All, Files.ReadWrite, Files.ReadWrite.All, Sites.Read.All, Sites.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, profile, openid, email, User.Read.All, User.Read.
To add more granular permissions, refer to the activities documentation.
Adding the Microsoft OneDrive and SharePoint connection
To create a connection to your Microsoft OneDrive and SharePoint instance, perform the following steps:
- In Automation Cloud, select Integration Service from the rail menu.
- From the Connectors list, select Microsoft OneDrive and SharePoint, or use the search bar to find the connector.
- Select Connect to Microsoft OneDrive and SharePoint, which redirects you to the connection page.
- Select the Client Certificate Authentication authentication type.
- Configure the following fields:
-
Client ID - You can find the ID in the Overview section of your Microsoft Azure application registration.
-
Password for the certificate - The password you set during the certificate creation.
-
OAuth base64 client certificate - The client certificate is generated in a .pfx file format, which you must convert to Base64-encoded format and provide it in this field.
-
Tenant ID - You can find the Microsoft Azure tenant ID for an app in the Overview section of your Microsoft Azure application registration.
-
Environment - Optionally, select an environment from the dropdown list:
- Office 365 (default)
- US Government L4 - Public Sector domain
- US Government L5 - Public Sector domain
- China Select Office 365 (default) for all regions, and only switch to Government or China for cloud deployments.
Note:For more details on environments, check Microsoft Graph and Graph Explorer service root endpoints.
-
Account - Enter the user principal name (UPN) of the account or shared mailbox that the system should use in the connection. This is required for the connection to be established.
-
- Select Connect.
- Authenticate with your Microsoft email address and password.
OAuth 2.0 Authorization code
Scopes
The connector requires the following minimum scopes to create a connection: openid, offline_access, email, and Files.Read.
The connector requires the following full set of scopes for all activities to function: offline_access, Files.Read, Files.Read.All, Files.ReadWrite, Files.ReadWrite.All, Sites.Read.All, Sites.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, profile, openid, email, User.Read.All, User.Read.
To add more granular permissions, refer to the activities documentation.
Adding the Microsoft OneDrive and SharePoint connection
To create a connection to your Microsoft OneDrive and SharePoint instance, perform the following steps:
- In Automation Cloud, select Integration Service from the rail menu.
- From the Connectors list, select Microsoft OneDrive and SharePoint. You can also use the search bar to narrow down the connector.
- Select the Connect to Microsoft OneDrive and SharePoint button, which redirects you to the connection page.
- Select the OAuth 2.0 Authorization code authentication type.
- Configure the following:
- Scope - Optionally, add or remove permissions for your connector.
- Environment - Optionally, select an environment from the dropdown list:
- Office 365 (default)
- US Government L4 - Public Sector domain
- US Government L5 - Public Sector domain
- China Select Office 365 (default) for all regions, and only switch to Government or China for cloud deployments.
Note:For more details on environments, check Microsoft Graph and Graph Explorer service root endpoints.
- 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, see the Microsoft documentation.
This issue affects not only the OneDrive & SharePoint connector, but all Microsoft Graph-based connectors, such as Outlook or Teams.
OAuth 2.0 Client credentials
Scopes
The connector requires the following minimum scopes to create a connection: Files.Read.
The connector requires the following full set of scopes for all activities to function: offline_access, Files.Read, Files.Read.All, Files.ReadWrite, Files.ReadWrite.All, Sites.Read.All, Sites.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, profile, openid, email, User.Read.All, User.Read.
To add more granular permissions, refer to the activities documentation.
Adding the Microsoft OneDrive and SharePoint connection
To create a connection to your Microsoft OneDrive and SharePoint instance, perform the following steps:
- In Automation Cloud, select Integration Service from the rail menu.
- From the Connectors list, select Microsoft OneDrive and SharePoint. You can also use the search bar to narrow down the connector.
- Select the Connect to Microsoft OneDrive and SharePoint button, which redirects you to the connection page.
- Select the OAuth 2.0 Client credentials authentication type.
- Configure the following:
-
Client ID - You can find the ID in the Overview section of your Microsoft Azure application registration.
-
Client Secret - The client secret from the Certificates & secrets section of your Microsoft Azure application.
-
Tenant ID - The Microsoft Azure tenant ID for an app from the Overview section.
-
Environment - Optionally, select an environment from the dropdown list:
- Office 365 (default)
- US Government L4 - Public Sector domain
- US Government L5 - Public Sector domain
- China Select Office 365 (default) for all regions, and only switch to Government or China for cloud deployments.
Note:For more details on environments, check Microsoft Graph and Graph Explorer service root endpoints.
-
Account - Provide the account used to impersonate a user.
-
- Select Connect.
Bring your own OAuth 2.0 app
Overview
To learn how to create an application, check the official Microsoft documentation: Register an application with the Microsoft identity platform.
This is an advanced functionality and requires admin privileges in the target application. Work with your IT administrator to set up your application successfully.
Requirements
When you create your own application to use with Integration Service, make sure you meet the following requirements:
- Configure the application as a Multi-tenant or Single-tenant application.
- Configure a Web application.
- 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 advantage of using your private OAuth application is that you can customize permissions depending on your actual needs. To learn which scopes are required for each activity in the Microsoft 365 package, refer to Working with scopes and check out the activities documentation. 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.
Scopes
- The connector requires the following minimum scopes to create a connection:
openid,offline_access,email, andFiles.Read. - OneDrive triggers require the following minimum scopes:
- For events on SharePoint sites:
openid,offline_access, andUser.Read.AllorUser.ReadandSites.Read.All. - For events on groups and calendars:
Group.Read.All - For all the remaining event types:
Files.Read.All
- For events on SharePoint sites:
The connector requires the following full set of scopes for all activities to function: offline_access, Files.Read, Files.Read.All, Files.ReadWrite, Files.ReadWrite.All, Sites.Read.All, Sites.ReadWrite.All, Group.Read.All, Group.ReadWrite.All, profile, openid, email, User.Read.All, User.Read.
To add more granular permissions, refer to the activities documentation.
Adding the Microsoft OneDrive and SharePoint connection
To create a connection to your Microsoft OneDrive and SharePoint instance, perform the following steps:
- In Automation Cloud, select Integration Service from the rail menu.
- From the Connectors list, select Microsoft OneDrive and SharePoint. You can also use the search bar to narrow down the connector.
- Select the Connect to Microsoft OneDrive and SharePoint button, which redirects you to the connection page.
- Select the Bring your own OAuth 2.0 app authentication type.
- Configure the following:
- Client ID - You can find the ID in the Overview section of your Microsoft Azure application registration.
- Client Secret - The client secret from the Certificates & secrets section of your Microsoft Azure application.
- Scope - Optionally, add or remove permissions for your connector.
- Tenant ID - The Microsoft Azure tenant ID for an app from the Overview section.
Note:
- If you use a multi-tenant application, keep the default value 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.
- Environment - Optionally, select an environment from the dropdown list:
- Office 365 (default)
- US Government L4 - Public Sector domain
- US Government L5 - Public Sector domain
- China Select Office 365 (default) for all regions, and only switch to Government or China for cloud deployments.
Note:For more details on environments, check Microsoft Graph and Graph Explorer service root endpoints.
- Select Connect.
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, see the Microsoft documentation.
This issue affects not only the OneDrive & SharePoint connector, but all Microsoft Graph-based connectors, such as Outlook or Teams.
- Overview
- Admin consent
- Client Certificate Authentication
- Scopes
- Adding the Microsoft OneDrive and SharePoint connection
- OAuth 2.0 Authorization code
- Scopes
- Adding the Microsoft OneDrive and SharePoint connection
- Refresh tokens for OAuth applications
- OAuth 2.0 Client credentials
- Scopes
- Adding the Microsoft OneDrive and SharePoint connection
- Bring your own OAuth 2.0 app
- Overview
- Scopes
- Adding the Microsoft OneDrive and SharePoint connection
- Refresh tokens for OAuth applications