Why can't I see the Microsoft Teams Meeting add-in for Outlook?
Published Mar 22 2018 09:26 AM 2.1M Views
Microsoft

We’ve heard reports that the Microsoft Teams Meeting Add-in for Outlook on Windows does not show up for some users who have installed the desktop app.  There are several reasons why the add-in may not display that have simple remedies.  Here are some steps to help you troubleshoot this problem.

 

Install the Teams app as an administrator of the Windows computer.

One requirement for successfully installing the add-in on a Windows computer is that the user must have administrator permissions on the computer.  This is a requirement because COM add-ins to Outlook write to the Windows registry, and only administrators can modify the registry.  If the user who wants to schedule Teams meetings in Outlook is not an administrator, an administrator must install the Teams app first, and then the user can sign in and run Outlook.

 

Run Outlook in normal user mode, not as an administrator. 

When starting Outlook, do not run it with elevated permissions as this can interfere with identifying registered COM add-ins.

 

Download, install and sign into Teams and then restart Teams and Outlook, in that order. 

To ensure that the add-in is installed and loaded correctly, you may need to restart Teams and Outlook after installing.  Follow these steps:

  • Download the Teams desktop app, run it, and sign in at least once.
  • After signing into Teams, restart the app.
  • Restart Outlook (after restarting Teams).

 

Ensure that the add-in is installed and enabled.  If after all that, you still don't see the add-in, make sure that it isn't disabled for some reason.

  • In Outlook, click File and then Options.
  • Select the Add-ins tab of Outlook Options dialog box

Outlook Options, View Add-ins dialog boxOutlook Options, View Add-ins dialog box

  • Confirm that Microsoft Teams Meeting Add-in for Microsoft Office is listed in the Active Application Add-ins list
  • If the Teams Meeting Add-in is listed in the Disabled Application Add-ins list, select COM Add-ins in Manage and click Go…
  • Set the checkbox next to Microsoft Teams Meeting Add-in for Microsoft Office

Outlook Options, View Add-ins dialog boxOutlook Options, View Add-ins dialog box

  • Click OK on all dialog boxes and restart Outlook.

 

This should help fix the most common issues with the add-in.  If you continue to experience problems, please contact your support team for further assistance.

 

Thanks for using Microsoft Teams!

 

155 Comments
Silver Contributor
I wish this had been around months ago!
Iron Contributor


@Phillip Garding - that is an extensive list of hoops to jump thru for end users who are used to the ease of S4B Outlook add-in or Zoom plug-in.   Teams user adoption becomes that much more difficult when a good portion of our users do not even see the add-in for one of the reasons above.  many of them are not admins.  Has there been any thought to making the add-in install more resilient?

Microsoft

Yes, we are actively working on the add-in to improve this.

 

Phil.

Microsoft

So what if the Teams add-in still isn't there? Can I find it somewhere to download?

Does the release of Teams I'm using matter (Dev preview).

 

Thanks

Microsoft

The Outlook add-in is installed with the Teams desktop app, so there is no additional download.  The add-in is included with all versions of the Teams app.  If you are still not seeing the add-in after going through these steps, please work with your support team so we can get logs, etc. to investigate further.

 

Phil.

Brass Contributor

Sounds like yet ANOTHER reason to fix the Teams desktop app installer so that it doesn't install to AppData for every single user. Make the installation the same as the rest of the Office apps. Install to program files, machine based, so a single install pushed by an admin is all that is necessary. Until this happens Teams is a cute toy that can't be deployed in tons of enterprises.

I went through all that when the Teams add-in went missing for me, and found that it came down to which tenant I was connected to in Teams when starting Outlook: http://www.loryanstrant.com/2018/01/20/teams-quick-tip-the-case-of-the-missing-teams-meeting-add-in/

Copper Contributor

When will similar functionality be available for OWA users? We have a lot of staff using OWA and it would be nice for them to schedule Team meetings via OWA similar to how they currently can for SfB.

Copper Contributor

