This seems to mean you are running an Insider Fast (aka “beta”) version of Outlook.
Compare: Outlook for Mac - Release notes for Insider Fast builds - Office Support.
Two of us here at CogSci Apps tested with Outlook version: 16.16 which is the latest official (non-beta) build from MS. It works fine. And our AppleScript test yields a different (and correct) response.
Perhaps Microsoft’s beta builds use a different bundle ID and maybe use a different app name. To verify, would you please run the following from the Terminal app, which normally lives in the
[/Applictions/Utilities folder](hook://file/V3vwC2mqk?p=Ly9BcHBsaWNhdGlvbnM=&n=Utilities) :
osascript -e 'id of app "Outlook"'
That command should return com.microsoft.Outlook . That is the bundle ID of the app. If not, that would explain the Hook issue. We could easily remedy that.
If that is not the issue, it suggests a bug with MS Outlook. (The AppleScript response you suggests a bug on the Outlook side.) Here are some notes on that: Join | Office Insiders
to quote them:
Best for Insiders who want to use the very earliest builds to identify issues and provide feedback about new features still in development. Insider is ideal for those who don’t mind the bit of risk involved in using unsupported builds.
If there’s a bug with their beta, it would be helpful for Outlook Insider Fast users, and CogSci Apps, to report the problem to MicroSoft. But first things first.