Posted Wed, 19 Dec 2018 01:16:36 GMT by

Hi

Team

 

I am having issues to try open/establish an e-mail session.

My organization have the outlook in the cloud (outlook.office.com).

Please can you share the steps to get this configured.

I am getting the following error using IMAP protocol :

[New Task (21)][Main](Step 1) Email failed (Error : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

 

Thanks in advance for all support received.

Regards,

 

Nelson Cunha

 

 

 

Posted Thu, 20 Dec 2018 02:16:32 GMT by

Hi Nelson,

When using Office 365, you will want to use the EWS protocol and use outlook.office365.com for the exchange server. The username and email will be your full email address.

Posted Thu, 20 Dec 2018 02:57:59 GMT by

Hi

Justin

Thanks for your feedback.

The session is created, but when I try to send a mail or get header(s) I get the following error:

Invalid URI.

thanks

 

Nelson Cunha

Posted Thu, 20 Dec 2018 16:58:53 GMT by

Nelson,

Please remove the information in the exchange server field and as long as you have the correct email address, user name and password specified, then click on the discover button and let Automate populate the exchange server field. It may not be outlook.office365.com.

 

- Leonard 

Posted Fri, 04 Jan 2019 00:40:41 GMT by

Hi Leonard

The discover button does not work and does not return any information.

Unfortunately still with the same problem.

Hope to have more help on this point.

Thanks in advance.

Nelson Cunha

Posted Fri, 04 Jan 2019 23:52:34 GMT by

We're just starting to use Outlook in O365 with Automate, and ran into some problems as well.  In my testing, I was not able to get the auto-discover to work at all.  But using outlook.office365.com as suggested earlier did work.  However, I was not able to use an account that was federated with ADFS, I had to use a cloud-only account to be able to authenticate.  Is this a known limitation with connecting to O365?

Posted Wed, 09 Jan 2019 09:21:41 GMT by

@ David

We currently do not support single sign-on.

 

@Nelson 

we will schedule a remote session for this issue on the current open case we have with you and Carlos. 

You must be signed in to post in this forum.