[Query] Office365 API for AutoIT?

[MarkIT]

Hi guys,

Been searching the forum but would need to ask for your confirmation if we have a UDF that can be used to send/receive emails by interacting with Office 365 APIs.

Just like the one on this link:

https://www.codeguru.com/csharp/csharp/cs_internet/mail/send-e-mail-using-office-365-apis-and-exchange-web-services.html

With similar implementation done on .NET:

https://www.emailarchitect.net/eagetmail/ex/c/9.aspx

The purpose is that we are working on a project where client requires that our Automation that sorts  emails gets triggered using Task Scheduler activities. The plan is to run the automation on the backend without using the Outlook UI and only connects to the Office365 platform via API? 

Edited October 30, 2020 by MarkIT

[Confuzzled]

I'm absolutely shocked you didn't stumble across across the OutlookEX UDF in your search in these forums! Probably does EXACTLY what you are looking for.

All the three options you have noted will be accessing the mail environment as objects. Is it worth mixing your development code between various languages and the support/maintenance overhead and confusion that entails?

Some good reading at https://www.autoitscript.com/wiki/OutlookEX_UDF_-_General

Edited October 30, 2020 by Confuzzled

[Danp2]

Using the Outlook UDF isn't the same as directly calling the platform APIs AFAIK.

[Confuzzled]

For performance and maintenance reasons, interspersing an AutoIT layer between code and the mail environment is probably going to end in some extra work they do not need.

A scripting platform compared to calling APIs direct? Naaah. Just one more level to debug. Whip out the Microsoft Tools and start coding!

..Horses for courses..

[MarkIT]

On 10/31/2020 at 5:11 AM, Confuzzled said:

I'm absolutely shocked you didn't stumble across across the OutlookEX UDF in your search in these forums! Probably does EXACTLY what you are looking for.

All the three options you have noted will be accessing the mail environment as objects. Is it worth mixing your development code between various languages and the support/maintenance overhead and confusion that entails?

Some good reading at https://www.autoitscript.com/wiki/OutlookEX_UDF_-_General

Hi Confuzzled, 

Thanks! We have already implemented OutlookEX UDF and functionalities for the project. Automation is already running perfectly for 1 year. Only issue now is that client doesnt want interactive login on the servers for the automation to work. They want services to run on backend and perform the process. They wanted now to access the O365 Exchange directly using APIs instead of an Outlook UI.

Thanks!

[water]

BTW: The OutlookEX UDF does not automate the UI (User Interace) of Outlook but uses the Microsoft API (COM) to access incoming mails etc.

I do not think it is a good idea to have such automation run on the server. The main purpose of an Exchange server is to provide a service for many, many users. it should not be overcharged with other tasks. If the automation tasksbrings the server to a halt (eats up all CPU, memory or disk space etc.) all users are affected.
If this happens on a client automating Outlok then just one user is affected.

This seems to be a good reading what MS intends: https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ba-p/608055

Graph overview: https://docs.microsoft.com/en-us/graph/overview?view=graph-rest-1.0

Edited November 3, 2020 by water

[MarkIT]

1 hour ago, water said:

BTW: The OutlookEX UDF does not automate the UI (User Interace) of Outlook but uses the Microsoft API (COM) to access incoming mails etc.

I do not think it is a good idea to have such automation run on the server. The main purpose of an Exchange server is to provide a service for many, many users. it should not be overcharged with other tasks. If the automation tasksbrings the server to a halt (eats up all CPU, memory or disk space etc.) all users are affected.
If this happens on a client automating Outlok then just one user is affected.

This seems to be a good reading what MS intends: https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ba-p/608055

Graph overview: https://docs.microsoft.com/en-us/graph/overview?view=graph-rest-1.0

Thanks Water! Will check on these

[Melba23]

MarkIT,

When you reply in future, please use the "Reply to this topic" button at the top of the thread or the "Reply to this topic" editor at the bottom rather than the "Quote" button - responders know what they wrote and it just pads the thread unnecessarily. Thanks in advance for your cooperation.

M23

[MarkIT]

Apologies and thanks Melba23