Issue with Scopes in Office365 Scope connection

[cacafundi (J.G.)]

Hi all,

I have a flow that connect to office365 account, and make some operations in sharepoint.

But i have a problem, the connection of office365 scope have by default Groups.Read.All and Groups.Read.All, but the admin of the tenant doesnt allow to normal users this permissions by enterprise security directives. I suppose that this is a pain in the neck for many users in my situation, because, not all users can have this type of scopes:

Due this, i ask to you if there is possible to do the connection with specific scopes, removing or adding the necessary scopes.

If this is not posible to reach with actual version of microsoft365 scope, i suggest an improvement, that allows select the scopes in the connection, avoiding this types of issues.

Thanks & BR.

[Anil_G (Anil Gorthi)]

@cacafundi

In the new release you can create your own app with a different set of scopes…as of now this is in community version

Announcing the General Availability of Authentication Enhancements in Integration Service

We’re excited to announce the general availability of Authentication enhancements in Integration Service! These new enhancements include Multi-Authentication and Bring your own OAuth 2.0 app (BYOA). Multi-Authentication: You can configure Multi-Authentication options for supported connectors in Integration Service. This allows users to select alternate methods of authenticating prior to creating a connection. Current supported connectors: [image] To create a connection using Multi-Authent…

Cheers

[cacafundi (J.G.)]

Hi Anil,

thanks for your quick response!

First , i have to use Office365 activities and above permissions are not allowed for users (like me)

This is the part of the workflow that fails:

This is the cause:

could you help me to remove or avoid this scopes ?

Thanks & BR

[Anil_G (Anil Gorthi)]

@cacafundi

Are you a community user ? Or enterprise…

As mentioned before For enterprise it is not released yet…for community users creating own app is released and that can be used …please check the link provided above

Cheers

[prateek.mehandiratta9 (Prateek Mehandiratta)]

Hi,

I faced similar issue couple of times only when working with OAuth application as “Custom” instead change it to OAuth Type Application as UiPath.

If you are authenticating through App registrations in Azure and running it through UiPath then you need UiPath as OAuth application: see image below(Yellow circled)

Thanks.