Microsoft 365 Scope

Help Activities
, ,
1

Hi Experts

I’ve built a library that uses the UiPath.MicrosoftOffice365 activities, including the Office365ApplicationScope. During a recent update, I noticed that the Microsoft 365 Application Scope has been moved to the Classic category. According to UiPath’s documentation, the Classic Microsoft 365 activities are now in maintenance mode, and no new features will be added. The recommended path is to switch to the Integration Service connection‑based activities:

Activities - Classic activities

I’m trying to understand how to migrate to the new Integration Service connection model.

I have already created a Microsoft OneDrive & SharePoint connection in Integration Service using OAuth 2.0 Client Credentials, reusing the same Client ID and Client Secret I previously used with the Application Scope. However, the connection setup also requires selecting a user account for impersonation.

My questions are:

  • Does the selected user account always act as the impersonated identity for all actions performed by the connection? (Based on what I understand, yes—but I want to confirm.)
  • I have multiple service accounts used to run automations. Should each user have its own separate Integration Service connection?
  • If multiple users can run the same process, how do I dynamically choose which connection to use at runtime?
  • Is it possible to reference the connection as a variable, or is a connection “hardcoded” into the workflow?
2

I think best way is to create a MS Azure Resource group under the subscription that you have for MS graph and add all users under that resource group(with same role) so that each account has similar accesses.
each user can then create a separate connection on DEV.

One the solution is promoted to the next environment, the Dev connection reference will also be copied to next environment but, you can edit the connection reference with another non-dev ID.
This way you can use the same connection reference across tenants but change with which account that resource need to be accessed.

during unattended runs, you can setup project requirements on processes or update the connection reference with your unattended bot ID.

image
image374×531 16.4 KB

so, yes, connection reference can also be passed as an argument(i did it for cloud solution), i think same should work for solutions built with studio desktop.

SG.