Cisco AMP and OSC Outlook AddIn

Summary

Any workaround for Outlook AddIn when ScriptControl (wshom.ocx) is enabled?

Content

Hi, we have Cisco AMP installed, and with increased frequency of cyberincidences our policy applies the ScriptControl function which blocks some DLLs, of which the wshom.ocx is one. As you may know, wshom.ocx and Powershell is utilised by the OSC Outlook Add-In for its operations. Thus our Outlook AddIn gets dropped at the cause of enterprise security.

The standard solution for this predicament is of course to shift Outlook from its desktop version to the web version i.e. Microsoft365.

Wondering if you have faced this or similar situation in your organisation and if there are any workarounds that you may know of. (short of moving to M365). Workarounds at OSC, at AddIn, at Outlook, at Powershell, at Windows, at Cisco AMP...