The add in is enabled for me (and most of my company) yet does not appear.

 

teams.PNG

@Luke Johnson did you try restarting Outlook after going back to your home tenant and Teams as suggested in my blog post?

Copper Contributor

I've gone through all these steps and still not Teams Meeting button in Outlook.  It doesn't show the COM Add-ins Manager:

 

2018-07-23 12_25_29-Clipboard.png

 

Trying to manually Add it from 

C:\Users\<Username>\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.18164.2\x64\Microsoft.Teams.AddinLoader.dll

Also doesn't work.

I'm doing all this with x64 versions, could this be a 64-bit issue?

Microsoft

Are you using the version of Outlook from the Microsoft Store (known as "Centennial")?  We have a known issue that the add-in does not load for this version of Outlook.  We have a fix for this issue coming.

 

Phil.

Brass Contributor

I have dealt with this a lot in our organization. I found that closing Teams, and Outlook. then confirming you have the TeamsMeetingAddin directory in  %localappdata%\Microsoft, if its there.. You will need to register the DLL for each the x86 and x64 versions. Once that has completed successfully, you can open Teams... wait, then open Outlook and the addin is back. I have had 100% success rate with this. If the client is missing the TeamsMeetingAddin directory, copy it from a machine that has the directory.

 

Sample of the batch file to register DLLs:

%SystemRoot%\System32\regsvr32.exe /n /i:user %LocalAppData%\Microsoft\TeamsMeetingAddin\1.0.18164.2\x64\Microsoft.Teams.AddinLoader.dll

%SystemRoot%\SysWOW64\regsvr32.exe /n /i:user %LocalAppData%\Microsoft\TeamsMeetingAddin\1.0.18164.2\x86\Microsoft.Teams.AddinLoader.dll

 

@Phillip Garding do you how far away is the Centennial support? We've been moved to Teams only and cannot create Teams Meeting via Outlook

Copper Contributor
Every freaking time that Teams is updated I have to re-register those two DLLs. Suppose this will ever be made better?!
Copper Contributor

I tried all the steps listed in the blog, but none of them worked. The only thing that did work is manually registering the DLL's. Gives me zero faith to roll this out as replacement for skype for business.


Copper Contributor
I continue to have issues with this. I was working away one evening week before last and noticed a couple items on the task bar coming and going and it was an automated Teams upgrade rolling through. Of course, at that point, the integration with Outlook was broken again. This time I took a few moments and moved the commands to manually register the DLLs into a batch file so that it's slightly less of a nuisance to deal with this.
Copper Contributor

Will there ever be a Mac version?

Microsoft

Michael, the Mac Outlook Teams add-in is currently in Outlook Insider Fast. We will be releasing it to public shortly. Thank you for your patience. 

Copper Contributor

@Phillip GardingI also would like to know about progress on the Centennial front. The Outlook client was recently updated with a brand new interface and I was expecting the Team integration to be in place.

Microsoft

Hi All,

 

This is a Tenant feature and if the add-on doesn't appear in Outlook, its generally because the tenant admin have not allowed it (disabled). In a lot of cases, customers maybe going through a Skype to Teams migration, planning Teams rollout/training planning, possible licensing requirements, like PSTN and PBX dialing plans, possible URL and port whitelisting not in place. Also worth knowing, PBX calling is not the same with Teams as SfB, so some additional contracts and configuration internally maybe needed. 

 

 Teams Outook Add-on [2].png

 

Please also see, 

Manage meeting policies in Teams

 

I hope this clarifies the issue now,

Deleted
Not applicable

We have experienced this issue with the Outlook Teams add-in this week as well with version 1810 (build 11001.20074 click-to-run) and Microsoft Teams Version 1.1.00.29068 (64-bit), last updated on Nov 9, 2018. The add-in has disappeared after the last update even though enabled in the meeting policies. The add-in files still exist in the local folder, but trying to add it back in, as mentioned above, does not work.

 

Command used to register the DLL was successful:

