Office 365 Email fails with connection error

[gkocev]

Hello, 

We have the an issue with the Office 365 Email activity. Since it requires an Office 365 connection, which cannot be shared between different users, it seems that it will trigger successfully only if the user who created it executes the pipeline. 

If another user starts the pipeline, when it comes to sending the email it fails with error "Failed to load the connection. Please make sure it exists and you have the permissions to access it."

We also have a small app that triggers the pipeline with the service principal - same issue. 

Is there any way to handle such situations? 

Thanks! 

[gkocev]

Hi @v-sshirivolu ,

Excuse my ignorance, but what  UiPath Integration Service has to do with a Fabric pipeline execution and with setting up the 'Office 365 Email' activity connection? 

What I was expecting is similar behaviour to the legacy "Office 365 Outlook" activity, where we could sign in some Office 365 account and no matter who executed the pipeline an email was sent from that account.... 

Thanks! 

[v-sshirivolu · Accepted solution]

Hi @gkocev ,
In Fabric pipelines, the Office 365 Email activity works with a user based connection, which means the login/permission is linked only to the person who created that connection. So when any other user or a service principal runs the pipeline, Fabric will not allow them to use that same connection, and that’s why you see the error. The older Outlook activity behaved differently, but the new Office 365 connector does not support that shared behaviour. At the moment, Fabric doesn't have an option to share a personal connection across all users. Because of that, the only practical workaround is to create the connection using a shared mailbox or a dedicated service account that everyone has access to. Once you switch the pipeline to use this shared connection, the email step will run for any user or unattended trigger without issues. If Microsoft enables shared connections in the future, this will work like the legacy behaviour again, but for now, this is the safest and most stable approach.

[v-sshirivolu]

Hi @gkocev ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[v-sshirivolu]

Hi @gkocev ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions

[v-sshirivolu]

Hi @gkocev ,
Thanks for reaching out to Microsoft Fabric Community Forum.

To fix the Office 365 email connection issue when other users or a service principal run the workflow, the best approach is to create a shared connection in UiPath Integration Service using OAuth 2.0 Client Credentials. This means you set up an Azure App Registration (Client ID + Secret) with Microsoft Graph Mail.Send application permission. After that, put this connection inside a shared Orchestrator folder and give View/Execute access to all required users, robot accounts, and the service principal. Finally, update your workflow to use this shared connection instead of a personal user connection. Once this setup is done, the email activity will run smoothly for anyone ,whether a different user or an unattended bot without showing the 'Failed to load the connection' error.
Thank you.