How to use Auth 2.0 for Send Exchange Mail Message for unattended robots?


In our company we are using Send Exchange Mail, Get Exchange Mail using basic authentication as of now.

i.e. Authentication Type = UserNameAndPassword

And the server url used is :

Microsoft is disabling basic authentication from October 1st so we have to move all exchange ews email activity to Auth 2.0.

Does anyone has any idea how to do? or what all is required to convert Exchange email to Auth 2.0?

There is authentication type called : “Interactive” which is 2.0 but when using this, there is a pop-up in the robot one time asking for username and password. We are not able to know if this is due to some setting in the UiPath or due to admin related username privilege’s issue.

Has anyone used Mail Exchange Send/Get for unattended robots for Auth 2.0? If yes can you please let me know what steps to be taken from uipath or IT admin for the privilege’s.

Hey @Lakshmi_Holla

Kindly try the O365 activities.


Yes we could. We need lot of permissions from admin to get application certificate and enabling them for REST API’s.

And we would have to convert nearly 40 robots in prod to this. So was wondering with the same Exchange mail activity if we could migrate to Auth 2.0.

Note: We use Get, Send,Move,Delete from exchange.

Why not just use Send SMTP Mail Message? Simpler, more reliable.

Hey @Lakshmi_Holla

Understood the pain ahead.

Did you check the updated latest package which has two more authentication options to use OAuth with same Exchange activity ? which supports Auth2.0


I don’t have answer for this. I joined recently and there are already bots built with Exchange send/get email activities.

Which one you mean?

Interactive? – we tried this but we are getting pop-up to input credential one time in each machine its deployed

WindowsIntegrated – Cannot use this as windows username and actually mail details do not match.

Yep, interactive sign in and for the first time we need to manually handle.

Hey Lakshmi,

Here’s what UiPath Recommends - Exchange Online - Prepare For Basic Authentication Deprecation

Hope it helps!

We went ahead with o365 activities with Application id and secret id