%SystemRoot%\System32\regsvr32.exe /n /i:user %LocalAppData%\Microsoft\TeamsMeetingAddin\1.0.18261.4\x64\Microsoft.Teams.AddinLoader.dll

 

Iron Contributor

Thank you so much @Loryan Strant - only noticed this issue tonight while testing a few things - that did it - I must share!  Cheers!

Brass Contributor

How about if it doesn't appear in OWA?  We have many users where the new OWA preview design shows the option for "Teams Meeting" when creating a calendar invite ... but another 1/3 of the tenant users do not see it - instead they see "Skype Meeting" toggle switch.

Brass Contributor

I am in TeamsOnly upgrade mode and I do NOT see the Teams meeting add-in in Outlook on Web, but I do have the S4B meeting add-in in Outlook on web.  Is anyone else seeing a Teams meeting add-in on OWA calendar events?

 

However, if I switch to "The new Outlook" in OWA then I do get a toggle for a Teams meeting which creates a link to a Teams meeting in the meeting invite.

 

Capture.PNG

Microsoft

@Sean McHugh@Tim Crean - currently scheduling a Teams meeting in OWA is only supported in the new React OWA platform which you can enable with the toggle. The old platform only supports scheduling Skype meetings. 

Any update about Centennial version, still only see Skype for Business option. Should we switch to normal Office365 desktop installation?

Copper Contributor

I believe some have suggested it here, so this may be redundant, but what I have found to work is the following:

  1. Close Outlook if open - wait - 5, 4, 3, 2, 1
  2. Sign out of Teams - actually sign out, don't just quit the application
  3. Sign in to Teams - Teams may actually automatically prompt for this after you sign out in step 2 - as @Loryan Strant mentioned be sure to be signing in to the same account/tenant as Outlook
  4. Teams will open - wait - 5, 4, 3, 2, 1
  5. Open Outlook - look for the Teams button in the Calendar

And agree, no better way to kill end user adoption than making people go through these hoops to schedule a meeting. We've been doing that for how many decades???

Brass Contributor

We had experienced this issue with the Teams add-in suddenly missing. In our case, I believe point #1 is the fix (compare the screen shots below). This may be something else to check if you have deprecated policies.

 

#1 – change meeting policy in the Teams admin center for the user to the Global policy (although the Outlook plug-in was allowed on all policies, the others were all marked as "deprecated")

 

#2 – also, we  re-installed Teams recommended above:

 

  1. Uninstall Teams and close Outlook – do not open again until step 5
  2. Re-install Teams and sign-in at least once
  3. Close Teams (make sure it’s not still running in memory – there’s a setting to determine if it keeps running when you close, for me it was set to not to keep running)
  4. Open Teams
  5. Open Outlook – the add-in should be back

"The new Outlook" was selected throughout testing and not touched.

Before making the change in #1 where (Skype meeting option shown):OWA with Skype.png

 

 After making the change in #1 (Teams meeting open shown):

 OWA with Teams.jpg

 

Note that this impacted user was on first release when the issue first occurred. For your information, we also tried to reinstall Office Pro Plus and Teams as well as upgrade to Windows 10 1803 first, but it didn’t change anything.

 

Iron Contributor

If you have the Teams Desktop client installed, Outlook will see an add-in for Teams, which will automatically be enabled. If you don’t have the desktop client installed, you won’t be able to see the ribbon icon.

 

Also, when you installed the Desktop version restart the machine. You will see the ribbon added there in your outlook.

 

If still not, check your Regedit: Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect

 

Make sure the LoadBehaviour is set to "3".

Copper Contributor
Ali, I've done everything you suggest on the 10-12 occasions where the Teams icon was present in the ribbon, and then disappeared when the next Teams or Outlook upgrade took place. Today I verified the registry setting just for fun. This is at the minor nuisance stage now, having created a batch file to re-register the necessary DLLs as described in an earlier post in this thread; all I need to check is that the version (and therefore the file path) has not changed. But it's a consistent nuisance; Outlook updated last week, and I got to run my batch file again.
Bronze Contributor

