You open Outlook to schedule a Teams meeting and the button is gone. No "Teams Meeting" in the ribbon, no option in the calendar event. This happens more often than it should, usually after a Teams update changes the DLL path and leaves the old COM registration behind.

Here is how to get it back.

Why the Button Disappears

The Teams Meeting button in classic Outlook is powered by a COM add-in called TeamsAddin.FastConnect. It loads a DLL from a version-numbered folder:

%LocalAppData%\Microsoft\TeamsMeetingAddin\<version>\x64\Microsoft.Teams.AddinLoader.dll

When Teams updates, it creates a new version folder. The old folder gets deleted, but the registry still points to the old path. Outlook tries to load a DLL that no longer exists, fails silently, and the button never appears.

Other causes: Outlook's resiliency system disabled the add-in for being too slow, Group Policy is blocking unmanaged COM add-ins, or classic Teams was uninstalled during migration to new Teams.

Fix 1: Check if the Add-in Is Disabled

  1. Open Outlook. Go to File > Options > Add-ins.
  2. Change the Manage dropdown to Disabled Items and click Go.
  3. If the Teams add-in is listed, select it and click Enable.
  4. Restart Outlook.
  5. Go back to File > Options > Add-ins, change to COM Add-ins, click Go, and verify the Teams add-in is checked.

If the add-in is not in either list, it is not registered at all. Move to Fix 2.

Fix 2: Re-register the DLL

First, find the current DLL. Open File Explorer and navigate to:

%LocalAppData%\Microsoft\TeamsMeetingAddin\

Open the folder with the highest version number. Inside, you will see x64 and x86 subfolders.

Open an elevated Command Prompt and run the appropriate command.

For 64-bit Office:

regsvr32 /n /i:user "%LocalAppData%\Microsoft\TeamsMeetingAddin\<version>\x64\Microsoft.Teams.AddinLoader.dll"

For 32-bit Office:

regsvr32 /n /i:user "%LocalAppData%\Microsoft\TeamsMeetingAddin\<version>\x86\Microsoft.Teams.AddinLoader.dll"

Replace <version> with the actual folder name. Restart Outlook and check for the button.

Fix 3: Fix the LoadBehavior Registry Value

The registry must tell Outlook to load the add-in at startup. Open Registry Editor and go to:

HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect

If this key does not exist, the add-in is not registered. Run the regsvr32 command from Fix 2 first.

If the key exists, check the LoadBehavior DWORD. It must be set to 3. Any other value means the add-in will not load automatically. Change it to 3 and restart Outlook.

Fix 4: Clear Resiliency Keys

Even after re-registering, Outlook might immediately disable the add-in again based on its crash history. Clear the slate.

Delete all entries under:

HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems
HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList

Then prevent future auto-disabling by creating:

HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList

Add a DWORD value named TeamsAddin.FastConnect set to 1.

Fix 5: Quick Repair Office

If the DLL is missing entirely or the COM registration is deeply broken, an Office repair will re-register everything.

  1. Go to Settings > Apps > Installed Apps.
  2. Find Microsoft 365 and click the three dots.
  3. Select Modify.
  4. Choose Quick Repair first. This takes about five minutes and fixes most registration issues.
  5. If that does not work, run Online Repair, which re-downloads all Office components.

Restart the machine after repair and check Outlook.

Fix 6: Check Group Policy and Trust Center

If your organization uses Group Policy to manage add-ins, the Teams add-in might be blocked.

Check this policy: User Configuration > Administrative Templates > Microsoft Outlook 2016 > Miscellaneous > List of managed add-ins

If the policy is enabled, TeamsAddin.FastConnect must be listed with a value of 1. If it is missing from the list while the policy is active, Outlook blocks the add-in entirely.

Also check Trust Center settings in Outlook: File > Options > Trust Center > Trust Center Settings > Macro Settings. If "Apply macro security settings to installed add-ins" is checked with strict macro security, the Teams add-in can be blocked on load.

New Outlook Does Not Use the COM Add-in

If you have switched to the new Outlook for Windows, the Teams Meeting button works differently. It is built into the app natively, not loaded as a COM add-in. If the Teams meeting option is missing in new Outlook, make sure you are signed into both Outlook and Teams with the same account and that your Microsoft 365 license includes Teams.

Teams meeting button missing across your organization? Contact Rain City Techworks.