New Outlook Desktop 365 Add-ins Not Showing on Secondary Mailboxes

Copper Contributor

I'm testing the New Outlook desktop version, and I have encountered an issue with add-ins. My primary inbox is Jeff@furni*******.com, and when I create a new email from this account, the signature add-ins load fine. I am using the CodeTwo 365 Signatures add-in, but it seems that the add-ins are displayed only for the primary default inbox and not for any other mailboxes. However, when I create a new email from another inbox, such as Jeff@edro*******.com, the add-in pane doesn't load, and the signatures are not imported.

 

This problem seems specific to the new Outlook desktop version. When I use the Outlook web app at https://outlook.office365.com/ or the old Outlook desktop version, the add-ins load correctly for all mailboxes.

It appears that the new Outlook desktop version only loads add-ins based on the primary mailbox. Even if I switch to another mailbox account, the add-ins do not load, unlike in the desktop and web versions where they load as expected once I choose another mailbox on the left pane and click compose email ill see the addins assigned to that mailbox on the editor pane. 

 

Now if I actually change one of the mailboxes to "Set as Primary Account" the addins will load fine but only for that mailbox. 

Jeffg635_0-1717974577047.png

 

 

Version Details:

  • New Outlook Desktop Version:

    • Microsoft Outlook Version: 1.2024.529.200 (Production)
    • Client Version: 20240531006.09
    • WebView2 Version: 125.0.2535.85
    • Session ID: bd1b8ccd-6d00-5b4b-bb4a-1307f365c0bf
  • Old Outlook Desktop Version:

    • Microsoft® Outlook® for Microsoft 365 MSO Version 2405 Build 16.0.17628.20006 64-bit

Is this a known issue, and are there any workarounds or solutions available?

2 Replies
Unfortunately, since the New Outlook for Windows is still in the preview stage, not everything works as expected. While our add-in does work for the primary account in the new Outlook, secondary mailboxes are not supported at the moment due to the current limitations of the new Outlook for Windows. For best experience, we still recommend using the classic Outlook.

This issue still exists in the production version of Outlook.

New Outlook Desktop Version:

Microsoft Outlook Version: 1.2024.903.200 (Production)
Client Version: 20240906004.17
WebView2 Version: 128.0.2739.79
Session ID: da723070-501c-4eca-b76f-b7e66ffa300f