Custom Delegated App being ignored — UiPath always uses UiPathStudioO365App for SharePoint access

Gustavo_Stamm
Wed, 16 Jul 2025 14:56:51 +0000
Activities

Hi everyone,

I’m trying to access SharePoint from UiPath using Microsoft Graph API with Delegated permissions, and specifically using the Sites.Selected scope (since the security team in the company I work for wasn’t comfortable with granting Sites.ReadWrite.All). I registered a custom Azure AD app, assigned the necessary delegated permissions, and granted admin consent.

However, even after configuring the Microsoft 365 Scope in UiPath to use my custom App ID and Tenant ID, the connection always ends up using the UiPathStudioO365App (as shown in the Enterprise Applications), not the custom app I registered.

Here’s what I’ve done:

Registered a custom App in Azure AD

Assigned Delegated permissions including Sites.Selected, User.Read, etc.

Granted Admin consent to the app

Used the Microsoft 365 Scope in UiPath (latest version) and providing the App ID and Tenant ID

Executing the automation using a user account that has access to the SharePoint folder

Still, execution routes through UiPathStudioO365App

Questions:

Is Sites.Selected supported when using Delegated authentication in UiPath?

Why does UiPath continue to use the default UiPathStudioO365App, even when a custom app is configured in the scope?

Is there a way to explicitly force the use of my registered app when using delegated auth?

Any guidance or clarification would be greatly appreciated.

Thanks!

8 posts - 2 participants