Add-ins in the new Outlook for Windows
The new Outlook for Windows brings a more consistent and robust experience with rapid access to new features. It also has some significant changes in how add-ins are handled. The article below outlines our approach and what admins need to know about add-ins in the new Outlook for Windows.
Teams meeting Add-In not displaying in Outlook
Hi, I recently detected problem on one of our workstations where both Teams and Outlook are installed and the Teams Meeting Add-In in the Outlook does not work. There are no Add-In buttons shown in Outlook's Calendar view and user is unable to create Teams meeting invitation. In the mail view however, online status of users in Teams is displayed and it is also possible to use the "IM" icon to initiate direct chat with the user. All Workstations are MS Office 2013 Std or Pro, connected to on-premise exchange server. All users have the same license added for Teams. The affected station had the add-in fully working until few days back when this has stopped working. I have tried the follwoign so far Roll back all recent updates Unistall / reinstall Teams Create new "test" user profile and login on this workstation. Checked .NET 4.8 and WebView2 are installed. Run .NET repair tool, Run Repair on WebView2 Create new Outlook profile Troubleshoot running MS SARA as per https://support.microsoft.com/en-gb/office/troubleshoot-the-teams-meeting-add-in-in-outlook-for-windows-d3f8819e-7993-43c7-a124-02b336273779 (It does re-register Add-In's DLL) Run repair on MS Office Uninstall and installed Office again All to no avail. The Add-in is loaded fine. The weird thing is, that ad-in seem to create blank "No label" entries in the Outlooks Calendar view ribbon. No menu is actually shown, perhaps as the group itself shwos No label, but these are visible when ribbon is customised. Creating custom group and adding those No label menu items in there however it makes these menu entries visible in the Ribbon and confirms these are indeed Add-in's entries when hovering mouse over. I'm at the end with ideas as to why this could be happening and what might possibly be causing Add-in not to work properly. woudl be grateful for your suggestions and ideas about this. Thansk and regards
Certificate issue from https://uci.cdn.office.net
Hi, One of the users of a Excel Js Add-in that I've recently had published to AppSource (Copy as List) has reported getting an Anti-Virus popup every time he starts Excel. From Avast anti-virus. The message is: Connection to this website is not secure. Avast has blocked access to https://uci.cdn.office.net/ because one of the issuers of the server certificate has expired. Certificate: cdn.uci.officeapps.live.com Issuer: Microsoft Azure ECC TLS Issuing CA 01 Indeed, if I try to browse to that URL in Chrome, I get an error: "This server could not prove that it is uci.cdn.office.net; its security certificate expired in the last day. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Friday 28 June 2024. Does that look right? If not, you should correct your system's clock and then refresh this page." Does anyone know what this is? Is it related to my add-in? How do I fix it? What advice do I give to my user? Thanks
Outlook - Integrated Apps (Admin-Managed) - Intermittently Appearing/Disappearing on PCs
In our office we have several integrated add-ins that our Microsoft 365 Global Admin assigns 'everyone in our organization' to Outlook. Examples: Zoom, Microsoft Viva, Since Mid July around when we received the (v2205) updates to Microsoft Office we began experiencing issues with these plugins not loading. Even when checking their settings within Outlook it shows me as having no apps assigned under admin-managed despite being able to log into the Outlook Web Mail service and see the very same plugins there. Outlook (V2205 - Enterprise Monthly Update Channel) Outlook for the Web I'm trying to identify if this is something that was introduced as part of the office update or some other security setting that is beginning to block these from loading. I should advise that the issue is intermittent for our users. Typically users will have to either close/relaunch Outlook when it goes missing. I've tried some local troubleshooting with certain machines. Erasing their Outlook profile along with their OST files and the plugins did load until the next day when they disappeared again. Needing some advise on what could be causing the add-ins to intermittently go away and come back.
Outlook app web add-ins not working when WIP enabled
Hi, I'm using the new Dynamics 365 app for Outlook and it works fine on a Windows 10 device that is not protected by MS Intune's Windows Information Protection / app protection. It seems like all Outlook web add-ins don't load (COM add-ins work fine). I have also opened a case with MS Intune support, but it seems like there is no option to add web add-ins as protected or exempted apps, so that it could work with WIP. This is a big concern as currently I need to either reduce our security by removing WIP protection from Outlook or not have the Dynamics 365 app for Outlook / any web add-in for that matter. Anybody have any ideas? Thanks, Georg
AD Connect with an existing O365 Tenant
we're about to enable AD Connect for an active Office 365 tenant and need some clarifications. The Tenant is hosting O365 users with exchange online for the organization mail domain company.org but at the moment is disconnected from the On-Prem AD. So all the users have been defined on the tenant with smtp email address as Email address removed. No Exchange Server is present onprem. The question is about Soft Merge and exchange management after the AD Connect is installed. - Am I correct that simply having the logon account UPN been equal to the Tenant's username will be enough to "match" the users and have them synchronized by AD as master ? - What happens to exchange online mailboxes ? Will there be any impact ? As far as I know when the users are "managed" by AD an on-prem exchange server should be present to manage the "email" properties. thanks SC
Strange Microsoft Add-In XML Error
Hi all, I'm running into a strange Add-In issue specific only to Native Outlook running on Windows version 1903. Our Add-In works for Native Outlook running on Windows versions later than 1903 just fine. The problem is that when you open our web Add-In in Native Outlook, you should be able to click a div which triggers a network request and then changes the state of the application in React. The actual behavior is that no network request is triggered and the state is not changed. Again, this behavior works fine on Windows 10 versions later than 1903. I've tried logging the behavior using Microsoft Edge's DevTools, but the only error I see is `XML5632: Only one root element is allowed.` at index.html (1,1). This is the only output from the Add-In that I can see-- none of my console logs actually show up in the console. My guess is that perhaps the JavaScript rendering engine responsible for running web-based Microsoft Add-Ins on native Outlook for Windows version 1903 is not Chromium-based, thus a bug in how the JavaScript rendering engine (pre-Chromium Edge?) interprets the XML and/or JS, but again that's just a guess. In any case, I would be grateful if anyone that has run into this issue before has any ideas, suggestions, fixes, or workarounds because at this point I am totally stuck.System.InvalidCastException: The COM object of the type “Outlook.ApplicationClass” cannot be convert
Hello everyone, We have an Outlook addon that communicates with our application. Our application used to be 32 bit. However, we changed it to 64 bit. We use the Microsoft.Office.Interop.Outlook DLL to create emails, appointments and so on. Recently we have been having problems with creating objects and unfortunately we do not know what exactly the problem is. We always get an exception like this: System.InvalidCastException: Das COM-Objekt des Typs "Outlook.ApplicationClass" kann nicht in den Schnittstellentyp "Outlook._Application" umgewandelt werden. Dieser Vorgang konnte nicht durchgeführt werden, da der QueryInterface-Aufruf an die COM-Komponente für die Schnittstelle mit der IID "{00063001-0000-0000-C000-000000000046}" aufgrund des folgenden Fehlers nicht durchgeführt werden konnte: Element nicht gefunden. (Ausnahme von HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)). bei System.StubHelpers.StubHelpers.GetCOMIPFromRCW(Object objSrc, IntPtr pCPCMD, IntPtr& ppTarget, Boolean& pfNeedsRelease) bei Outlook.ApplicationClass.GetNamespace(String Type) or System.InvalidCastException: Das COM-Objekt des Typs "Microsoft.Office.Interop.Outlook.ApplicationClass" kann nicht in den Schnittstellentyp "Microsoft.Office.Interop.Outlook._Application" umgewandelt werden. Dieser Vorgang konnte nicht durchgeführt werden, da der QueryInterface-Aufruf an die COM-Komponente für die Schnittstelle mit der IID "{00063001-0000-0000-C000-000000000046}" aufgrund des folgenden Fehlers nicht durchgeführt werden konnte: Fehler beim Laden der Typbibliothek/DLL. (Ausnahme von HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). bei System.StubHelpers.StubHelpers.GetCOMIPFromRCW(Object objSrc, IntPtr pCPCMD, IntPtr& ppTarget, Boolean& pfNeedsRelease) bei Microsoft.Office.Interop.Outlook.ApplicationClass.get_Session() The only solutions we found online were to repair Office, which we and our customers did. Unfortunately, it only works for a few days or weeks and then the problem reappears. We tried to reproduce the problem with a powershell script and we could. This is the script: $Outlook = New-Object -ComObject Outlook.Application $Mail = $Outlook.CreateItem(0) # 0 steht für MailItem $Mail.Subject = "Test E-Mail von PowerShell" $Mail.Body = "Dies ist eine Test-E-Mail, die mit PowerShell erstellt wurde." $Mail.Display() Write-Host "Das E-Mail-Fenster wurde angezeigt." [System.Runtime.Interopservices.Marshal]::ReleaseComObject($Mail) | Out-Null [System.Runtime.Interopservices.Marshal]::ReleaseComObject($Outlook) | Out-Null What is the problem? Could the problem be related to Windows group policies? If so, which ones? We have a lot of customers that have this problem so we need help asp. Thanks and best regards
