Forum Discussion
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
5 Replies
312Pinky I would work through the steps in Resolve issues with Teams Meeting add-in for Outlook - Microsoft Teams | Microsoft Learn
Also though as I'm sure you are aware Office 2013 is out of all support and extension since April this year, it's quite possible that recent Teams builds may well have not been tested against that client. What's the plan to upgrade back to a supported version?
- Hello Pinky,
welcome to the Microsoft community, My name is Yakubu Suleman I'll be happy to help you today;
I understand that Teams meeting Addin is not displaying in outlook and I can see you have carried out several steps aside verifying the registry key settings.
Kindly follow the steps below to check the registry settings.
Warning
Follow this section's steps carefully. Incorrect registry entries can cause serious system issues. As a precaution, back up the registry for restoration.
Check the load behavior of the add-in:
Open RegEdit.exe.
Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect.
Check the value of LoadBehavior. It should be set to 3.
If LoadBehavior has a value other than 3, change it to 3 and restart Outlook.
If the add-in still doesn't appear, go to step 2.
Check whether the Configure Outlook object model prompt when reading address information policy setting is configured:
Open RegEdit.exe.
Navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Security. If you applied the policy settings by using Cloud Policy service, navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Cloud\Office\16.0\Outlook\Security.
Note: Policy settings that are implemented by using Cloud Policy take precedence over policy settings that are implemented by using Group Policy on Windows.
Check for the promptoomaddressinformationaccess registry value and whether a value is set for it. If the value is 0, it indicates that the policy setting is set to the Automatically deny option. If it is, Outlook will automatically deny programmatic access requests from any program. In this situation, go to step d.
Check the Configure trusted add-ins policy setting.
If this policy setting is configured, Teams administrators can use one of the following options:
Disable or unconfigure the policy setting.
If the policy is required, make sure that Microsoft.Teams.AddinLoader.dll is in the list of trusted add-ins and that the corresponding hash value is correct. You can use the Get-FileHash cmdlet to compute the hash value of the .dll file.
Note: The Microsoft.Teams.AddinLoader.dll file that's used is automatically updated with the Teams client. Therefore, the hash value must be constantly updated to pair with the .dll file.
I believe this help?- Hello Suleman,
thank you for your suggestion.
There is already correct value 3 in the LoadBehavior key of HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect already.
My Office is 2013 and in HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\Security I only have two subkeys InitEncrypt and InitSign, there is no "promptoomaddressinformationaccess" there nor anywhere else in affected machine's registry.
No change therefore, the Teams Meeting Add-in appears not to load properly and doesn't interact with Outlook es expected 😞- Hello 312pinky,
thank you very much for your email response however since you are not able to see the "promptoomaddressinformationaccess" I will advise you raise a support ticket with Microsoft for further assistance.
Regards.