Here is one user also without the Add-in. When looking for the Teams' installation log under:

C:\Users\<userID>\AppData\Roaming\Microsoft\Teams\logs.txt

That says for me:

Fri Dec 07 2018 10:53:47 -- info -- Meeting policies synced. Enable Outlook Addin for Teams Meeting: true 
Fri Dec 07 2018 10:53:47 -- info -- Current Outlook Version: 16 
Fri Dec 07 2018 10:53:47 -- error -- Error in registering outlook meeting addin. Errorcode:[object Object] 
Fri Dec 07 2018 10:53:47 -- event -- name: meeting_addin_registration_failed, result: 2, reason: com_registration_failure, contextForAddin: meetingPolicySettingsSynced,  
Fri Dec 07 2018 10:53:48 -- info -- Comparing app version 1.1.00.31860 with critical version 1.0.00.6903 
Fri Dec 07 2018 10:53:48 -- info -- Comparing app version 1.1.00.31860 with minimum version 1.0.00.25152 

 

Kind of strange is also when you take a look the Add-in version from the folder, it says:

C:\Users\<userID>\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.17123.7

But at the same time the Teams version is: 1.1.00.31860.

Some very strange way I thought they should be the same, but obviously not...?

Iron Contributor

Sometimes when there are two instances( old and newer one) it causes conflict and becomes dysfunctional. remove both of them from options ( Outlook ) and Registry if possible, reboot machine. And install it again.

@Phillip Garding@Ali Fadavinia 

 

Any update about Centennial version, still only see Skype for Business option. Should we switch to normal Office365 desktop installation?

Copper Contributor

I am running 32-bit Office.  If I install 64-bit Teams as a standard user, the Teams Meetings add-on fails to install.  This is the log from %LOCALAPPDATA%\Microsoft\Teams\TeamsMeetingAddin:

2019-01-23-05:38:03.145 PM System.ArgumentException: Cannot delete a subkey tree because the subkey does not exist.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(String subkey, Boolean throwOnMissingSubKey)
   at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(String subkey)
   at Squirrel.MeetingAddinInstaller.<InstallMeetingAddinAsync>d__14.MoveNext()
2019-01-23-05:38:03.153 PM StagedAppDirectory does not exist. Using Current
2019-01-23-05:38:03.153 PM Version: 1.0.18317.2; addinPackageDirectory: 1.0.18317.2
2019-01-23-05:38:03.155 PM .dead exists: False
2019-01-23-05:38:03.155 PM before cleanup unused versions
2019-01-23-05:38:05.801 PM Addin directory exists. Copy was successful
2019-01-23-05:38:25.648 PM Failed to install the Teams meeting add-inCOM registration failed. Regsvr Path: C:\WINDOWS\system32\regsvr32.exe, Arguments: /s /n /i:user "C:\Users\rbz\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.18317.2\x64\Microsoft.Teams.AddinLoader.dll", ErrorCode: 0, % Message: 
2019-01-23-05:38:25.649 PM Directory exists. deleting...
2019-01-23-05:38:25.650 PM x64 Directory exists. deleting...
2019-01-23-05:38:25.651 PM x86 Directory exists. deleting...

It successfully copies the files but attempts to register the x64 add-in and fails.

 

I uninstalled 64-bit Teams and installed 32-bit Teams (matching the version of Office I am using), but it fails again as it attempts to register the x64 add-in.

 

Why is it attempting to register (and fails) the 64-bit add-in for my 32-bit Office?  I haven't tried uninstalling my 32-bit Office and installing 64-bit Office and seeing what happens when I install 32-bit and 64-bit Teams.

Iron Contributor

Hey Rod,

 

The versions should be same when you are installing add-ins: if your office is 32-bit, add-in should be 32-bit aswell. 

1) Cleanup the add-in in the Options --> Add-ins. Click Remove

2) If it still appears on the Add/Remove Programs remove it there

