07-05-24 02:42 PM
Hello All,
Please be advised that Microsoft's newest Outlook client DOES NOT support COM interop. What that means is the Outlook VBO will not work with this newer Outlook client. See below reference from Microsoft regarding supported features with the new Outlook client software.
Getting started with the new Outlook for Windows
The solution, at the moment, is to not use Microsoft's latest Outlook client on runtime resources. Alternatively, you could consider using the newer Microsoft 365 - Outlook VBO which leverages Microsoft's Graph API (RESTful web service) instead of COM interop and the Outlook client software.
Cheers,
Eric
22-07-24 04:20 PM
That's interesting since Microsoft has stated there's no COM API capability in the new client, and our previous tests showed exactly that. I wonder if they've made a recent change due to feedback?
Cheers,
Eric
05-08-24 03:26 PM
Hi @ewilson , is there any update on this? are they made any change to support com API ?
Thanks,
Arghya
05-08-24 04:46 PM
Hello @arghya.b ,
Unfortunately, this still seems to be an issue. There's been no change communicated by Microsoft as to the removal of the COM API from the new Outlook client. Further, our tests with the new client continue to produce ActiveX component exceptions when trying to make any requests against what was the COM API. You'll see the following exception with the new Outlook client:
You may also see an exception like this:
Without reviewing one of the machines @Neel1 uses, I can't explain how this is working in their environment.
Cheers,
Eric