SharePoint Integration Services - App permissions sites.selected - nothing visible

Hello, Currently I try to use the SharePoint Integration from Integration Services within Cloud Orchestrator. The goal is to connect to a SharePoint Online site document library.
For the setup I have an Azure App configured with “sites.selected” permissions for Microsoft Graph. Furthermore, the target SharePoint site is assigned with write permissions to the Azure App. Note: I can only use app permissions, delegate permissions is not an option.

Within Integration Services I then selected authentication type “OAuth 2.0 Client credentials”. I provide the respective Client ID, Client Secret, Tenant ID from the Azure App. Environment is Office 365 default. I am not sure if field “Account” is required, however I just provided my own account mail to populate this field. After clicking on “Connect” it works and create the integration. However, when I then use respective activities (either in desktop Studio or in the web Agents studio) I don’t get any folder content when selecting the created integration. Also, I don’t get any error message pointing to any missing configuration piece.

Does anyone have a clue on whats missing in the configuration? Thanks! :slight_smile:

Hi @T800

Pls check this:

Happy Automation

Thanks for the hint. I also checked the process based on this article. I am a bit confused as in section " Approach 2: Using Application Permissions" at the end it is saying:

These are the only permissions that needs to be assigned and configured, SharePoint wise. This permission only works for Office 365 Scope authentication.

I wonder if that means application permissions cannot be used within the SharePoint/OneDrive integration option from Orchestrator Integration Services? For my use case it doesn’t help if I only can use the “Office 365 Scope authentication” as a Studio activity. I also need the SharePoint access within the Agents web studio which in my understanding only works with an integration from Integration services.

@T800

First thing the account is the account used to impersonate..means the account you provided should have access to the sharepoint

Also as impersonation is mandate app only permissions might not work.

one way to work with the agent is create rpa flows for each send email or get files etc and add them as tools to agents

cheers