Just FYI:
This morning Outlook did force me again to the “New” Outlook.
(Message is in Dutch but translated: “The new version of Outlook for Mac is available. The new version will be launched the next time Outlook is started”).
When I just relaunched Outlook, I did have indeed the “New” version. But the switch to the old version is still available. But for how long? I see that they are really pushing the New version.
In the same boat. Seems MS are getting progressively stronger in their “persuasion” of us moving to the new version (most recently, yesterday). Upon a forced restart, Outlook was now “new”.
Fortunately, the switch in the menu option is still there, and yes – when being asked why I was leaving, I selected “Applescript” as the reason… Hopefully, there are enough of us to get the message across to them.
Curious though:
If we are forced, and Applescript is still not active, what options should we still have? I presume the “drag and drop” onto the DT icon will still work, correct? Not even sure if that is a thing – since I have always relied on AS? Or would all functionality to import into DT3 be broken (apart from printing >> PDF >> import)?
Yes, drag and drop should still work though you may have to drag and drop to the desktop, then to DEVONthink.
Hmm. Was this problem fixed now? Meaning does DevonTHINK work with the ‘new’ Outlook?
No. This is something Microsoft has to address. We cannot do anything about the fundamental change they made.
I am not sure if Microsoft will have any Bussiness reason to do the mentioned change.
Assuming that not, my take-away is that in future the DEVONTHINK import from Outlook will not be available anymore as the legacy compatibility will be obsoleted/desupported/removed by Microsoft.
Note: Just blaming Microsoft which is a much larger software company, does not solve Clients problem 
It is not “blaming Microsoft”. It is stating the realities of the situation and the avenue for addressing it lies with Microsoft.
When you disable the New Outlook, you are presented with a feedback panel with choices and a comment section. AppleScript is one of those built-in choices, acknowledging this is a reason people may abandon the new interface. We suggest people disable the New Outlook and send feedback they want AppleScript restored.
Apologies for reviving this, what — 2 years later — but think my days of running the legacy version are starting to run out… Seems that the various MS Office applications are starting to hang/freeze far more frequently, and I suspect it is related to Outlook still operating as the deprecated version.
Can anyone who has moved over to the “new” Outlook, kindly confirm whether the import feature is still broken, and if drag and drop (or any alternatives) work?
[To be clear, I realise this is a MS issue / not something Devonthink can do anything about — just want to check the lie of the land, before being forced to move across.]
Not trying to revive anything. I have never had need to use Applescript in conjunction with Outlook, so I was new to the dysfunction vis a vis DT3 and importing from Outlook for, as here, archival reasons. It turns out, as far as I (a lowly single licensee of Office 365 for Mac), this problem has not yet been rectified by MS. The “new” Outlook still does not support Applescript or Tasks from the world of Mac. If a user selects from the Outlook “Help” menu the choice of “Revert to Legacy” a mini-survey window opens, apparently lamenting your decision to slip backwards and asking you to comment as to why, and also to select either or both of two choices for their developers to concentrate on in future (with no specific target in view) to adapt to the architecture of the new protocol. And these choices are “Tasks” and “Scripts.” Selecting the button “Done” summarily closes Outlook and reopens the Legacy version with, of course, no accounts yet registered for retrieval of email. Fortunately, choosing “New Outlook” from the Outlook menu immediately reverts to New Outloook from your error-laden recidivist behavior.
Unfortunately, correct. With regards to any anticipated fix from them, we left the “guardedly hopeful” phase quite some time ago.
Thank you for this — and yes, I too have selected the “scripts” option each time Outlook pulled a sneaky switch to the .newVersion, and I had to revert.
Going to be an annoying day when they quash the legacy version — but until then, happy to have it around.