App Integration 365 Activities Prompting Login Despite ApplicationIdAndSecret?

Has anyone worked with the latest App Integration 365 activities (not classic)?

I have it working in the our environment with my email along with the existing Azure app with API permissions for emails using the app ID, secret ID, and tenant.

The only change I had to make in the Azure app was to add a callback URL that UiPath provides, which doesn’t affect the existing classic activities using the same Azure app with API permissions.

Issue: Integration setup in the cloud still asks me to log in via the MS login UI interface to complete the integration and get connected. This doesn’t happen with classic activities. We use the “ApplicationIdAndSecret” authentication method to avoid any UI login interface so our BOT service accounts can perform tasks via API calls as intended.

Has anyone faced this issue or have any clues as to why it’s still asking for the MS login? When I use the classic activities with the same azure app tokens , there is no login—just a simple Graph API call with tokens provided.

The difference is that we don’t use the tokens in UiPath Studio/code but rather in the Cloud Orchestrator. There, we set up the integration, and Studio can see the integrated app, which shows up in a dropdown like any ML skills, for example.