We did recently notice the following difference in behavior between Office 365 and Office 2016 Professional when trying to connect to the Office Add-In Business Inbox. Here is a small repro that does describe the unwanted behavior:
Simplified repro:
- create an Office 365 tenant plus Exchange Online
- install Dynamics NAV 2018 on your own machine, or on Hyper-V VM or on Azure VM
- verify documentation below
- deploy Office Add-In Business Inbox (use My Mailbox and not Global Deployment)
- install one of the below Outlook releases
- start OWA and note that Office Add-In Business Inbox can be opened
- start Outlook 2016 and note that Office Add-In Business Inbox can not be opened. It will keep loading with no authentication prompt
- uninstall Outlook 2016 and install Office 365 Pro Plus
- start Outlook 366 and note that Office Add-In Business Inbox can be opened.
Documentation:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/setting-up-office-add-ins-outlook-inbox
The good news is that root cause has been identified and a fix has been created.
The issue is with a feature we introduced in the add-in a while ago that takes a dependency on the Outlook requirement set 1.5. Unfortunately, Outlook 2016 only supports up to requirement set 1.4, so the Outlook add-in is crashing when it opens. We created a fix to safely access the 1.5 methods so that the add-in still works in Outlook 2016.
This fix will be made available in one of the upcoming cumulative updates.
The Outlook Office Add-In Business Inbox works fine with the following version of Outlook:
Microsoft Outlook for Office 365 MSO (16.0.1123.20122) 32-bit
But it does not load (stuck in loading) when using the following version of Outlook:
Microsoft Outlook 2016 MSO (16.0.4738.1000) 32-bit
The issue is with a feature we introduced in the add-in a while ago that takes a dependency on the Outlook requirement set 1.5. Unfortunately, Outlook 2016 only supports up to requirement set 1.4, so the Outlook add-in is crashing when it opens. We created a fix to safely access the 1.5 methods so that the add-in still works in Outlook 2016.
This fix will be made available in one of the upcoming cumulative updates.
Thank you.