3) And delete the Teams add-in folder in the registry.

4) Reboot the machine

5) Install the compatible add-in

 

Copper Contributor

I think the problem is that I have had the 64-bit version as well as the 32-bit version of Office installed on this laptop.  My guess is that the uninstall of the 64-bit office left around some trash and the installer found enough 64-bit pieces that were left behind to think that this version was installed.  I have tested installing it on a few other laptops (some fresh, some users that I know never had the 64-bit Office installed) and it is working fine for them.  They did not have to do anything with administrative credentials as mentioned in the top of this post.  My solution for the moment was to copy the add-in folder from another computer and copy it to mine.  I then ran the regsvr32 command and pointed it at the x86 dll.  This will probably break during the next update but fixing this way is less time then wiping my laptop and starting over.  

 

Bottom line: bad code during the uninstall of 64-bit Office and bad code deciding which add-in should be installed.

Iron Contributor

It is the best to pull out and uninstall all remnants of both.

 

Microsoft recommends to move forward with the 64-bit version unless you have some serious hardware restraints.

 

Reinstall fresh one of those versions, and then add-in.

 

Once you installed the add-in, check in the reg-key value if it is set to "2" to load always when the Outlook kicks off.

 


@Phillip Garding wrote:

We’ve heard reports that the Microsoft Teams Meeting Add-in for Outlook on Windows does not show up for some users who have installed the desktop app.  There are several reasons why the add-in may not display that have simple remedies.  Here are some steps to help you troubleshoot this problem.

 

Install the Teams app as an administrator of the Windows computer.

One requirement for successfully installing the add-in on a Windows computer is that the user must have administrator permissions on the computer.  This is a requirement because COM add-ins to Outlook write to the Windows registry, and only administrators can modify the registry.  If the user who wants to schedule Teams meetings in Outlook is not an administrator, an administrator must install the Teams app first, and then the user can sign in and run Outlook.

 

Run Outlook in normal user mode, not as an administrator. 

When starting Outlook, do not run it with elevated permissions as this can interfere with identifying registered COM add-ins.

 

Download, install and sign into Teams and then restart Teams and Outlook, in that order. 

To ensure that the add-in is installed and loaded correctly, you may need to restart Teams and Outlook after installing.  Follow these steps:

  • Download the Teams desktop app, run it, and sign in at least once.
  • After signing into Teams, restart the app.
  • Restart Outlook (after restarting Teams).

 

Ensure that the add-in is installed and enabled.  If after all that, you still don't see the add-in, make sure that it isn't disabled for some reason.

  • In Outlook, click File and then Options.
  • Select the Add-ins tab of Outlook Options dialog box

Outlook Options, View Add-ins dialog boxOutlook Options, View Add-ins dialog box

  • Confirm that Microsoft Teams Meeting Add-in for Microsoft Office is listed in the Active Application Add-ins list
  • If the Teams Meeting Add-in is listed in the Disabled Application Add-ins list, select COM Add-ins in Manage and click Go…
  • Set the checkbox next to Microsoft Teams Meeting Add-in for Microsoft Office

Outlook Options, View Add-ins dialog boxOutlook Options, View Add-ins dialog box

  • Click OK on all dialog boxes and restart Outlook.

 

This should help fix the most common issues with the add-in.  If you continue to experience problems, please contact your support team for further assistance.

 

Thanks for using Microsoft Teams!

 


 

Copper Contributor

@Ali Fadavinia said "Microsoft recommends to move forward with the 64-bit version unless you have some serious hardware restraints." 

 

I still have a need to stay on 32-bit due to some old add-ins that aren't 64-bit compatible.  "All the remnants" didn't uninstall, hence why I am having this problem.

 

Iron Contributor

@rodgerzeisler Did you try to remove add in from Outlook --> Options --> add-ins?

 

Try to uninstall all your Office(s) there, and install a fresh 32-bit

Copper Contributor

