You open Outlook to schedule a meeting and the New Teams Meeting button isn’t on the ribbon. No toggle in the event window either. It’s a common one, and the reason catches people off guard: the Teams Meeting add-in isn’t an Outlook feature. It’s installed and registered by the Teams desktop client, so anything that breaks that link — using Teams only in a browser, Outlook disabling the add-in, the two apps running as different users — makes the button vanish.
This guide works through the fixes in the order that resolves the most cases first: confirm desktop Teams is installed, enable the COM add-in, rescue it from the disabled list, match the user accounts, then re-register the DLL if it’s still missing. There’s also a section on the new Outlook for Windows, which handles this differently and trips up a lot of people after the switch.
Quick checks before you dig in
- The Teams desktop app is installed and you've signed in to it at least once
- You're using classic Outlook (the COM add-in doesn't exist in new Outlook)
- Outlook and Teams are both running as the same, normal Windows user — not 'as administrator'
- You've fully restarted both apps since the last update
- It's a desktop problem — the button never appears in Outlook on the web regardless
First: confirm desktop Teams is installed and signed in
This is the root cause more often than anything else. The add-in ships with the Teams desktop client and registers itself the first time Teams runs and signs in. If a user only ever opens Teams in a browser, or a fresh machine never had desktop Teams launched, the add-in was never installed and Outlook has nothing to show.
Install the Teams desktop app, sign in, and leave it running. Then restart Outlook. For a lot of people that alone brings the button back.
Enable the COM add-in in Outlook
If desktop Teams is installed but the button still isn’t there, the add-in is probably present but switched off. Check the COM add-ins list:
- In Outlook, go to File > Options > Add-ins.
- At the bottom, set the Manage dropdown to COM Add-ins and click Go.
- Find Microsoft Teams Meeting Add-in for Microsoft Office in the list.
- If its checkbox is clear, tick it and click OK.
- Restart Outlook.
If the add-in is listed and ticked but the button still doesn’t show, move on to the disabled items list — Outlook can keep an add-in “enabled” in this dialog while having quietly blocked it elsewhere.
Rescue it from the Disabled Items list
Outlook automatically disables add-ins it thinks crashed or slowed startup, and it dumps them in a separate list that’s easy to miss. The Teams add-in lands here after a Teams or Outlook crash more often than you’d expect.
- Go to File > Options > Add-ins again.
- Set the Manage dropdown to Disabled Items and click Go.
- If Microsoft Teams Meeting Add-in is in the list, select it and click Enable.
- Restart Outlook.
Make sure both apps run as the same, non-admin user
The add-in registers per Windows user. When Outlook and Teams run under different security contexts, the registration one app wrote isn’t visible to the other, and the button disappears.
The usual mistake is launching one app “as administrator.” If you right-click Outlook and run it elevated but Teams runs as your normal account, they’re effectively different users and the add-in won’t load. Close both, then start each one normally — same logged-in user, no elevation.
Re-register the add-in with regsvr32
If the add-in is installed but Outlook won’t load it at all — not in COM Add-ins, not in Disabled Items — the DLL registration is likely broken. You can re-register it manually.
First, close both Outlook and Teams completely (check Task Manager so no background process is holding the file). The add-in DLL lives under your local app data in a versioned folder, with separate x86 and x64 subfolders:
Teams Meeting add-in DLL location
| Base folder | %localappdata%\Microsoft\TeamsMeetingAddin |
|---|---|
| 32-bit Outlook | ...\TeamsMeetingAddin\ |
| 64-bit Outlook | ...\TeamsMeetingAddin\ |
Match the bitness to your Outlook build (File > Office Account > About Outlook shows 32-bit or 64-bit). Register the matching DLL — adjust the <version> folder name to whatever is actually present:
# Close Outlook and Teams first
$dll = Get-ChildItem "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin" -Recurse -Filter "Microsoft.Teams.AddinLoader.dll" |
Where-Object FullName -like "*\x64\*" | Select-Object -First 1
regsvr32.exe /n /i:user "$($dll.FullName)"For 32-bit Outlook, point at the x86 copy instead:
regsvr32.exe /n /i:user "%localappdata%\Microsoft\TeamsMeetingAddin\<version>\x86\Microsoft.Teams.AddinLoader.dll"Then start Teams, sign in, and start Outlook. The /i:user switch matters — it registers for the current user, which is exactly the per-user scope the add-in expects.
If you’re on the new Outlook for Windows
This is the section that explains a lot of “it vanished after an update” reports. The new Outlook for Windows doesn’t use the classic COM add-in model at all, so the Microsoft Teams Meeting Add-in for Microsoft Office won’t appear in it — and there’s no COM Add-ins dialog to enable it in.
Instead, new Outlook has a built-in Teams meeting toggle that appears when you create a calendar event, as long as your account is licensed and configured for Teams meetings. Nothing to install.
Add-in behavior by Outlook version
| Classic Outlook (desktop) | Uses the COM add-in installed by desktop Teams — enable it in File > Options > Add-ins |
|---|---|
| New Outlook for Windows | No COM add-in; uses a built-in Teams meeting toggle on calendar events |
| Outlook on the web | Built-in Teams toggle; the COM add-in never applies |
So if you flipped the Try the new Outlook switch and the familiar button disappeared, that’s expected behavior, not a fault. Look for the built-in toggle when scheduling, or turn off the new Outlook switch to return to classic Outlook and the COM add-in.
Last resort: repair or reinstall Teams
If none of the above brings the add-in back in classic Outlook, the Teams install itself is likely damaged. Reinstalling the desktop client re-deploys and re-registers the add-in cleanly.
Quit Teams and Outlook, uninstall the Teams desktop client, reboot, then install the current desktop client fresh. Sign in to Teams, let it settle, and start Outlook. Because reinstalling regenerates the versioned add-in folder, this also clears up a broken regsvr32 state without you hunting for the right path.
If clearing cache is part of your usual Teams repair routine, the cache locations and a safe clear procedure are covered in the Teams meeting troubleshooting guide.
Quick reference: fixes in order
Work through these top to bottom
- Install desktop Teams and sign in (the add-in comes from it, not Outlook)
- Start Teams first, then Outlook
- Enable the COM add-in: File > Options > Add-ins > Manage: COM Add-ins > Go
- Rescue it from Manage: Disabled Items if Outlook switched it off
- Run both apps as the same, non-elevated Windows user
- Re-register Microsoft.Teams.AddinLoader.dll with regsvr32 (matching bitness)
- On new Outlook, use the built-in Teams toggle — the COM add-in doesn't apply
- Reinstall the Teams desktop client as a last resort
Wrapping up
The missing Teams Meeting button almost always comes down to the add-in’s source: it’s installed by the Teams desktop client and registered per user, so the fix is making that link solid again. Confirm desktop Teams is installed, enable the COM add-in, pull it out of Disabled Items, and make sure both apps run as the same non-admin user. If you’ve moved to new Outlook, there’s nothing to repair — the toggle is built in and behaves differently by design.
When the button is part of a wider set of Teams problems — calls not connecting, a dead camera in Teams, or join failures — work the broader Teams meeting troubleshooting guide alongside this one. For more client and admin fixes, browse the Microsoft Teams guides.
