Fix the Teams Meeting Addin for Outlook
There are two things that are critically broken:
The Teams Meeting Addin for Outlook never works out of the box. Even on a fresh installation of Office 365 ProPlus and Teams, the Teams Meeting addin never loads. We have to manually go to each user's computer and close Teams and Outlook and then manually register the Microsoft.Teams.AddinLoader.dll, then start Teams, then Outlook to get it to work. And then the next time Teams updates (which is frequently), the Addin breaks and disappears.
The Teams Meeting Addin for Outlook does not work if we use federated authentication. All our users MFA through a federated authentication provider, so, even if we get the Teams Meeting Addin loaded, it doesn't work.
These issues are complete SHOWSTOPPERS for our migration from Skype for Business to Teams. A migration being forced upon us by Microsoft.
Gunter Königsmann commented
The problem seems to arise on a big percentage of boxes with 32-bit outlook...
20 Clients, none of them had the outlook plug-in by default installed after teams has been installed. I had to add it manually with the help of SaRa, and practically on every single machine. Just to see that out of 20 pcs, the plug-in was not really working on 18 of them: Error scheduling meeting.
Seriously Microsoft ???
And then I get a totally unhelpful error-message.
That makes me even more mad. What a double fail.
Try explaining to your boss why its not working and why you wasted plenty of hours trying to get it to work.
But here is the fun-fact, which is more important to all others maybe:
Only two machines have been working with the plug-in, and guess what, those two clients were running Win 7 (+ Office 2013).
All the others had Win10 and various combinations of Office H&B 2013, 2016 and 2019 (32 and 64bit). Exchange on-premise/AD.
Peter Guilbert commented
This is a major concern for our company who were going to switch from Slack/GoToMeeting to Teams. We simply can't recommend to the Board that this is a sensible approach at this time.
Christopher Holmes commented
it looks like the Teams not showing Create new meeting has been fixed by Microsoft. This still does not resolve the chaotic plugin not working at all in Microsoft Outlook. I have to give credit, when it goes belly up, it really is just done. I have registered, unregistered and this thing is still just not having it. Please for the love of Support people everywhere, just make this thing as robust as Skype. I mean IT WORKED!
It would really help our company to get this fixed!
Please fix this add-in, thanks!
Christopher Holmes commented
We are having this issue with 90% of our environment. If office x64 is installed it seems to be more of an issue than Office x86. Our users will see the plugin loaded in Outlook but unable to create new meetings. The plugin only works for joining Microsoft Teams meetings. I even have a few users where it works on one computer but does not work on another.
We fixed this problem (for couple of users in RDS environment) by creating a new profile. Then after logon first start Teams (takes a while) and then start outlook. Addin is now active.
Issue is still active. Sysprepped image, fresh installation of Office 365 (E3 license). Very annoying, high impact on support.
Oscar Escano commented
Two Microsoft products that do NOTh and shake well. My outlook 365 still do NOT have a Teams add-in
Paul Barber commented
I have two users that this is happening to and it seems to happen after an Office update. One thing I have noticed is that for the two users it has happened to, their Teams meeting policy was changed from Global (Org-wide default) to RestrictedAnonymousAccess. Now even though I changed the policy, the AddIn still does not show, but there seems to be something that is messing with the meeting policy and breaking the connection.
Paul Andres Pedroza Martinez commented
No fix yet?
Jahangir Shah commented
What is the permanent solution to this?
is there any solution for this
Rick Ledford commented
Has anyone seen/heard of a fix from Microsoft in regards to this?
I am noticing that B Davis shared this idea in October 2019, and people are still seeing issue with this.
We have x64 installations of Office 365 and Office 2016. Both have worked great with Teams x64 for months and just recently, a random sample of our installations are starting to have this problem:
The Teams addin for Outlook disappears one day.
There are the failed registrations in both the squirrelsetup.log and the teams log.
Some of the Team addin versions are 20031.2 and some are 20077.4.
We've been able to fix SOME of them by registering the 20031.2 using:
C:\WINDOWS\SysWOW64\regsvr32.exe /s /n /i:user "%userprofile%\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20031.2\x86\Microsoft.Teams.AddinLoader.dll"
C:\WINDOWS\System32\regsvr32.exe /s /n /i:user "%userprofile%\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20031.2\x64\Microsoft.Teams.AddinLoader.dll"
But some just won't come back.
We have several tickets on several avenues open with Microsoft and I can't even explain the poor response.
Anyone here solve it yet? Anyone know how to get Microsoft to react?
Like Markwell, the problem is spreading throughout our org with no rhyme or reason.
Peter Markwell commented
We also are using Office 2016 x64. Teams is separately installed per user. Add in fails to register. The teams add-in insatl llog shows.
Failed on call Regsvr in wow mode Squirrel.ComRegistrationException
2020-05-05-01:44:40.760 PM Addin directory exists. Copy was successful
2020-05-05-01:44:40.762 PM COM registration. Regsvr Path: C:\WINDOWS\system32\regsvr32.exe, Arguments: /s /n /i:user "C:\Users\robertsr\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20031.2\x64\Microsoft.Teams.AddinLoader.dll"
2020-05-05-01:44:41.272 PM Failed on call Regsvr in wow mode Squirrel.ComRegistrationException
The problem seems to be spreading across our organisation through people who formerly had working Teams add-in. Started being reported since 22/April/2020 auto update was deployed.
Our call logged with support a few days ago is't getting much traction.
we use all in 64 Bits versions. The weird thing is that for it is working for +/-50% of the users (new created accounts, and old migated from the past). I don't see a patern in the who are and who not be able to get the pluginn started
We have a Citrix farm and all working with the same publish windows desktop.
Andrew McNaughton commented
This might be simpler than you think, although Microsoft should make their installer smarter.
If you chose to install the 64-bit version of Teams BUT your copy of Outlook is 32-bit then the Add-in won’t load because it’s 64-bit. Try registering the 32-bit version and you’ll find it works. Or upgrade to 64-bit Outlook.
The reverse would be true if your Outlook is 64-bit but you installed Teams 32-bit.
Lazar Tomovski commented
Same here .. fresh install of office 365
2020-04-30-01:41:08.473 ValidateAddinInstallationInternal Entry : HKEY_CLASSES_ROOT C:\Users\user\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20077.4\x64\Microsoft.Teams.AddinLoader.dll
2020-04-30-01:41:08.474 Failed to validate addin installation System.FormatException
2020-04-30-01:41:08.475 Failed to install the Teams meeting add-inCOM registration failed. Regsvr Path: C:\Windows\system32\regsvr32.exe, Arguments: /s /n /i:user "C:\Users\user\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.20077.4\x64\Microsoft.Teams.AddinLoader.dll", ErrorCode: 3, % Message:
we have the same problem within our RDP/citrix farm
Can’t figure out what causes the problem, it fails on 50% new and/or old users accounts