Hi, All above fixes works and it is fine when we have to address individual user. But in corporate environment for every Teams update there are around 200 to 300 users report on this add-in issue which is really annoying. Microsoft should give serious thought process to this. I believe this because of the version number folder of the add-in gets updated every Teams update. When Outlook is open the folder gets messed. Though the Teams retains these folders based on the logs, sometimes it gets messed up. We cant expect users to maintain a correct order of closing or opening of Outlook and teams. The dependency of this should be removed. Until then the issue will persist. Let the version numbers be maintained in logs and atleast think of folder name as "Current Addin" and "Previous Addin" so that the entire path remains same for any N number of updates. And the registered application will be retaining the same path. And it does not need to register everytime. C:\Users\Userprofile\AppData\Local\Microsoft\TeamsMeetingAddin\VersionNumber\x86

Copper Contributor

We're having the same issue at our place of work. Teams Addon shows as inactive - Had to re-register the DLL (once the folder version number was identified) and then Restart Outlook and re-activate (tick it) in the Addon's section. 

 

As mentioned above if either Outlook or Teams is updated the Add-in DLL needs to be re-registered.

 

Microsoft please look at a more permanent solution...

Copper Contributor
I have an issue on my RDS servers since the Teams install is located in the user appdata folder and not program files. I have refused to push the Teams client to my RDS servers as it will add a bunch of disk space to user profiles and also trigger an update each time users open teams. So my users have gotten used to using the web version of Teams. However, they really want to be able to schedule a Teams meeting from regular outlook 2016 installed on the RDS servers. So my issue is I can not find any way to get the Teams outlook plugin for my users without installing teams for each user. Is there any way around this?
Microsoft

Morning Adam,

 

MS Teams support for VDI is in planning, according to Teams User Voice. I suggest following that article for more information on this topic and adding your 5 cents with the Product Group.

 

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18882088-non-persistent-vdi

 

I’ve seen some workarounds on this topic, nothing official, but it apparently works. As a final thought, have you considered using Teams Web Access to book meetings?

 

https://teams.microsoft.com/

 

Good luck ;)

Copper Contributor

@Phillip Garding can you comment as to when the Teams Meeting add-in for Outlook is coming to the Mac please?

It's February 28th 2019 and we still don't have it.

Microsoft
Copper Contributor

@Wayne Dean Thanks for the prompt reply. This has been rolling out supposedly for months now however yet has still not hit our org.

We've moved our entire tenant over to Teams only to find that Outlook for Mac doesn't have the add-in. We're 50/50 PCs Macs and unfortunately overlooked this in testing. Admittedly our mistake.

Is there any way to force the required REST upgrade using PowerShell to our Org?

 

Microsoft

Its most likely because your tenant is in the wrong mode and there for the add-on wont appear, please reach out to you IT Support (GA) for assistance. Remember this is a global change that needs to be made so it will effect all users.

 

ScreenClip [2].png

Migration and interoperability guidance for organizations using Teams together with Skype for Business

https://docs.microsoft.com/en-US/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype?WT.m...

 

 

Copper Contributor

@Wayne Dean We're in TeamsOnly mode which was set at the org level in the admin GUI a while ago now.

Surely this means we should be seeing the Teams Meetings add-in in Outlook for Mac? Outlook for Windows works fine.

 

It is my understanding that the Teams Meetings add-in in Outlook for Mac requires the backend REST upgrade that MS is currently pushing out, albeit very, very slowly.

This is what I want to force upgrade on the backend to enable Teams Meetings Add-in, as well as shared calendars, to appear in Outlook for Mac.

https://support.office.com/en-gb/article/teams-meeting-button-is-missing-in-outlook-for-mac-0d6608c7...

 

Microsoft

Gotcha, I would suggest logging into teams.microsoft.com and checking if its available there, if not, its being rolled out. A GA could log a ticket in the portal with O365 support to check on the status of the rollout.

 

Good luck

Version history
Last update:
‎Nov 09 2023 11:10 AM
Updated by: